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

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 31 Oct 2011 21:08:42 +0000
To: public-html@w3.org
Message-ID: <bug-14638-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14638

           Summary: Should a canceled drop event signify a failed drop
                    operation?
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: bytecrafter@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


In "Drag-and-drop processing model", it appears that the determination of
whether the drop succeeded or failed has been decided before the drop event is
fired. Even if the drop event is canceled, this is still considered to be a
successful drop. While it doesn't matter from the web page's point-of-view (if
the drop handler is smart enough to cancel the event, it's also smart enough to
treat the drop as a failure), it does matter for browsers that use feedback to
signify drag failure (such as "snap-back" feedback). Should a canceled drop
event be treated by the browser as a failure or a success?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 31 October 2011 21:10:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:28 UTC