W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2009

Re: Marked addEventListenerNS and removeEventListenerNS At Risk

From: Jonas Sicking <jonas@sicking.cc>
Date: Sat, 19 Sep 2009 13:28:12 -0700
Message-ID: <63df84f0909191328q7e06295ck4ec0ed6477678b61@mail.gmail.com>
To: Krzysztof Maczyński <1981km@gmail.com>
Cc: www-dom@w3.org
2009/9/19 Krzysztof Maczyński <1981km@gmail.com>:
> I'm strongly against removing namespace support from DOM Events. The use case for them is as valid as that for element types - to avoid clashes.

There is an important difference.

Elements and attributes use namespaces, but use a prefix mapping
mechanism so that you won't have to type the full namespace every
time. Events don't have that.

With Events you'd always be writing:

someEventFunction(..., "http://example.com/myNamespace", "myEvent", ...);

With the proposed changed you'd instead write:

someEventFunction(..., "http://example.com/myNamespace/myEvent", ...);

where 'someEventFunction' is initEvent, addEventListener,
removeEventListener etc.

So on the whole not that big of a difference.

/ Jonas
Received on Saturday, 19 September 2009 20:29:14 GMT

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