- From: <bugzilla@jessica.w3.org>
- Date: Tue, 13 Jan 2015 22:59:29 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27739 David Dorwin <ddorwin@google.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Depends on| |27740 --- Comment #2 from David Dorwin <ddorwin@google.com> --- The HTML5 media element spec has the following "change" events [1]: 1. durationchange: The duration attribute has just been updated. 2. ratechange: Either the defaultPlaybackRate or the playbackRate attribute has just been updated. 3. volumechange: Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned. The Timed text tracks section defines change and cuechange [2], which do not appear to be related to any specific attributes. Document's readystatechange event is fired when the readystate attribute changes [3]. In general, the pattern appears to be "<attribute-name>change" (or "attribute-category-name"). In that case, assuming we keep the attribute name "keyStatuses" as currently proposed in bug 27740, the event name should be "keystatuseschange". It's not easy to say, but it is easy to understand. [1] http://www.w3.org/TR/html5/embedded-content-0.html#mediaevents [2] http://www.w3.org/TR/html5/embedded-content-0.html#cue-events [3] Above http://www.w3.org/TR/html5/dom.html#dom-document-readystate -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 13 January 2015 22:59:31 UTC