Re: Marked addEventListenerNS and removeEventListenerNS At Risk

FYI, XML Events 1.0[3] relies on DOM 2 Events, so it doesn't
need namespaced events.
XML events 2.0 is still just a draft, and it just says "However, future 
versions of DOM Events are likely to allow namespaced event names, so 
language designers are advised not to use the colon character ":" in 
event names."


Doug Schepers wrote:
> Hi, DOM3 Events folks-
> (BCC to groups potentially affected.)
> I have marked addEventListenerNS and removeEventListenerNS at-risk in 
> the latest Editor's Draft of the DOM3 Events specification [1]. This 
> means that we are gathering information on whether we can safely remove 
> these methods from the specification.
> Apparently, these are not yet implemented in desktop browsers, so there 
> has been a call to reexamine their inclusion in this specification. I 
> personally suspect that there is not much of an implementation burden 
> regarding these methods, but I would welcome implementer feedback on the 
> matter.
> I don't know how widely deployed other implementations are, nor how much 
> content relies on these methods. I do note that it is supported in Batik 
> [2] and Inkscape, and more generally in Java implementations of the DOM. 
> I believe that other W3C specifications may rely on it (XML Events [3], 
> maybe XForms). Any evidence that removing these methods from the 
> specification should be sent to
> We also welcome use cases in favor of retaining or removing them. My 
> inclination is to retain the namespace-aware methods, since there are 
> existing implementations, so evidence that removing them will be 
> beneficial will have to be pretty strong, but it's on the table.
> Thanks for your feedback.
> [1] 
> [2] 
> [3]
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG and WebApps WGs

Received on Sunday, 13 September 2009 12:17:35 UTC