Connecting duplicated blocks can result in the stack being executed

[thisandagain]

[paulkaplan]

This appears to be due to the pointer-events: none; that GUI applies to the .blocklyBlockDragSurface, but I'm not exactly sure why, still investigating. Removing that line fixes the problem, but there is a comment about why that line is needed. https://github.com/LLK/scratch-gui/blob/develop/src/components/blocks/blocks.css#L83

/ht @picklesrus

[ErikMejerHansen]

Possible duplicate of: scratchfoundation/scratch-blocks#1935 (or the other way around)

[paulkaplan]

@ErikMejerHansen yup can confirm this is the same issue. The issue does not appear in the blocks playground, it is actually a problem introduced by the GUI CSS, so I'm going to close that one as a duplicate of this.

[adroitwhiz]

This is happening again because #5078 was reverted

[griffpatch]

As you probably are all aware, but I just wanted to state it. The execution occurs because you click to drop the duplicated block stack. If you are attaching to the bottom of another stack then the scripts are not executed, but if you drop between other blocks in a block stack then the stack is executed. This is because your cursor is 'over' the block stack when you click to place the duplicated stack, and are therefore clicking the stack behind too. If we could just cancel the event bubbling it might all go away?

…

On Wed, 8 Jul 2020 at 23:53, adroitwhiz ***@***.***> wrote: Reopened #1307 <#1307>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1307 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTM3PS523RJ556VNPQIQUTR2T2INANCNFSM4EMOQQDA> .