- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 16 Feb 2010 08:38:34 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8928 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NEEDSINFO Summary|A listing of which events |A listing of which events |were fired on which |were fired on which |elements, and at what times,|elements, and at what times, |would be extremely useful. |would be extremely useful. |For instance |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|the table in | |http://www.whatwg.org/specs/| |web-apps/current- | |work/multipage/section- | |index.html#events-0 claims | |that the volumechange event | |is | --- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-02-16 08:38:33 --- 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 -- 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 Tuesday, 16 February 2010 08:38:35 UTC