- From: poot <cvsmail@w3.org>
- Date: Tue, 31 Mar 2009 10:50:13 +0900 (JST)
- To: public-html-diffs@w3.org
Define that <embed> and <applet> elements in <object> fallback do not instantiate plugins. (bug 6434) (whatwg r2929) http://www.w3.org/Bugs/Public/show_bug.cgi?id=6434 When the sandboxed plugins browsing context flag is set on the browsing context for which the applet element's document is the active document, and when the element has an ancestor object element that is not showing its fallback content, the element must be ignored (it represents nothing). http://people.w3.org/mike/diffs/html5/spec/Overview.1.2094.html#sandboxPluginApplet When the sandboxed plugins browsing context flag is set on the browsing context for which the embed element's document is the active document, then the user agent must render the embed element in a manner that conveys that the plugin was disabled. The user agent may offer the user the option to override the sandbox and instantiate the plugin anyway; if the user invokes such an option, the user agent must act as if the sandboxed plugins browsing context flag was not set for the purposes of this element. http://people.w3.org/mike/diffs/html5/spec/Overview.1.2094.html#sandboxPluginEmbed 11.1.1 The applet element http://people.w3.org/mike/diffs/html5/spec/Overview.1.2094.html#the-applet-element type http://people.w3.org/mike/diffs/html5/spec/Overview.1.2094.html#attr-embed-type http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2093&r2=1.2094&f=h http://html5.org/tools/web-apps-tracker?from=2928&to=2929 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2093 retrieving revision 1.2094 diff -u -d -r1.2093 -r1.2094 --- Overview.html 31 Mar 2009 01:28:36 -0000 1.2093 +++ Overview.html 31 Mar 2009 01:48:11 -0000 1.2094 @@ -15834,8 +15834,10 @@ <p>When the element is created with neither a <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute nor a <code title=attr-embed-type><a href=#attr-embed-type>type</a></code> attribute, and when attributes are removed such that neither attribute is present on the element - anymore, any plugins instantiated for the element must be removed, - and the <code><a href=#the-embed-element>embed</a></code> element represents nothing.</p> + anymore, and when the element has an ancestor <code><a href=#the-object-element>object</a></code> + element that is <em>not</em> showing its <a href=#fallback-content>fallback + content</a>, any plugins instantiated for the element must be + removed, and the <code><a href=#the-embed-element>embed</a></code> element represents nothing.</p> <p id=sandboxPluginEmbed>When the <a href=#sandboxed-plugins-browsing-context-flag>sandboxed plugins browsing context flag</a> is set on the <a href=#browsing-context>browsing context</a> for @@ -15859,10 +15861,13 @@ <p>When the element is created with a <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute, and whenever the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute is subsequently set, and whenever the <code title=attr-embed-type><a href=#attr-embed-type>type</a></code> attribute is set or removed while the element has a <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute, if the element is not - in a sandboxed browsing context, user agents must <a href=#resolve-a-url title="resolve a url">resolve</a> the value of the attribute, - relative to the element, and if that is successful, should - <a href=#fetch>fetch</a> the resulting <a href=#absolute-url>absolute URL</a>, find and - instantiate an appropriate <a href=#plugin>plugin</a> based on the <a href=#concept-embed-type title=concept-embed-type>content's type</a>, and hand that + in a sandboxed browsing context and not a descendant of an + <code><a href=#the-object-element>object</a></code> element that is not showing its <a href=#fallback-content>fallback + content</a>, the user agent must <a href=#resolve-a-url title="resolve a + url">resolve</a> the value of the attribute, relative to the + element, and if that is successful, should <a href=#fetch>fetch</a> the + resulting <a href=#absolute-url>absolute URL</a>, find and instantiate an + appropriate <a href=#plugin>plugin</a> based on the <a href=#concept-embed-type title=concept-embed-type>content's type</a>, and hand that <a href=#plugin>plugin</a> the content of the resource, replacing any previously instantiated plugin for the element. <!-- Note that this doesn't happen when the base URL changes. --></p> @@ -56632,11 +56637,13 @@ is obsoleted so that all extension frameworks (Java, .NET, Flash, etc) are handled in a consistent manner.</p> - <p id=sandboxPluginApplet>If the <a href=#sandboxed-plugins-browsing-context-flag>sandboxed plugins browsing - context flag</a> is set on the <a href=#browsing-context>browsing context</a> for - which the <code><a href=#the-applet-element>applet</a></code> element's document is the <a href=#active-document>active - document</a>, then the element must be ignored (it represents - nothing).</p> + <p id=sandboxPluginApplet>When the <a href=#sandboxed-plugins-browsing-context-flag>sandboxed plugins + browsing context flag</a> is set on the <a href=#browsing-context>browsing + context</a> for which the <code><a href=#the-applet-element>applet</a></code> element's document + is the <a href=#active-document>active document</a>, and when the element has an + ancestor <code><a href=#the-object-element>object</a></code> element that is <em>not</em> showing + its <a href=#fallback-content>fallback content</a>, the element must be ignored (it + represents nothing).</p> <p>Otherwise, <span class=XXX>define how the element works, if supported</span>.</p>
Received on Tuesday, 31 March 2009 01:50:50 UTC