[Bug 16662] New: 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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16662

           Summary: 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
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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

-- 
Configure bugmail: https://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 Monday, 9 April 2012 06:37:02 UTC