W3C home > Mailing lists > Public > public-html-commits@w3.org > May 2009

html5/spec Overview.html,1.2282,1.2283

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 25 May 2009 22:10:49 +0000
To: public-html-commits@w3.org
Message-Id: <E1M8iNd-0005vF-7O@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv22751

Modified Files:
	Overview.html 
Log Message:
Clarify how registered handlers work a little. (bug 6457) (whatwg r3125)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2282
retrieving revision 1.2283
diff -u -d -r1.2282 -r1.2283
--- Overview.html	25 May 2009 02:35:01 -0000	1.2282
+++ Overview.html	25 May 2009 22:10:45 -0000	1.2283
@@ -44040,9 +44040,10 @@
     a url">resolve</a> the resulting URL, relative to the <a href="#script-s-base-url" title="script's base URL">base URL</a> of the <a href="#first-script">first
     script</a> at the time the <code title="dom-navigator-registerContentHandler"><a href="#dom-navigator-registercontenthandler">registerContentHandler()</a></code>
     or <code title="dom-navigator-registerProtocolHandler"><a href="#dom-navigator-registerprotocolhandler">registerProtocolHandler()</a></code>
-    methods were invoked, and then <a href="#fetch">fetch</a> the resulting
-    URL using the GET method (<a href="#concept-http-equivalent-get" title="concept-http-equivalent-get">or equivalent</a> for
-    non-HTTP URLs).</p>
+    methods were invoked, and then <a href="#navigate">navigate</a> an
+    appropriate <a href="#browsing-context">browsing context</a> to the resulting URL
+    using the GET method (<a href="#concept-http-equivalent-get" title="concept-http-equivalent-get">or
+    equivalent</a> for non-HTTP URLs).</p>
 
     <p>To get the escaped version of the <a href="#absolute-url">absolute URL</a> of
     the content in question, the user agent must replace every
@@ -46378,12 +46379,20 @@
    equivalent</a>, then <a href="#scroll-to-fragid" title="navigate-fragid">navigate to
    that fragment identifier</a> and abort these steps.</li>
 
-   <li><p>If the new resource is to be handled by displaying some sort
-   of inline content, e.g. an error message because the specified
-   scheme is not one of the supported protocols, or an inline prompt
-   to allow the user to select <a href="#dom-navigator-registerprotocolhandler" title="dom-navigator-registerProtocolHandler">a registered
-   handler</a> for the given scheme, then <a href="#read-ua-inline" title="navigate-ua-inline">display the inline content</a> and
-   abort these steps.</li>
+   <li>
+
+    <p>If the new resource is to be handled by displaying some sort of
+    inline content, e.g. an error message because the specified scheme
+    is not one of the supported protocols, or an inline prompt to
+    allow the user to select <a href="#dom-navigator-registerprotocolhandler" title="dom-navigator-registerProtocolHandler">a registered
+    handler</a> for the given scheme, then <a href="#read-ua-inline" title="navigate-ua-inline">display the inline content</a> and
+    abort these steps.</p>
+
+    <p class="note">In the case of a registered handler being used,
+    the algorithm will be reinvoked with a new URL to handle the
+    request.</p>
+
+   </li>
 
    <li><p>If the new resource is to be handled using a mechanism that
    does not affect the browsing context, e.g. ignoring the navigation
@@ -46585,13 +46594,20 @@
 
    </li>
 
-   <li id="navigate-non-Document"><p><i>Non-document content</i>: If,
-   given <var title="">type</var>, the new resource is to be handled
-   by displaying some sort of inline content, e.g. a native rendering
-   of the content, an error message because the specified type is not
-   supported, or an inline prompt to allow the user to select <a href="#dom-navigator-registercontenthandler" title="dom-navigator-registerContentHandler">a registered
-   handler</a> for the given type, then <a href="#read-ua-inline" title="navigate-ua-inline">display the inline content</a> and
-   abort these steps.</li>
+   <li id="navigate-non-Document">
+
+    <p><i>Non-document content</i>: If, given <var title="">type</var>, the new resource is to be handled by
+    displaying some sort of inline content, e.g. a native rendering of
+    the content, an error message because the specified type is not
+    supported, or an inline prompt to allow the user to select <a href="#dom-navigator-registercontenthandler" title="dom-navigator-registerContentHandler">a registered
+    handler</a> for the given type, then <a href="#read-ua-inline" title="navigate-ua-inline">display the inline content</a> and
+    abort these steps.</p>
+
+    <p class="note">In the case of a registered handler being used,
+    the algorithm will be reinvoked with a new URL to handle the
+    request.</p>
+
+   </li>
 
    <li><p>Otherwise, the document's <var title="">type</var> is such
    that the resource will not affect the browsing context,
Received on Monday, 25 May 2009 22:10:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 25 May 2009 22:11:00 GMT