[Bug 10975] from gmail, JimJJewett said: Audio and Video should show the fallback content (for older browsers) if they do not understand the codec -- even if they understand video (or audio) itself

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10975

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-12 07:35:25 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: Not showing fallback content in browsers that support <video> is an
explicit design choice motivated by the eventual agreement on a single codec,
at which point this situation won't arise. It is unfortunate that we have not
yet been able to find a common codec, but in practice the market will almost
certainly resolve that long before this specification is done.

-- 
Configure bugmail: http://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 Tuesday, 12 October 2010 07:35:27 UTC