W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2011

html5/spec Overview.html,1.5340,1.5341

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 11 Oct 2011 23:09:08 +0000
To: public-html-commits@w3.org
Message-Id: <E1RDlRc-0000MF-Pv@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv1343

Modified Files:
	Overview.html 
Log Message:
Make the */*+xml handling be fallback handling, rather than overriding any registered handlers for specific XML types. (whatwg r6661)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5340
retrieving revision 1.5341
diff -u -d -r1.5340 -r1.5341
--- Overview.html	11 Oct 2011 22:58:34 -0000	1.5340
+++ Overview.html	11 Oct 2011 23:09:04 -0000	1.5341
@@ -46449,9 +46449,11 @@
      these steps.</dd>
 
      
-     <dt>Any type ending in "<code title="">+xml</code>"</dt> 
      <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> 
      <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
@@ -46475,7 +46477,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
Received on Tuesday, 11 October 2011 23:09:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 October 2011 23:09:13 GMT