W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2011

[Bug 15259] New: CustomEvent initEvent

From: <bugzilla@jessica.w3.org>
Date: Sun, 18 Dec 2011 04:25:08 +0000
To: www-dom@w3.org
Message-ID: <bug-15259-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15259

           Summary: CustomEvent initEvent
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM Core
        AssignedTo: annevk@opera.com
        ReportedBy: brandonyoyoslade@gmail.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, www-dom@w3.org


In the DOM4 specification, the interface of CustomEvent (found at
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#customevent) contains
only one member: "readonly attribute any detail;" The DOM3EVENTS specification
declares one more method overload, "initCustomEvent(DOMString type, bool
bubbles, bool cancelable, any detail);". (This can be found at
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-CustomEvent)

I know that the initEvent method is made obsolete due to the fact that in DOM3
you are introducing Event constructors, but as long as they're not actually
depreciated, shouldn't you keep them simply for backwards-compatibility? At the
very least, shouldn't you keep initCustomEvent for the same reason that you are
keeping initEvent, or if you need to get rid of one, then unify the change and
get rid of both?

-- 
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 Sunday, 18 December 2011 04:25:14 GMT

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