- From: <bugzilla@jessica.w3.org>
- Date: Fri, 24 Jun 2011 21:15:50 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12957 Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NEEDSINFO --- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-06-24 21:15:49 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: Additional Information Needed Change Description: no spec change Rationale: ODFs and PDFs can already be included using <object>. <img>, <canvas>, and <audio> all have special features that are specific to the media type that are not available using just <object>. What are you seeking to gain by introducing a new tag? Browsers can already implement their own ODF or PDF viewers or editors directly in the browser, and use those to handle <object> -- it doesn't need its own tag for that. We'd only need a special tag if we wanted to have special standardized behavior, like attributes or methods that only make sense for PDF/ODF. If you want browsers to implement in-browser viewing or editing of PDF or ODF in <object> tags, rather than requiring the use of plugins, I encourage you to communicate directly with the implementers of the browsers in question. -- 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 Friday, 24 June 2011 21:15:51 UTC