This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18070 - Requiring a "plugin" for <embed> is not compatible with <embed> pointing to SVG
Summary: Requiring a "plugin" for <embed> is not compatible with <embed> pointing to SVG
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 16:21 UTC by contributor
Modified: 2013-06-07 22:08 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2012-07-18 16:21:08 UTC
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.
================================================================================
Comment 1 Travis Leithead [MSFT] 2013-06-07 22:08:38 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: Accepted
Change Description: Merged WHATWG Spec change into W3C

See: https://github.com/w3c/html/commit/9a563d5979c2f4e5a97c062d584de27e6ba5fe00