scratchfoundation / scratchfoundation/scratch-blocks
Replacing reporter hides previous reporter under block
Open
Nobody has claimed this yet.
needs-triage
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
Expected Behavior
All added blocks and reporters should be visible all the time.
Actual Behavior
If you replace a reporter the previous reporter may get hidden under other blocks in stack.
Steps to Reproduce
Add two blocks in a stack.
Add reporter to first block
Replace reporter with a new reporter
See that the previous reporter gets paced behind block
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 issue using the listed steps: stack two blocks, add a reporter to the first, and replace it. Trace the replacement and block-rendering behavior to determine why the previous reporter is placed behind another block; done means all added blocks and reporters remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100