- From: <bugzilla@jessica.w3.org>
- Date: Thu, 19 Dec 2013 22:49:28 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13524 Andrew R <andrew@eternicode.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@eternicode.com --- Comment #5 from Andrew R <andrew@eternicode.com> --- Open bug in webkit: https://bugs.webkit.org/show_bug.cgi?id=66547 Similar, fixed bug in mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=458613 Test case: http://jsfiddle.net/3yWqy/1/ (If I need to submit an actual HTML file to be legit, let me know) In Firefox 26.0, relatedTarget on a dragleave is the DOM element being entered (the element which subsequently triggers a dragenter). Similarly, for dragenter it's the DOM element being left. Essentially, dragleave and dragenter are treated as mirror events, as they should be -- dragleave.target = dragenter.relatedTarget and dragleave.relatedTarget = dragenter.target. This makes much more sense than setting it to null, and is much more useful. Can we reopen this issue? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 19 December 2013 22:49:30 UTC