This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In Section 4.8.10.11.2, the table in step 2 of "report the controller state" describing readyState events doesn't match the table in Section 4.8.10.17 for Media Controller events. The former talks about the "readyState newly being X" and the latter talks about the "readyState newly being X or greater".
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: This is not incorrect. One is talking about the minimum value amongst all the media elements, the other is talking about the actual values of all the media elements. So if the values are 1, 2, and 3, then the event for 1 will fire because that's the minimum value, but all the objects are newly 1 or greater (specifically, in one case 1, in one case 2, and in another case 3).
Having said that, maybe the events _should_ all fire in sequence when the state increments.
Checked in as WHATWG revision r6824. Check-in comment: For MediaController, we need to fire all the events when the state increases, otherwise scripts will miss steps when the network is particularly fast. http://html5.org/tools/web-apps-tracker?from=6823&to=6824