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 8730 - Buffering should not be a boolean "autobuffer" tag - but something along the lines of "buffermax= n%" There should also be a "no-cache" attribute - this will overcome expected objections from copyright holders
Summary: Buffering should not be a boolean "autobuffer" tag - but something along the ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
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: 2010-01-13 07:15 UTC by contributor
Modified: 2010-10-04 13:55 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-01-13 07:15:20 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#video

Comment:
Buffering should not be a boolean "autobuffer" tag - but something along the
lines of "buffermax= n%" There should also be a "no-cache" attribute - this
will overcome expected objections from copyright holders

Posted from: 81.82.208.61
Comment 1 Ian 'Hixie' Hickson 2010-02-12 12:50:38 UTC 
Since there's more discussion there, I'll deal with the first part of that (controlling what is buffered) as part of bug 8731.
Comment 2 Ian 'Hixie' Hickson 2010-02-12 12:51:45 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: Regarding the second part, you can already specify the caching behaviour using HTTP Cache-Control headers, so it doesn't seem that there's anything needed in HTML itself.