W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2011

[Bug 14638] Should a canceled drop event signify a failed drop operation?

From: <bugzilla@jessica.w3.org>
Date: Tue, 01 Nov 2011 05:52:04 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RL7GW-0004yo-Cy@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14638

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-11-01 05:52:02 UTC ---
The text actually already handles the case you're describing, it's just not
very clear. I've tried to clarify the text.

Search for where the spec says "If the platform conventions dictate that this
be represented to the user (e.g. by animating the dragged selection going back
to the source of the drag-and-drop operation), then do so", and notice that the
condition for that is that either /dropped/ be false, or that the /current drag
operation/ be "none". The latter can happen for several reasons even if
/dropped/ is true, in particular, you can set event.dataTransfer.dropEffect to
"none" in the "drop" event and cancel it, or, if the user isn't dragging to
some text editing region, you can just not handle the event (not cancel it).

Does that make sense?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 1 November 2011 05:52:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 November 2011 05:52:12 GMT