[html5] r6661 - [giow] (0) Make the */*+xml handling be fallback handling, rather than overridin [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-10-11 16:05:42 -0700 (Tue, 11 Oct 2011)
New Revision: 6661

Modified:
   complete.html
   index
   source
Log:
[giow] (0) Make the */*+xml handling be fallback handling, rather than overriding any registered handlers for specific XML types.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13882

Modified: complete.html
===================================================================
--- complete.html	2011-10-11 22:55:10 UTC (rev 6660)
+++ complete.html	2011-10-11 23:05:42 UTC (rev 6661)
@@ -64862,9 +64862,11 @@
      these steps.</dd>
 
      <!-- an <span>XML MIME type</span> -->
-     <dt>Any type ending in "<code title="">+xml</code>"</dt> <!-- no need to say that the _subtype_ ends in "+xml" so long as the "sniffed type" algorithm continues to drop parameters -->
      <dt>"<code>application/xml</code>"</dt>
      <dt>"<code>text/xml</code>"</dt>
+     <dt>"<code>image/svg+xml</code>"</dt>
+     <dt>"<code><a href=#application/xhtml+xml>application/xhtml+xml</a></code>"</dt>
+     <dt>Any other type ending in "<code title="">+xml</code>" that is not an <a href=#explicitly-supported-xml-type>explicitly supported XML type</a></dt> <!-- no need to say that the _subtype_ ends in "+xml" so long as the "sniffed type" algorithm continues to drop parameters -->
      <dd>Follow the steps given in the <a href=#read-xml title=navigate-xml>XML
      document</a> section. If that section determines that the
      content is <em>not</em> to be displayed as a generic XML
@@ -64888,7 +64890,18 @@
      <dd>Follow the steps given in the <a href=#read-plugin title=navigate-plugin>plugin</a> section, and abort these
      steps.</dd>
 
