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 11884 - HAVE_ALL_DATA would be good for when the UA has finished downloading the entire media file. Also, a "loaded" or "progressend" event should be fired so users can know when a file has finished buffering.
Summary: HAVE_ALL_DATA would be good for when the UA has finished downloading the enti...
Status: RESOLVED WONTFIX
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:
Blocks:
 
Reported: 2011-01-27 04:26 UTC by contributor
Modified: 2011-08-04 05:14 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-01-27 04:26:20 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-ready-states

Comment:
HAVE_ALL_DATA would be good for when the UA has finished downloading the
entire media file. Also, a "loaded" or "progressend" event should be fired so
users can know when a file has finished buffering.

Posted from: 60.242.139.60
Comment 1 Robert O'Callahan (Mozilla) 2011-01-27 04:40:12 UTC 
What about UAs like Firefox that can dynamically evict portions of media data from the cache at any time, and will limit the amount of cached data so that large resources will never be fully loaded?

You can't depend on "loaded" ever firing (because a large resource might never all fit locally at once) and if it does fire you can't depend on it meaning anything (because some data might be evicted immediately afterward). So it's useless. Same goes for HAVE_ALL_DATA.
Comment 2 Ian 'Hixie' Hickson 2011-02-18 23:22:41 UTC 
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: Yeah, we intentionally didn't support this so that pages wouldn't depend on browsers ever getting to this state, since some never will.
Comment 3 Michael[tm] Smith 2011-08-04 05:14:57 UTC 
mass-move component to LC1