W3C home > Mailing lists > Public > public-html@w3.org > December 2010

[Bug 11568] New: dragenter should be fired after dragleave

From: <bugzilla@jessica.w3.org>
Date: Fri, 17 Dec 2010 11:28:15 +0000
To: public-html@w3.org
Message-ID: <bug-11568-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11568

           Summary: dragenter should be fired after dragleave
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: giorgio.liscio@email.it
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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

-- 
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 Friday, 17 December 2010 11:28:18 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:07 UTC