spec/Overview.html 1.1116 1925 Resolve the issue markers in the <embed>

Resolve the issue markers in the <embed> section. (whatwg r1925)

Diffs for this change per section: 
  type of the content
  http://people.w3.org/mike/diffs/html5/spec/Overview.1.1116.html#type-of
  If 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.1116.html#sandboxPluginEmbed
  type
  http://people.w3.org/mike/diffs/html5/spec/Overview.1.1116.html#type4

Cumulative diff: http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1115&r2=1.1116&f=h

http://html5.org/tools/web-apps-tracker?from=1924&to=1925

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1115
retrieving revision 1.1116
diff -u -d -r1.1115 -r1.1116
--- Overview.html 24 Jul 2008 01:32:30 -0000 1.1115
+++ Overview.html 24 Jul 2008 02:02:15 -0000 1.1116
@@ -16493,44 +16493,37 @@
    disabled). User agents should convey the danger of overriding the sandbox
    to the user if an option to do so is provided.
 
-  <p>Otherwise, the <code title=attr-embed-src><a href="#src3">src</a></code>
-   attribute is present, and the element is not in a sandboxed browsing
-   context:
-
   <p>When the element is created with a <code title=attr-embed-src><a
    href="#src3">src</a></code> attribute, and whenever the <code
    title=attr-embed-src><a href="#src3">src</a></code> attribute is
-   subsequently set, user agents are expected to find an appropriate <a
-   href="#plugin">plugin</a> for the specified resource, based on the <a
-   href="#type-of" title=concept-embed-type>content's type</a>, and hand that
-   <a href="#plugin">plugin</a> the content of the resource, fetching it if
-   necessary. If the <a href="#plugin">plugin</a> supports a scriptable
-   interface, the <code><a
-   href="#htmlembedelement">HTMLEmbedElement</a></code> object representing
-   the element should expose that interfaces.</p>
-  <!-- Note that this
+   subsequently set, if the element is not in a sandboxed browsing context,
+   user agents should fetch the specified resource, find an appropriate <a
+   href="#plugin">plugin</a> it based on the <a href="#type-of"
+   title=concept-embed-type>content's type</a>, and hand that <a
+   href="#plugin">plugin</a> the content of the resource. <!-- Note that this
   doesn't happen when the base URL changes. -->
+   If the <a href="#plugin">plugin</a> supports a scriptable interface, the
+   <code><a href="#htmlembedelement">HTMLEmbedElement</a></code> object
+   representing the element should expose that interfaces.
 
   <p>Fetching the resource must <a href="#delays">delay the <code
    title=event-load>load</code> event</a>.
 
-  <p>The user agent should pass the names and values of all the attributes of
-   the <code><a href="#embed">embed</a></code> element that have no namespace
-   to the <a href="#plugin">plugin</a> used.
-
   <p>Any (namespace-less) attribute may be specified on the <code><a
    href="#embed">embed</a></code> element, so long as its name is <a
    href="#xml-compatible">XML-compatible</a>.
 
-  <p>The <code><a href="#embed">embed</a></code> element has no <a
-   href="#fallback">fallback content</a>. If the user agent can't display the
-   specified resource, e.g. because the given type is not supported, then the
-   user agent must use a default plugin for the content. (This default could
-   be as simple as saying "Unsupported Format", of course.)
+  <p>The user agent should pass the names and values of all the attributes of
+   the <code><a href="#embed">embed</a></code> element that have no namespace
+   to the <a href="#plugin">plugin</a> used.
 
   <p>The <dfn id=type4 title=attr-embed-type><code>type</code></dfn>
    attribute, if present, gives the MIME type of the linked resource. The
-   value must be a valid MIME type, optionally with parameters. <a
+   value must be a valid MIME type, optionally with parameters. If the
+   attribute is present, its value must specify the same type as the <a
+   href="#content-type5" title=Content-Type>explicit Content-Type
+   metadata</a> of the resource given by the <code title=attr-embed-src><a
+   href="#src3">src</a></code> attribute. <a
    href="#references">[RFC2046]</a>
 
   <p>The <dfn id=type-of title=concept-embed-type>type of the content</dfn>
@@ -16550,14 +16543,19 @@
     href="#plugin">plugin</a> for it.
   </ol>
 
-  <p class=big-issue>Should we instead say that the content-sniffing used for
-   top-level browsing contexts should apply here?
+  <p>Whether the resource is fetched successfully or not must be ignored when
+   determining the resource's type and when handing the resource to the
+   plugin.
 
-  <p class=big-issue>Should we require the type attribute to match the server
-   information?
+  <p class=note>This allows servers to return data for plugins even with
+   error responses (e.g. HTTP 500 Internal Server Error codes can still
+   contain plugin data).
 
-  <p class=big-issue>We should say that 404s, etc, don't affect whether the
-   resource is used or not. Not sure how to say it here though.
+  <p>The <code><a href="#embed">embed</a></code> element has no <a
+   href="#fallback">fallback content</a>. If the user agent can't display the
+   specified resource, e.g. because the given type is not supported, then the
+   user agent must use a default plugin for the content. (This default could
+   be as simple as saying "Unsupported Format", of course.)
 
   <p>The <code><a href="#embed">embed</a></code> element supports <a
    href="#dimension0">dimension attributes</a>.

Received on Thursday, 24 July 2008 02:30:19 UTC