Check for duplicates
Description
In v12 dragging a disabled block remains disabled. But in v12 + keyboard nav plugin dragging or keyboard moving a disabled block enables it for the duration of the drag/move, which we did to improve the understanding of the connection previews.
Plugin implementation: https://github.com/RaspberryPiFoundation/blockly-keyboard-experimentation/blob/main/src/disabled_blocks.ts#L17-L44
I think a case can be made for just doing this across the board but will check with the MakeCode team later today. Perhaps an explicitly disabled block in Blockly should be treated differently.
In MakeCode the typical scenario is a block that's disabled because it's on the workspace but should be moved to a top-level event block or value input. It's hard to reproduce that exactly in the playground.
Reproduction steps
Priority
Looking for a stance initially: was this missed or intentionally dropped? I think it's all public API so it could be an application concern, but consistency might be good for something like this. Was the effect on drags intended or just a side effect of getting it right for keyboard moves?
Stack trace
Screenshots
No response
Browsers
No response
Check for duplicates
Description
In v12 dragging a disabled block remains disabled. But in v12 + keyboard nav plugin dragging or keyboard moving a disabled block enables it for the duration of the drag/move, which we did to improve the understanding of the connection previews.
Plugin implementation: https://github.com/RaspberryPiFoundation/blockly-keyboard-experimentation/blob/main/src/disabled_blocks.ts#L17-L44
I think a case can be made for just doing this across the board but will check with the MakeCode team later today. Perhaps an explicitly disabled block in Blockly should be treated differently.
In MakeCode the typical scenario is a block that's disabled because it's on the workspace but should be moved to a top-level event block or value input. It's hard to reproduce that exactly in the playground.
Reproduction steps
Priority
Looking for a stance initially: was this missed or intentionally dropped? I think it's all public API so it could be an application concern, but consistency might be good for something like this. Was the effect on drags intended or just a side effect of getting it right for keyboard moves?
Stack trace
Screenshots
No response
Browsers
No response