Marked addEventListenerNS and removeEventListenerNS At Risk

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 www-dom@w3.org.

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] 
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.80
[2] 
http://xmlgraphics.apache.org/batik/javadoc/org/apache/batik/dom/events/NodeEventTarget.html#addEventListenerNS%28java.lang.String,%20java.lang.String,%20org.w3c.dom.events.EventListener,%20boolean,%20java.lang.Object%29
[3] http://www.w3.org/TR/xml-events/

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs

Received on Saturday, 12 September 2009 21:31:16 UTC