This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The following events defined in various parts of HTML5 are not listed in the Index (Events): activate bounce cached canplay canplaythrough checking cuechange dblclick downloading drag dragend dragenter dragleave dragover dragstart drop durationchange emptied ended enter exit finish keydown keypress keyup loadeddata loadedmetadata loadstart mousedown mousemove mouseout mouseover mouseup mousewheel noupdate obsolete pause play playing progress ratechange redo resize scroll seeked seeking select stalled start storage suspend timeupdate undo updateready volumechange waiting This comment is in reference to Editor's Draft of 11 July 2011.
mass-move component to LC1
A lot of those fall into one of four categories: - events defined in the media section, linked to from the appendix - events defined in the appcache section, linked to from the appendix - events defined in the d&d section, linked to from the appendix - events that should be defined in an Interaction Events specification (currently DOM3 Events) Are there any events in this list that do not fall into these categories?
Glenn, this bug is waiting for your response to comment #2: > A lot of those fall into one of four categories: > - events defined in the media section, linked to from the appendix > - events defined in the appcache section, linked to from the appendix > - events defined in the d&d section, linked to from the appendix > - events that should be defined in an Interaction Events specification > (currently DOM3 Events) > > Are there any events in this list that do not fall into these categories?
(In reply to comment #3) > Glenn, this bug is waiting for your response to comment #2: > > A lot of those fall into one of four categories: > > - events defined in the media section, linked to from the appendix > > - events defined in the appcache section, linked to from the appendix > > - events defined in the d&d section, linked to from the appendix > > - events that should be defined in an Interaction Events specification > > (currently DOM3 Events) > > > > Are there any events in this list that do not fall into these categories? Irrelevant. The appendix purports to by the "List of events". This is not qualified for category of event. It should list *all* events normatively defined by the specification. I have provided (in comment #1) a list of missing events based on my review on July 13, 2011. Perhaps it has changed since then. If desired I can re-review for missing events in this list.
(In reply to comment #4) > (In reply to comment #3) > > Glenn, this bug is waiting for your response to comment #2: > > > A lot of those fall into one of four categories: > > > - events defined in the media section, linked to from the appendix > > > - events defined in the appcache section, linked to from the appendix > > > - events defined in the d&d section, linked to from the appendix > > > - events that should be defined in an Interaction Events specification > > > (currently DOM3 Events) > > > > > > Are there any events in this list that do not fall into these categories? > > Irrelevant. The appendix purports to by the "List of events". This is not > qualified for category of event. It should list *all* events normatively > defined by the specification. > > I have provided (in comment #1) a list of missing events based on my review on > July 13, 2011. Perhaps it has changed since then. If desired I can re-review > for missing events in this list. I just noticed the "See also media element events, MediaStream and PeerConnection events, application cache events, and drag-and-drop events" note after the table. I'm not particularly satisfied with just a partial enumeration table in the index. I will submit (shortly) an update that incorporates these additional events into the table (and removes the redundant DOMContentLoaded entry).
I do not think it would be good to have to maintain multiple tables whenever I change the media events (e.g.). Also, note that not all these tables have the same set of columns. 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: I don't think we should do this. The current situation is fine, IMHO.