W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2012

[Bug 16336] New: defaultPrevented and preventDefault() conflict

From: <bugzilla@jessica.w3.org>
Date: Mon, 12 Mar 2012 21:09:03 +0000
To: www-dom@w3.org
Message-ID: <bug-16336-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16336

           Summary: defaultPrevented and preventDefault() conflict
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
               URL: http://lists.w3.org/Archives/Public/www-dom/2011JanMar
                    /0067.html
        OS/Version: Windows NT
            Status: NEW
          Keywords: LC
          Severity: normal
          Priority: P2
         Component: DOM3 Events
        AssignedTo: travil@microsoft.com
        ReportedBy: travil@microsoft.com
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, annevk@opera.com, www-dom@w3.org


defaultPrevented says it reflects whether preventDefault() has been  
invoked for the event whereas preventDefault() says it only has an effect  
if the event is in fact cancelable. I think this has led to different  
implementations of these features in e.g. Opera and Gecko.

In DOM Core defaultPrevented can only be true for cancelable events. (This  
is another reason why I changed initEvent() to also reset the "canceled  
flag" so that if you change an event from being cancelable to  
non-cancelable everything still makes sense.)

-- 
Configure bugmail: https://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, 12 March 2012 21:09:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:09 GMT