This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8928 - 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
Summary: A listing of which events were fired on which elements, and at what times, wo...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-10 09:47 UTC by contributor
Modified: 2010-10-04 14:49 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-02-10 09:47:59 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2010-02-16 08:38:33 UTC 
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