16662 2012-04-09 06:36:56 +0000 Feedback for the Audio and Video tags option section This standard offers many different options for what codecs to use, and as of April 8 2012, the implementations of the major browsers circumvent the purpose of a standard. Rendering the work of this com 2012-09-14 11:14:02 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor dave.null mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 66515 0 contributor 2012-04-09 06:36:56 +0000 Specification: http://www.w3.org/TR/html5/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Feedback for the Audio and Video tags option section This standard offers many different options for what codecs to use, and as of April 8 2012, the implementations of the major browsers circumvent the purpose of a standard. Rendering the work of this committee useless for these tags. As a developer I appreciate the work that the HTML WG have done, but I feel that in this section they have overlooked the fundamental purpose of a standard. That everything be done a standard way. As such the tags should require the default of a specific, universal codec. Whether that be open source, free software, or a proprietary option. I personally don't care which, so long as I can create media to that standard, and know that a standards compliant browser can display it. Not the current make 2 or in some cases 3 versions of the same media, and some browser detection script to determine which one needs to be served to the browser. Basically I am asking that the standard defines a standard. If they also want to include a mechanism for extending the options great... but then we are back to plugins. Which is what HTML5 was supposed to avoid. Oh wait. WebM is a plugin... Posted from: 96.48.151.28 User agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0 70316 1 contributor 2012-07-18 07:18:30 +0000 This bug was cloned to create bug 17927 as part of operation convergence. 73891 2 robin 2012-09-14 11:14:02 +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 Rationale: It would be a great world in which we had just the one universal video codec. Achieving that is however beyond the reach of the HTML WG at this point.