13524 2011-08-02 18:43:38 +0000 relatedTarget shouldn't be null for dragleave event(as mouseout) 2014-01-14 00:43:26 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-dragevent-interface a11y P3 normal Unsorted 1 contributor ian andrew cooper ian mike public-html-admin public-html-wg-issue-tracking contributor oldest_to_newest 52001 0 contributor 2011-08-02 18:43:38 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html Multipage: http://www.whatwg.org/C#the-dragevent-interface Complete: http://www.whatwg.org/c#the-dragevent-interface Comment: relatedTarget shouldn't be null for dragleave event(as mouseout) Posted from: 188.17.104.28 User agent: Opera/9.80 (Windows NT 5.1; U; ru) Presto/2.9.168 Version/11.50 52762 1 mike 2011-08-04 05:04:04 +0000 mass-moved component to LC1 54665 2 ian 2011-08-11 02:58:38 +0000 Do you have a test case demonstrating this? What should it be? 57034 3 cooper 2011-09-20 15:18:51 +0000 Bug triage sub-team is tracking this because of drag and drop, doesn't yet have an opinion one way or the other on the issue raised. 57454 4 ian 2011-09-27 22:24:36 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: It's null in WebKit, at least (I happened to test that one because it's easy to set breakpoints in WebKit). If it's not null in another browser, please attach a test case demonstrating it. 97821 5 andrew 2013-12-19 22:49:28 +0000 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? 98272 6 andrew 2014-01-11 01:58:43 +0000 Reopening pursuant to: > If you have additional information and would like the editor to reconsider, please reopen this bug. 98388 7 ian 2014-01-14 00:43:18 +0000 Ok, I've tried to spec this. Please don't hesitate to reopen this bug if the edit isn't complete enough, or if it doesn't match Firefox precisely (assuming what Firefox does is better). 98389 8 contributor 2014-01-14 00:43:26 +0000 Checked in as WHATWG revision r8396. Check-in comment: Make some dragleave and dragenter events have a relatedTarget. http://html5.org/tools/web-apps-tracker?from=8395&to=8396