[Bug 13237] inconsistency in event name convention - DOMContentLoaded

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13237

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |Simetrical+w3cbug@gmail.com
         Resolution|                            |WONTFIX

--- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-13 22:26:58 UTC ---
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.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 13 July 2011 22:27:00 UTC