This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html Section: http://www.whatwg.org/specs/web-apps/current-work/#getting-media-metadata Comment: <video> define exact order and state during the last progress event Posted from: 83.218.67.122 User agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.8.131 Version/11.10
Somewhat related to http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267 "Once the entire media resource has been fetched (but potentially before any of it has been decoded) Queue a task to fire a simple event named progress at the media element." The details of this last progress event fired because the entire media resource has been fetched is not so clear. After the state changes and events are made to be in sync, the spec should require that it be fired while networkState is still LOADING, that is before the suspend event. Additionally, this should happen not only when the entire resource has been fetched, but any time that buffering has stopped, e.g. due to preload buffering strategy.
To clarify, I was assuming in the previous comment that the requested change in http://www.w3.org/Bugs/Public/show_bug.cgi?id=12595 will be made, so that the suspend event does in fact fire in this situation.
I don't understand. Order relative to what, exactly?
It's not defined what networkState is while the event is handled. Assuming that I get my way with http://www.w3.org/Bugs/Public/show_bug.cgi?id=12595 it must also be defined that this last progress event is fired before the suspend event.
mass-moved component to LC1
The order relative to the 'suspend' event is now defined. 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: Accepted Change Description: see diff given below Rationale: Made networkState completely race-free relative to the progress and suspend events (and also error and emptied, I think, though I didn't check those closely). As a side-effect, this defined the order of networkState changes relative to the last 'progress' event.
Checked in as WHATWG revision r6545. Check-in comment: Make networkState changes have better-defined order relative to 'suspend' and 'progress' events. http://html5.org/tools/web-apps-tracker?from=6544&to=6545