11568 2010-12-17 11:28:15 +0000 Add "dragexit" event to the drag-and-drop model 2013-03-18 22:15:54 +0000 1 1 1 Unclassified WHATWG HTML unspecified All All RESOLVED FIXED https://www.w3.org/Bugs/Public/show_bug.cgi?id=19041 P2 major Unsorted 1 giorgio.liscio ian giorgio.liscio ian mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 43449 0 giorgio.liscio 2010-12-17 11:28:15 +0000 spec says that when i drag over a new item first is fired dragenter on the new target then is fired dragleave on the old target i think this is wrong because any ancestor element receives as "last-fired-event" the "dragleave". that means, for me, "no drag operation is in progress" in mouseover/mouseout first is fired mouseout on the old target then is fired mouseover on the new target when the event propagates, for example at the body element, i can determine that the mouse is over my page with dragleave/dragenter i can not please read test cases and samples here https://bugzilla.mozilla.org/show_bug.cgi?id=619703 44189 1 ian 2011-01-11 19:21:00 +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: I agree that it's awkward (you have to track the targets from the ancestor dragleave event handler to make sure you don't screw it up), but it's what IE does, and we're just speccing what IE does here. Changing it would risk breaking pages written to work with IE's drag-and-drop over the last decade or so. 44267 2 giorgio.liscio 2011-01-12 08:39:15 +0000 hi Hixie, mozilla supports both dragleave and dragexit (old mozilla's api) the order is: dragexit dragenter dragleave its exactly like dragleave, but it is fired before dragenter, why not include this event too to extend compatibility with mozilla? 44286 3 giorgio.liscio 2011-01-12 17:41:57 +0000 sorry if i reopen, maybe i need to do this to have comments about include dragexit too in the spec 45509 4 ian 2011-02-15 00:08:47 +0000 Do you have a testcase demonstrating this? I tried testing it but was unsuccessful in demonstrating the existence of 'dragexit' events. 45545 5 955 giorgio.liscio 2011-02-15 02:52:14 +0000 Created attachment 955 dragexit vs dragleave sure Hixie, here both events in action you probably need and it is sure better to run this file in firefox's latest trunk http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ thank you 45546 6 giorgio.liscio 2011-02-15 03:02:16 +0000 a note: i've just tested with both firefox 3.6 and firefox 4 beta firefox 3.6 does not match the current spec (dragenter is fired after dragleave) firefox 4.0 matches the current spec so in firefox 3.6 dragexit == dragleave and they are fired both before dragenter in firefox 4.0 the event order is: aaa dragexit bbb dragenter aaa dragleave 47876 7 ian 2011-05-03 19:27:40 +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: Partially Accepted Change Description: see diff given below Rationale: Thanks. Interesting. I've not added this to the spec yet, but I think we should probably do so in due course. Before we do so, I'd like to wait to see if we can get all the other recent additions to this API implemented reliably in all the major browsers. If another browser intends to implement 'dragexit' before I've specced it please let me know and I'll prioritize this. 53858 8 mike 2011-08-04 05:33:52 +0000 mass-move component to LC1 69006 9 giorgio.liscio 2012-06-12 17:12:57 +0000 hi hixie, news about this? *see the attachment when you drag over the white paragraph the drag event is still valid because the dragover bubbles up to #test but it is impossible to handle contents according to pointer movements, because of the bad design of events I think dragenter and dragleave events are totally useless now... but! a challenge for hackers: try to workaround this, with some code that allows to move on the white paragraph (coming from the gray area) without losing the dotted border... ... yeah... it is madness... yeah... why the standard is what IE does and not what Firefox does? 69007 10 1143 giorgio.liscio 2012-06-12 17:14:01 +0000 Created attachment 1143 wrong event order 82043 11 public-rdfa-wg 2013-01-24 06:57:45 +0000 This bug was cloned to create HTML WG bug 19041. 84578 12 contributor 2013-03-18 22:15:54 +0000 Checked in as WHATWG revision r7760. Check-in comment: Add 'dragexit' event similar to what Firefox does. http://html5.org/tools/web-apps-tracker?from=7759&to=7760 955 2011-02-15 02:52:14 +0000 2011-02-15 02:52:14 +0000 dragexit vs dragleave dragexitVSdragleave.htm text/html 892 giorgio.liscio PGRpdiBpZD0ibG9nIiBzdHlsZT0iZmxvYXQ6cmlnaHQ7Ij48L2Rpdj4NCg0KPGRpdiBpZD0iZHJh Z21lIiBkcmFnZ2FibGU9InRydWUiIHN0eWxlPSJib3JkZXI6M3B4IHJlZCBzb2xpZDtwYWRkaW5n OjEwcHg7d2lkdGg6MTAwcHg7Ij4gZHJhZyBtZSA8L2Rpdj4NCg0KI0FBQToNCjxkaXYgaWQ9ImFh YSIgc3R5bGU9ImJvcmRlcjoycHggYmxhY2sgZG90dGVkO3dpZHRoOjIwMHB4O2hlaWdodDoyMDBw eDtwYWRkaW5nOjQwcHg7Ij4NCgk8ZGl2IGlkPSJiYmIiIHN0eWxlPSJib3JkZXI6MnB4IGJsYWNr IGRvdHRlZDtwYWRkaW5nOjIwcHg7Ij4NCgkJI0JCQg0KCTwvZGl2Pg0KPC9kaXY+DQoNCjxzY3Jp cHQ+DQoNCnZhciBsb2cgPSBkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgibG9nIik7DQoNCnZhciBh YWEgPSBkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgiYWFhIik7DQoNCmRvY3VtZW50LmdldEVsZW1l bnRCeUlkKCJkcmFnbWUiKS5hZGRFdmVudExpc3RlbmVyKCJkcmFnc3RhcnQiLGZ1bmN0aW9uKGV2 KXtldi5kYXRhVHJhbnNmZXIuc2V0RGF0YSgidGV4dC9wbGFpbiIsInRlc3QiKTt9LHRydWUpOw0K ZnVuY3Rpb24gc2hvd2V2ZW50KGV2KXsgbG9nLmlubmVySFRNTCArPSAoZXYudGFyZ2V0LmlkID8g ZXYudGFyZ2V0LmlkIDogJycpICsgIiAiICsgZXYudHlwZSArICI8YnI+IiArIChldi50eXBlPT0i ZHJhZ2xlYXZlIiA/ICItLS0tLS0tLS08YnI+IiA6ICIiKTt9DQoNCmFhYS5hZGRFdmVudExpc3Rl bmVyKCJkcmFnZW50ZXIiLCBzaG93ZXZlbnQsdHJ1ZSk7DQphYWEuYWRkRXZlbnRMaXN0ZW5lcigi ZHJhZ2V4aXQiLCBzaG93ZXZlbnQsdHJ1ZSk7DQphYWEuYWRkRXZlbnRMaXN0ZW5lcigiZHJhZ2xl YXZlIiwgc2hvd2V2ZW50LHRydWUpOw0KDQoNCjwvc2NyaXB0Pg== 1143 2012-06-12 17:14:01 +0000 2012-06-12 17:14:01 +0000 wrong event order dragdrop.htm text/html 837 giorgio.liscio PGRpdiBpZD0idGVzdCIgc3R5bGU9ImJvcmRlcjozcHggYmxhY2sgc29saWQ7YmFja2dyb3VuZDpy Z2IoMjAwLDIwMCwyMDApOyI+DQoJPGJyPjxicj4NCgk8cCBzdHlsZT0iYmFja2dyb3VuZDp3aGl0 ZTtwYWRkaW5nOjEwcHg7bWFyZ2luOjEwcHg7Ij5EUk9QIFRFWFQgSEVSRSAod2hpdGUgcGFyYWdy YXBoLCBjaGlsZCBvZiBncmF5IGFyZWEpPC9wPg0KCTxicj48YnI+DQo8L2Rpdj4NCg0KZHJhZyBU SElTIHRleHQgb3ZlciB0aGUgZ3JheSBhcmVhLCB0aGVuIG92ZXIgdGhlIHdoaXRlIHBhcmFncmFw aDxicj4NCg0KPHNjcmlwdD4NCmZ1bmN0aW9uIGxvZ2codGV4dCkNCnsNCmRvY3VtZW50LmJvZHku YXBwZW5kQ2hpbGQoZG9jdW1lbnQuY3JlYXRlVGV4dE5vZGUodGV4dCkpOw0KZG9jdW1lbnQuYm9k eS5hcHBlbmRDaGlsZChkb2N1bWVudC5jcmVhdGVFbGVtZW50KCJiciIpKTsNCn0NCg0KdmFyIGEg PSBkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgidGVzdCIpOw0KYS5hZGRFdmVudExpc3RlbmVyKCJk cmFnZW50ZXIiLCBmdW5jdGlvbihldil7IGxvZ2coZXYudHlwZSArICIgb24gIiArIGV2LnRhcmdl dCk7IHRoaXMuc3R5bGUuYm9yZGVyPSIzcHggcmVkIGRvdHRlZCI7IH0sZmFsc2UpOw0KYS5hZGRF dmVudExpc3RlbmVyKCJkcmFnbGVhdmUiLCBmdW5jdGlvbihldil7IGxvZ2coZXYudHlwZSArICIg b24gIiArIGV2LnRhcmdldCk7IHRoaXMuc3R5bGUuYm9yZGVyPSIzcHggYmxhY2sgc29saWQiOyB9 LGZhbHNlKTsNCmEuYWRkRXZlbnRMaXN0ZW5lcigiZHJhZ292ZXIiLCBmdW5jdGlvbihldil7ZXYu cHJldmVudERlZmF1bHQoKTt9LGZhbHNlKTsNCg0KPC9zY3JpcHQ+