W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: publish a new Working Draft of DOM Core; comment deadline March 2

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 01 Mar 2011 15:05:04 +0100
To: "Adrian Bateman" <adrianba@microsoft.com>, "Garrett Smith" <dhtmlkitchen@gmail.com>
Cc: "Arthur Barstow" <art.barstow@nokia.com>, public-webapps <public-webapps@w3.org>, "Michael Champion" <Michael.Champion@microsoft.com>
Message-ID: <op.vrn32qig64w2qv@anne-van-kesterens-macbook-pro.local>
On Mon, 28 Feb 2011 18:49:48 +0100, Garrett Smith <dhtmlkitchen@gmail.com>  
wrote:
> | DOM Core defines the event and document model the Web platform uses.
>
> That says that DOM Core defines two different things: events and DOM.
> Some things might implement DOM Events Core (or a subinterface
> thereof) but are unrelated to the DOM. Like XHR.
>
> Could Events Core exist on its own? (You could make DOM Core
> conformance require Events Core conformance).

These are the reasons they are intertwined:

  * document.createEvent()
  * mutation events
  * we want Node to inherit from EventTarget
  * both events and documents depend on the same tree concept
  * INVALID_STATE_ERR is shared

Of course, given a mutual dependency they could be split, but I do not  
really see the point. Should the "Exceptions" section be split out too in  
your opinion? Given that "Events" and "Exceptions" are quite short and per  
the above summary quite integral to how everything fits together I think  
the current division makes sense.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Tuesday, 1 March 2011 14:05:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT