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 12312 - This says "The codecs parameter, which certain MIME types define, might be necessary to specify exactly how the resource is encoded." Is this completely up to the browser to decide? Are there any instructions for browsers on how to respond if the codecs a
Summary: This says "The codecs parameter, which certain MIME types define, might be ne...
Status: RESOLVED NEEDSINFO
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-03-16 03:36 UTC by contributor
Modified: 2011-08-04 05:16 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-03-16 03:36:57 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#attr-source-type

Comment:
This says "The codecs parameter, which certain MIME types define, might be
necessary to specify exactly how the resource is encoded." Is this completely
up to the browser to decide? Are there any instructions for browsers on how to
respond if the codecs are included incorrectly, or not at all? Seems a bit
vague, that's all.

Posted from: 70.31.9.131
User agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Comment 1 Ian 'Hixie' Hickson 2011-05-06 21:32:51 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: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. Could you elaborate? Is what up to the browser to decide?
Comment 2 Michael[tm] Smith 2011-08-04 05:16:12 UTC 
mass-move component to LC1