-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shadow Block Converter Plugin Parent Block Visual Selection Bug #2426
Comments
@johnnesky: Would you like to take a look at this? |
Sure! |
Hm, I'm having trouble replicating the problem at the shadow block converter demo page. @changminbark, can you share more information? What version of Blockly are you using? Do you have any of your own customizations we should know about? Is there a public demo we can try? Screen.Recording.2024-08-02.at.11.00.03.AM.mov |
Hello! I am currently testing this on Blockly v11.1.1. Below is my package.json file.
My index.js file is also shown below: As for a public demo, you can try cloning this branch and running npm i and npm start to test things out: Let me know if you have any other questions. Thank you! |
It turns out that I'm able to replicate the bug inside the shadow-block-converter plugin demo page by updating the dependency on core Blockly from 11.0.0 to 11.1.1. Will investigate. EDIT: The bug is also present in 11.1.0. |
I believe the bug was a side effect of: google/blockly#8172 |
If I revert the changes related to |
Check for duplicates
Component
Shadow Block Converter Plugin
Description
I think that I've come across a bug where editing a shadow block will select the parent block (at least visually). However, when trying to select something else (like a block or the workspace), the former shadow block's parent block does not get unselected (visually). This was tested without any of the other plugins (except for backpack). I will report this on the Blockly plugins github page. Look at the gif below for reference.
Reproduction steps
Stack trace
No response
Screenshots
The text was updated successfully, but these errors were encountered: