scratchfoundation / scratchfoundation/scratch-blocks
What should behaviour be when a block is very long?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
Expected Behavior
However large my block is, should I be able to somehow see all of it when I drag it, either by scrolling or some other approach?
Should there be a max length/ max size? I would guess not, because it's easy to imagine that if you're using e.g. operators or custom blocks you could get some very long blocks.
Actual Behavior
When the block is long enough that it's wider than my computer screen, when I'm dragging it, I can't scroll or drag it any further to the left in order to see the rest of the block.
Steps to Reproduce
- Make a very long block
- Click & drag it to make it come to the front layer
Operating System and Browser
Mac OS El Capitan, Chrome 59
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the long-block dragging behavior from https://llk.github.io/scratch-gui/ using the reported Mac OS El Capitan and Chrome 59 setup. The issue names no source files or tests; first determine the intended behavior for viewport access and block size, then verify the chosen behavior with a very long block.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100