@Liza @Rodrigo @awesomeonion
The recent addition of the drag & drop trash can to editor to prevent accidental deletions is a reasonable idea, however...
The code scrolls up as you drag down to the trash can, so you lose your place. This makes deleting code blocks very frustrating.
This scrolling behavior drives the user to try to drag & drop on the trash can quickly before scrolling begins. Which in turn increases the risk of dropping the code block in an unintended place (which may not be noticed) if you don't quite drag it completely onto the trash can. It doesn't make sense to me to mitigate one risk by replacing it with another. Worse is that accidental deletion was already undoable so the risk was already mitigated. Now code might be moved instead of being deleted and not noticed, which would cause significant headaches.
Dragging down still needs to allow the code to scroll, but the scolling needs to be locked (off) when the drag event occurs over the trash can so the user can pause to confirm they're dropping the block in the intended location.
Please fix this behavior. If this can't easily be fixed, I'd much prefer the prior "drag-to-the-side to delete"
P.S. the Set Text block causing 'Whomp' was not fixed in v3.18.0. Why, oh why, do you continue to tinker with the GUI (causing new problems) instead of fixing the existing problems???