11884 2011-01-27 04:26:20 +0000 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. 2011-08-04 05:14:57 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#the-ready-states P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking roc public-html-bugzilla oldest_to_newest 44785 0 contributor 2011-01-27 04:26:20 +0000 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 44786 1 roc 2011-01-27 04:40:12 +0000 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. 45842 2 ian 2011-02-18 23:22:41 +0000 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. 53546 3 mike 2011-08-04 05:14:57 +0000 mass-move component to LC1