-    </dl><p><dfn id="set-the-document's-address" title="set the document's address">Setting the document's
+    </dl><p>An <dfn id=explicitly-supported-xml-type>explicitly supported XML type</dfn> is one for which
+    the user agent is configured to use an external application to
+    render the content (either a <a href=#plugin>plugin</a> rendering
+    directly in the <a href=#browsing-context>browsing context</a>, or a separate
+    application), or one for which the user agent has dedicated
+    processing rules (e.g. a Web browser with a built-in Atom feed
+    viewer would be said to explicitly support the
+    <code>application/atom+xml</code> MIME type), or one for which the
+    user agent has a dedicated handler (e.g. one registered using
+    <code title=dom-navigator-registerContentHandler><a href=#dom-navigator-registercontenthandler>registerContentHandler()</a></code>).</p>
+
+    <p><dfn id="set-the-document's-address" title="set the document's address">Setting the document's
     address</dfn>: If there is no <dfn id=override-url>override URL</dfn>, then any
     <code><a href=#document>Document</a></code> created by these steps must have its <a href="#the-document's-address" title="the document's address">address</a> set to the
     <a href=#url>URL</a> that was originally to be <a href=#fetch title=fetch>fetched</a>, ignoring any other data that was

Modified: index
===================================================================
--- index	2011-10-11 22:55:10 UTC (rev 6660)
+++ index	2011-10-11 23:05:42 UTC (rev 6661)
@@ -64862,9 +64862,11 @@
      these steps.</dd>
 
      <!-- an <span>XML MIME type</span> -->
-     <dt>Any type ending in "<code title="">+xml</code>"</dt> <!-- no need to say that the _subtype_ ends in "+xml" so long as the "sniffed type" algorithm continues to drop parameters -->
      <dt>"<code>application/xml</code>"</dt>
      <dt>"<code>text/xml</code>"</dt>
+     <dt>"<code>image/svg+xml</code>"</dt>
+     <dt>"<code><a href=#application/xhtml+xml>application/xhtml+xml</a></code>"</dt>
+     <dt>Any other type ending in "<code title="">+xml</code>" that is not an <a href=#explicitly-supported-xml-type>explicitly supported XML type</a></dt> <!-- no need to say that the _subtype_ ends in "+xml" so long as the "sniffed type" algorithm continues to drop parameters -->
      <dd>Follow the steps given in the <a href=#read-xml title=navigate-xml>XML
      document</a> section. If that section determines that the
      content is <em>not</em> to be displayed as a generic XML
@@ -64888,7 +64890,18 @@
      <dd>Follow the steps given in the <a href=#read-plugin title=navigate-plugin>plugin</a> section, and abort these
      steps.</dd>
 
-    </dl><p><dfn id="set-the-document's-address" title="set the document's address">Setting the document's
+    </dl><p>An <dfn id=explicitly-supported-xml-type>explicitly supported XML type</dfn> is one for which
+    the user agent is configured to use an external application to
+    render the content (either a <a href=#plugin>plugin</a> rendering
+    directly in the <a href=#browsing-context>browsing context</a>, or a separate
+    application), or one for which the user agent has dedicated
+    processing rules (e.g. a Web browser with a built-in Atom feed
+    viewer would be said to explicitly support the
+    <code>application/atom+xml</code> MIME type), or one for which the
+    user agent has a dedicated handler (e.g. one registered using
+    <code title=dom-navigator-registerContentHandler><a href=#dom-navigator-registercontenthandler>registerContentHandler()</a></code>).</p>
+
+    <p><dfn id="set-the-document's-address" title="set the document's address">Setting the document's
     address</dfn>: If there is no <dfn id=override-url>override URL</dfn>, then any
     <code><a href=#document>Document</a></code> created by these steps must have its <a href="#the-document's-address" title="the document's address">address</a> set to the
     <a href=#url>URL</a> that was originally to be <a href=#fetch title=fetch>fetched</a>, ignoring any other data that was

Modified: source
===================================================================
--- source	2011-10-11 22:55:10 UTC (rev 6660)
+++ source	2011-10-11 23:05:42 UTC (rev 6661)
@@ -73641,9 +73641,11 @@
      these steps.</dd>
 
      <!-- an <span>XML MIME type</span> -->
-     <dt>Any type ending in "<code title="">+xml</code>"</dt> <!-- no need to say that the _subtype_ ends in "+xml" so long as the "sniffed type" algorithm continues to drop parameters -->
      <dt>"<code>application/xml</code>"</dt>
      <dt>"<code>text/xml</code>"</dt>
+     <dt>"<code>image/svg+xml</code>"</dt>
+     <dt>"<code>application/xhtml+xml</code>"</dt>
+     <dt>Any other type ending in "<code title="">+xml</code>" that is not an <span>explicitly supported XML type</span></dt> <!-- no need to say that the _subtype_ ends in "+xml" so long as the "sniffed type" algorithm continues to drop parameters -->
      <dd>Follow the steps given in the <span title="navigate-xml">XML
      document</span> section. If that section determines that the
      content is <em>not</em> to be displayed as a generic XML
@@ -73673,6 +73675,18 @@
 
     </dl>
 
+    <p>An <dfn>explicitly supported XML type</dfn> is one for which
+    the user agent is configured to use an external application to
+    render the content (either a <span>plugin</span> rendering
+    directly in the <span>browsing context</span>, or a separate
+    application), or one for which the user agent has dedicated
+    processing rules (e.g. a Web browser with a built-in Atom feed
+    viewer would be said to explicitly support the
+    <code>application/atom+xml</code> MIME type), or one for which the
+    user agent has a dedicated handler (e.g. one registered using
+    <code
+    title="dom-navigator-registerContentHandler">registerContentHandler()</code>).</p>
+
     <p><dfn title="set the document's address">Setting the document's
     address</dfn>: If there is no <dfn>override URL</dfn>, then any
     <code>Document</code> created by these steps must have its <span