18070 2012-07-18 16:21:08 +0000 Requiring a "plugin" for <embed> is not compatible with <embed> pointing to SVG 2013-06-07 22:08:38 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-embed-element P3 normal --- 1 contributor robin bzbarsky mike public-html-admin public-html-wg-issue-tracking robin travil public-html-bugzilla oldest_to_newest 70608 0 contributor 2012-07-18 16:21:08 +0000 This was was cloned from bug 16136 as part of operation convergence. Originally filed: 2012-02-27 16:46:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-02-27 16:46:54 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html Multipage: http://www.whatwg.org/C#the-embed-element Complete: http://www.whatwg.org/c#the-embed-element Comment: Requiring a "plugin" for <embed> is not compatible with <embed> pointing to SVG Posted from: 71.184.125.56 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0a1) Gecko/20120218 Firefox/13.0a1 ================================================================================ #1 Boris Zbarsky 2012-02-27 16:50:32 +0000 -------------------------------------------------------------------------------- Specifically, I believe <embed> pointing to SVG creates a child browsing context in browsers, whereas the current spec text requires that no child browsing context ever be created for <embed>.... Gecko's behavior for <embed> is that it's only handled via plug-ins (in the "no child browsing context" sense, though they also happen to be NPAPI plug-ins) except for "image/svg+xml" when it creates a child browsing context. I haven't tested other browsers extensively to see what their behavior is. ================================================================================ 88926 1 travil 2013-06-07 22:08:38 +0000 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: Accepted Change Description: Merged WHATWG Spec change into W3C See: https://github.com/w3c/html/commit/9a563d5979c2f4e5a97c062d584de27e6ba5fe00