- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 25 Feb 2010 09:15:05 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8731 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #24 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-02-25 09:15:05 --- 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: Partially Accepted Change Description: see diff given below Rationale: The described problem is valid. I went with: preload=none preload=metadata preload=auto I'm not convinced there's a need for more than that — I don't see how an author can know whether prebuffering the whole thing or prebuffering the minimum required for smooth playback with just-in-time download is best, since that seems to be entirely a client-side thing. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 25 February 2010 09:15:07 UTC