Issue metadata
Sign in to add a comment
|
can't stop on breakpoints in both "drop" and "dragend" handlers
Reported by
pie...@gmail.com,
Aug 23 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. https://jsfiddle.net/pdho35k6/1/ 2. f12, run, hit 'debugger;' 3. set BP ONLY on 'dragend' handler 4. drag yellow div to 'target' div, hits BP in 'dragend' handler 5. NOTICE: 'drop2' was written to the console window. 6. f8, clear console window. 7. set another BP in 'drop' handler 8. drag yellow div to target again, hits BP in 'drop' handler 9. BUG: 'dragend' was written to console, but 1st BP was NOT hit What is the expected behavior? should hit both BPs What went wrong? it doesn't stop on the BP Did this work before? N/A Chrome version: 52.0.2743.116 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0
,
Aug 26 2016
Alexey, could you please look at this? I think you've dealt with drag handlers some time ago
,
Aug 27 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pie...@gmail.com
, Aug 23 2016ok, this is even worse than just this. it seems like all sorts of drag/drop events are fired, and script executed even when stopped at a breakpoint. for example, if you add a "console.log('dragover');" in the dragover handler, then stop at a breakpoint on that line; dragging a file from the desktop over the drop-target will cause 'dragover' to be written multiple times to the console, even while stopped at the breakpoint. why does 'dragover' have this behavior and not, say 'mouseover', or 'click' ? does this mean that the browser is multi-threaded wrt drag-drop events? is this thread-safe? are there thread synchronization mechanisms available to manage this?