- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Jan 2012 23:15:08 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=10975
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
--- Comment #13 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-01-12 23:15:05 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:
I would recommend the following approaches:
* Don't allow people to upload content that isn't in the well-supported
format(s).
* If you really must, then first, realise that this is not what the feature was
designed for. But then, use script to detect the error condition (using the
onerror handler on <video> or <source> depending on what you're doing) and then
in that handler, replace the <video> element with the plugin.
* Alternatively, use <video> as the fallback to the plugin, instead of the
plugin as the fallback to the <video>.
Also, always provide the download link, don't hide it in the fallback.
--
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 Thursday, 12 January 2012 23:19:13 UTC