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 12608 - <video> define exact order and state during the last progress event
Summary: <video> define exact order and state during the last progress event
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on: 12267 12595
Blocks:
  Show dependency treegraph
 
Reported: 2011-05-05 12:57 UTC by contributor
Modified: 2011-09-08 22:01 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2011-05-05 12:57:49 UTC
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
Comment 1 Philip Jägenstedt 2011-05-05 13:06:05 UTC
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.
Comment 2 Philip Jägenstedt 2011-05-05 13:08:05 UTC
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.
Comment 3 Ian 'Hixie' Hickson 2011-08-03 00:08:49 UTC
I don't understand. Order relative to what, exactly?
Comment 4 Philip Jägenstedt 2011-08-03 14:48:27 UTC
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.
Comment 5 Michael[tm] Smith 2011-08-04 05:01:24 UTC
mass-moved component to LC1
Comment 6 Ian 'Hixie' Hickson 2011-09-08 21:52:08 UTC
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.
Comment 7 Ian 'Hixie' Hickson 2011-09-08 22:01:45 UTC
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