- From: Maciej Stachowiak <mjs@apple.com>
- Date: Mon, 4 Jun 2007 23:35:36 -0700
On Jun 4, 2007, at 9:25 PM, Ian Hickson wrote: > On Sat, 19 May 2007, Maciej Stachowiak wrote: >> >> May I suggest reproposing [DOMContentLoaded] for DOM 3 Events, then, >> since your former objection to it is withdrawn? > > I can if you want, but I don't really see it as a feature that > would be > expected in DOM3 Events. DOM Events defines the event > infrastructure; it > doesn't define when and how each event is actually fired. The > firing of > the events in HTML is very closely tied to the rest of the HTML > processing > model. It also defines the names of events, their associated IDL interfaces, whether they bubble, whether they are cancellable, and so forth. Admittedly it does not give useful formal conformance criteria for when to dispatch most of events. DOM 3 Events defines this for the "load" event for instance. It seems to me that "load" and "DOMContentLoaded" can both be defined in ways that are independent of the specific markup language, and are equally deserving of being in DOM 3 Events itself. Certainly in a user agent that supports multiple markup languages, you'd want DOMContentLoaded to be dispatched for all of them under the same conditions. Finally, the reason it was left out in the first place was largely due to presumed lack of use cases, not because it was believed to require language-specific processing rules. And that argument was accepted largely due to your support for it. So it would be good to at least present the new info. Regards, Maciej
Received on Monday, 4 June 2007 23:35:36 UTC