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 17927 - 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
Summary: Feedback for the Audio and Video tags option section This standard offers man...
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 07:18 UTC by contributor
Modified: 2012-09-19 23:00 UTC (History)
2 users (show)

See Also:


Attachments

Description contributor 2012-07-18 07:18:27 UTC
This was was cloned from bug 16662 as part of operation convergence.
Originally filed: 2012-04-09 06:36:00 +0000

================================================================================
 #0   contributor@whatwg.org                          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
================================================================================
Comment 1 Ian 'Hixie' Hickson 2012-09-19 23:00:38 UTC
I agree. Which format do all the browser vendors agree to implement? I'd be happy to make the spec require such a format if there is one.