8928 2010-02-10 09:47:59 +0000 A listing of which events were fired on which elements, and at what times, would be extremely useful. For instance, the table in http://www.whatwg.org/specs/web-apps/current-work/multipage/section-index.html#events-0 claims that the volumechange event is 2010-10-04 14:49:29 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#global-attributes P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking wycats public-html-bugzilla oldest_to_newest 31712 0 contributor 2010-02-10 09:47:59 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#global-attributes Comment: A listing of which events were fired on which elements, and at what times, would be extremely useful. For instance, the table in http://www.whatwg.org/specs/web-apps/current-work/multipage/section-index.html #events-0 claims that the volumechange event is on "HTML Elements" when it's clearly limited to media elements Posted from: 64.134.222.102 32155 1 ian 2010-02-16 08:38:33 +0000 That's not saying that "volumechange" fires on HTML elements, it's saying that "onvolumechange", the attribute, is allowed on any HTML element. There is a separate table that lists 'volumechange' semantics: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#mediaevents It's linked to from the event table: http://www.whatwg.org/specs/web-apps/current-work/multipage/section-index.html#events-0 Those tables do say what events are fired on what elements. Is it sufficient? 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: Did Not Understand Request Change Description: no spec change Rationale: see above for query