scratchfoundation / scratchfoundation/scratch-blocks
Issues with showing and hiding flyout
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
I tried to use flyout.hide() function to hide the flyout and flyout.show() to show to populate it with a new set of blocks. When the flyout is hidden, I can drag the blocks in the workspace to where the flyout was suppose to be, then the blocks gets deleted because those blocks are deemed to be dropped on top of the flyout. There seems to be a bug where the workspace doesn't know that the flyout isn't there anymore. Additionally, using flyout.show() doesn't work as expected. workspace.updateToolbox() works but then if the flyout is hidden, it doesn't reshow it. Is this a known issue or that isn't supported in the current version of the library.
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
Start by reproducing the reported behavior with flyout.hide(), flyout.show(), and workspace.updateToolbox(). Trace how the workspace handles drops in the flyout area while hidden and how showing the flyout interacts with toolbox updates. Done means hidden flyouts no longer delete blocks dropped in their former area, and showing the flyout works as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100