This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
With the exception of DOMContentLoaded, all current event types defined for use in HTML5 are lower-cased, unhyphenated. As such DOMContentLoaded is the sole exception to this convention. It would be useful to change this to maintain a consistent naming convention. Perhaps this could be renamed, for example, to "contentloaded"? This comment is in reference to Editor's Draft of 11 July 2011.
misfiled against wrong component, change to HTML5 spec component
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Test case: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1069 IE10PP2, Firefox 7.0a2, and Chrome 14 dev all support only "DOMContentLoaded". Opera 11.50 supports "DOMContentLoaded" and "domcontentloaded", but not "contentloaded". Thus the spec matches browsers, so it seems correct. Changing already-deployed features like this can only be done with really good reason, which I don't see here.
ok, i accept, but it's a shame that this one inconsistency stands out
mass-moved component to LC1