This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
HTML5 fires a DOMContentLoaded event. [1] It would probably be useful to define it in DOM3Events. [1] http://www.whatwg.org/html5/#stop-parsing
What exactly needs to be defined?
Assigning to myself to take action on these open bugs.
Starting from HTML5, section 8.2.6 (http://dev.w3.org/html5/spec/Overview.html#the-end), I see the definition of an event type named "DOMContentLoaded". That section calls it a "simple event". Looking at the definition for simple event (http://dev.w3.org/html5/spec/Overview.html#fire-a-simple-event), it looks like it is (swapping out variables): "an event with the name [DOMContentLoade], <del>which does not bubble</del> (except where otherwise stated [it *is* stated]) and is not cancelable <del>(except where otherwise stated)</del>, and which uses the Event interface, must be created and dispatched at the given target [Document]." So this is just a regular Event, which is defined in DOM3 Events and DOM4. My conclusion is that this is a satisfactory definition of DOMContentLoaded.
Agreed; thank you.