[html5] r8269 - [e] (0) Update how we reference XHR Affected topics: DOM APIs

whatwg at whatwg.org whatwg at whatwg.org
Tue Nov 12 13:10:12 PST 2013


Author: ianh
Date: 2013-11-12 13:10:10 -0800 (Tue, 12 Nov 2013)
New Revision: 8269

Modified:
   complete.html
   index
   source
Log:
[e] (0) Update how we reference XHR
Affected topics: DOM APIs

Modified: complete.html
===================================================================
--- complete.html	2013-11-12 21:07:15 UTC (rev 8268)
+++ complete.html	2013-11-12 21:10:10 UTC (rev 8269)
@@ -3831,15 +3831,11 @@
 
    <dd>
 
-    <p>This specification references the XMLHttpRequest specification to define how the two
+    <p>This specification references the XMLHttpRequest specification to describe how the two
     specifications interact and to use its <code><a href=#progressevent>ProgressEvent</a></code> features. The following
     features and terms are defined in the XMLHttpRequest specification: <a href=#refsXHR>[XHR]</a></p>
 
-    <ul class=brief><li><dfn id=document-response-entity-body>Document response entity body</dfn>
-     <li><dfn id=xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</dfn>
-     <li><dfn id=xmlhttprequest-origin><code>XMLHttpRequest</code> origin</dfn>
-     <li><dfn id=xmlhttprequest-referrer-source><code>XMLHttpRequest</code> referrer source</dfn>
-
+    <ul class=brief><li><dfn id=xmlhttprequest><code>XMLHttpRequest</code></dfn>
      <li><dfn id=progressevent><code>ProgressEvent</code></dfn>
      <li><dfn id=fire-a-progress-event title="fire a progress event">Fire a progress event named <var title="">e</var></dfn>
 
@@ -51531,7 +51527,7 @@
 
     <p class=note>The definition of <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a>
     means that, amongst others, the following scripts will not execute: scripts in
-    <code>XMLHttpRequest</code>'s <code title=dom-XMLHttpRequest-responseXML>responseXML</code>
+    <code><a href=#xmlhttprequest>XMLHttpRequest</a></code>'s <code title=dom-XMLHttpRequest-responseXML>responseXML</code>
     documents, scripts in <code>DOMParser</code>-created documents, scripts in documents created by
     <code>XSLTProcessor</code>'s <code title=dom-XSLTProcessor-transformToDocument>transformToDocument</code> feature, and scripts
     that are first inserted by a script into a <code><a href=#document>Document</a></code> that was created using the
@@ -67978,7 +67974,7 @@
   application and user data, with the logic (markup, scripts, style sheets, images, etc) listed in
   the manifest and stored in the application cache, with a finite number of static HTML pages for
   the application, and with the application and user data stored in Web Storage or a client-side
-  Indexed Database, updated dynamically using Web Sockets, <code>XMLHttpRequest</code>, server-sent
+  Indexed Database, updated dynamically using Web Sockets, <code><a href=#xmlhttprequest>XMLHttpRequest</a></code>, server-sent
   events, or some other similar mechanism.</p>
 
   <p>This model results in a fast experience for the user: the application immediately loads, and
@@ -67996,7 +67992,7 @@
 
    <p>A news application designed for the application cache feature, however, would instead have the
    main page just consist of the logic, and would then have the main page fetch the data separately
-   from the server, e.g. using <code>XMLHttpRequest</code>.</p>
+   from the server, e.g. using <code><a href=#xmlhttprequest>XMLHttpRequest</a></code>.</p>
 
   </div>
 
@@ -78043,7 +78039,7 @@
   requests. Clients will reconnect if the connection is closed; a client can be told to stop
   reconnecting using the HTTP 204 No Content response code.</p>
 
-  <p>Using this API rather than emulating it using <code>XMLHttpRequest</code> or an
+  <p>Using this API rather than emulating it using <code><a href=#xmlhttprequest>XMLHttpRequest</a></code> or an
   <code><a href=#the-iframe-element>iframe</a></code> allows the user agent to make better use of network resources in cases where
   the user agent implementor and the network operator are able to coordinate in advance. Amongst
   other benefits, this can result in significant savings in battery life on portable devices. This
@@ -79986,12 +79982,12 @@
   <p><i>This section is non-normative.</i></p>
 
   <p>Continuing the example from the previous section, consider the contacts provider in particular.
-  While an initial implementation might have simply used <code>XMLHttpRequest</code> objects in the
+  While an initial implementation might have simply used <code><a href=#xmlhttprequest>XMLHttpRequest</a></code> objects in the
   service's <code><a href=#the-iframe-element>iframe</a></code>, an evolution of the service might instead want to use a <a href=#sharedworker title=SharedWorker>shared worker</a> with a single <code><a href=#websocket>WebSocket</a></code> connection.</p>
 
   <p>If the initial design used <code><a href=#messageport>MessagePort</a></code> objects to grant capabilities, or even just
   to allow multiple simultaneous independent sessions, the service implementation can switch from
-  the <code>XMLHttpRequest</code>s-in-each-<code><a href=#the-iframe-element>iframe</a></code> model to the
+  the <code><a href=#xmlhttprequest>XMLHttpRequest</a></code>s-in-each-<code><a href=#the-iframe-element>iframe</a></code> model to the
   shared-<code><a href=#websocket>WebSocket</a></code> model without changing the API at all: the ports on the service
   provider side can all be forwarded to the shared worker without it affecting the users of the API
   in the slightest.</p>
@@ -95562,7 +95558,7 @@
    <dt><dfn id=attr-datasrc title=attr-datasrc><code>datasrc</code></dfn> on <code><a href=#the-a-element>a</a></code>, <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-button-element>button</a></code>, <code><a href=#the-div-element>div</a></code>, <code><a href=#frame>frame</a></code>, <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-input-element>input</a></code>, <code><a href=#the-label-element>label</a></code>, <code><a href=#the-legend-element>legend</a></code>, <code><a href=#the-marquee-element>marquee</a></code>, <code><a href=#the-object-element>object</a></code>, <code><a href=#the-option-element>option</a></code>, <code><a href=#the-select-element>select</a></code>, <code><a href=#the-span-element>span</a></code>, <code><a href=#the-table-element>table</a></code>, and <code><a href=#the-textarea-element>textarea</a></code> elements</dt>
    <dt><dfn id=attr-datafld title=attr-datafld><code>datafld</code></dfn> on <code><a href=#the-a-element>a</a></code>, <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-button-element>button</a></code>, <code><a href=#the-div-element>div</a></code>, <code><a href=#the-fieldset-element>fieldset</a></code>, <code><a href=#frame>frame</a></code>, <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-input-element>input</a></code>, <code><a href=#the-label-element>label</a></code>, <code><a href=#the-legend-element>legend</a></code>, <code><a href=#the-marquee-element>marquee</a></code>, <code><a href=#the-object-element>object</a></code>, <code><a href=#the-param-element>param</a></code>, <code><a href=#the-select-element>select</a></code>, <code><a href=#the-span-element>span</a></code>, and <code><a href=#the-textarea-element>textarea</a></code> elements</dt>
    <dt><dfn id=attr-dataformatas title=attr-dataformatas><code>dataformatas</code></dfn> on <code><a href=#the-button-element>button</a></code>, <code><a href=#the-div-element>div</a></code>, <code><a href=#the-input-element>input</a></code>, <code><a href=#the-label-element>label</a></code>, <code><a href=#the-legend-element>legend</a></code>, <code><a href=#the-marquee-element>marquee</a></code>, <code><a href=#the-object-element>object</a></code>, <code><a href=#the-option-element>option</a></code>, <code><a href=#the-select-element>select</a></code>, <code><a href=#the-span-element>span</a></code>, and <code><a href=#the-table-element>table</a></code> elements</dt>
-   <dd><p>Use script and a mechanism such as <code>XMLHttpRequest</code> to populate the page dynamically. <a href=#refsXHR>[XHR]</a></dd>
+   <dd><p>Use script and a mechanism such as <code><a href=#xmlhttprequest>XMLHttpRequest</a></code> to populate the page dynamically. <a href=#refsXHR>[XHR]</a></dd>
 
    <dt><dfn id=attr-body-alink title=attr-body-alink><code>alink</code></dfn> on <code><a href=#the-body-element>body</a></code> elements</dt>
    <dt><dfn id=attr-body-bgcolor title=attr-body-bgcolor><code>bgcolor</code></dfn> on <code><a href=#the-body-element>body</a></code> elements</dt>

Modified: index
===================================================================
--- index	2013-11-12 21:07:15 UTC (rev 8268)
+++ index	2013-11-12 21:10:10 UTC (rev 8269)
@@ -3831,15 +3831,11 @@
 
    <dd>
 
-    <p>This specification references the XMLHttpRequest specification to define how the two
+    <p>This specification references the XMLHttpRequest specification to describe how the two
     specifications interact and to use its <code><a href=#progressevent>ProgressEvent</a></code> features. The following
     features and terms are defined in the XMLHttpRequest specification: <a href=#refsXHR>[XHR]</a></p>
 
-    <ul class=brief><li><dfn id=document-response-entity-body>Document response entity body</dfn>
-     <li><dfn id=xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</dfn>
-     <li><dfn id=xmlhttprequest-origin><code>XMLHttpRequest</code> origin</dfn>
-     <li><dfn id=xmlhttprequest-referrer-source><code>XMLHttpRequest</code> referrer source</dfn>
-
+    <ul class=brief><li><dfn id=xmlhttprequest><code>XMLHttpRequest</code></dfn>
      <li><dfn id=progressevent><code>ProgressEvent</code></dfn>
      <li><dfn id=fire-a-progress-event title="fire a progress event">Fire a progress event named <var title="">e</var></dfn>
 
@@ -51531,7 +51527,7 @@
 
     <p class=note>The definition of <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a>
     means that, amongst others, the following scripts will not execute: scripts in
-    <code>XMLHttpRequest</code>'s <code title=dom-XMLHttpRequest-responseXML>responseXML</code>
+    <code><a href=#xmlhttprequest>XMLHttpRequest</a></code>'s <code title=dom-XMLHttpRequest-responseXML>responseXML</code>
     documents, scripts in <code>DOMParser</code>-created documents, scripts in documents created by
     <code>XSLTProcessor</code>'s <code title=dom-XSLTProcessor-transformToDocument>transformToDocument</code> feature, and scripts
     that are first inserted by a script into a <code><a href=#document>Document</a></code> that was created using the
@@ -67978,7 +67974,7 @@
   application and user data, with the logic (markup, scripts, style sheets, images, etc) listed in
   the manifest and stored in the application cache, with a finite number of static HTML pages for
   the application, and with the application and user data stored in Web Storage or a client-side
-  Indexed Database, updated dynamically using Web Sockets, <code>XMLHttpRequest</code>, server-sent
+  Indexed Database, updated dynamically using Web Sockets, <code><a href=#xmlhttprequest>XMLHttpRequest</a></code>, server-sent
   events, or some other similar mechanism.</p>
 
   <p>This model results in a fast experience for the user: the application immediately loads, and
@@ -67996,7 +67992,7 @@
 
    <p>A news application designed for the application cache feature, however, would instead have the
    main page just consist of the logic, and would then have the main page fetch the data separately
-   from the server, e.g. using <code>XMLHttpRequest</code>.</p>
+   from the server, e.g. using <code><a href=#xmlhttprequest>XMLHttpRequest</a></code>.</p>
 
   </div>
 
@@ -78043,7 +78039,7 @@
   requests. Clients will reconnect if the connection is closed; a client can be told to stop
   reconnecting using the HTTP 204 No Content response code.</p>
 
-  <p>Using this API rather than emulating it using <code>XMLHttpRequest</code> or an
+  <p>Using this API rather than emulating it using <code><a href=#xmlhttprequest>XMLHttpRequest</a></code> or an
   <code><a href=#the-iframe-element>iframe</a></code> allows the user agent to make better use of network resources in cases where
   the user agent implementor and the network operator are able to coordinate in advance. Amongst
   other benefits, this can result in significant savings in battery life on portable devices. This
@@ -79986,12 +79982,12 @@
   <p><i>This section is non-normative.</i></p>
 
   <p>Continuing the example from the previous section, consider the contacts provider in particular.
-  While an initial implementation might have simply used <code>XMLHttpRequest</code> objects in the
+  While an initial implementation might have simply used <code><a href=#xmlhttprequest>XMLHttpRequest</a></code> objects in the
   service's <code><a href=#the-iframe-element>iframe</a></code>, an evolution of the service might instead want to use a <a href=#sharedworker title=SharedWorker>shared worker</a> with a single <code><a href=#websocket>WebSocket</a></code> connection.</p>
 
   <p>If the initial design used <code><a href=#messageport>MessagePort</a></code> objects to grant capabilities, or even just
   to allow multiple simultaneous independent sessions, the service implementation can switch from
-  the <code>XMLHttpRequest</code>s-in-each-<code><a href=#the-iframe-element>iframe</a></code> model to the
+  the <code><a href=#xmlhttprequest>XMLHttpRequest</a></code>s-in-each-<code><a href=#the-iframe-element>iframe</a></code> model to the
   shared-<code><a href=#websocket>WebSocket</a></code> model without changing the API at all: the ports on the service
   provider side can all be forwarded to the shared worker without it affecting the users of the API
   in the slightest.</p>
@@ -95562,7 +95558,7 @@
    <dt><dfn id=attr-datasrc title=attr-datasrc><code>datasrc</code></dfn> on <code><a href=#the-a-element>a</a></code>, <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-button-element>button</a></code>, <code><a href=#the-div-element>div</a></code>, <code><a href=#frame>frame</a></code>, <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-input-element>input</a></code>, <code><a href=#the-label-element>label</a></code>, <code><a href=#the-legend-element>legend</a></code>, <code><a href=#the-marquee-element>marquee</a></code>, <code><a href=#the-object-element>object</a></code>, <code><a href=#the-option-element>option</a></code>, <code><a href=#the-select-element>select</a></code>, <code><a href=#the-span-element>span</a></code>, <code><a href=#the-table-element>table</a></code>, and <code><a href=#the-textarea-element>textarea</a></code> elements</dt>
    <dt><dfn id=attr-datafld title=attr-datafld><code>datafld</code></dfn> on <code><a href=#the-a-element>a</a></code>, <code><a href=#the-applet-element>applet</a></code>, <code><a href=#the-button-element>button</a></code>, <code><a href=#the-div-element>div</a></code>, <code><a href=#the-fieldset-element>fieldset</a></code>, <code><a href=#frame>frame</a></code>, <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-input-element>input</a></code>, <code><a href=#the-label-element>label</a></code>, <code><a href=#the-legend-element>legend</a></code>, <code><a href=#the-marquee-element>marquee</a></code>, <code><a href=#the-object-element>object</a></code>, <code><a href=#the-param-element>param</a></code>, <code><a href=#the-select-element>select</a></code>, <code><a href=#the-span-element>span</a></code>, and <code><a href=#the-textarea-element>textarea</a></code> elements</dt>
    <dt><dfn id=attr-dataformatas title=attr-dataformatas><code>dataformatas</code></dfn> on <code><a href=#the-button-element>button</a></code>, <code><a href=#the-div-element>div</a></code>, <code><a href=#the-input-element>input</a></code>, <code><a href=#the-label-element>label</a></code>, <code><a href=#the-legend-element>legend</a></code>, <code><a href=#the-marquee-element>marquee</a></code>, <code><a href=#the-object-element>object</a></code>, <code><a href=#the-option-element>option</a></code>, <code><a href=#the-select-element>select</a></code>, <code><a href=#the-span-element>span</a></code>, and <code><a href=#the-table-element>table</a></code> elements</dt>
-   <dd><p>Use script and a mechanism such as <code>XMLHttpRequest</code> to populate the page dynamically. <a href=#refsXHR>[XHR]</a></dd>
+   <dd><p>Use script and a mechanism such as <code><a href=#xmlhttprequest>XMLHttpRequest</a></code> to populate the page dynamically. <a href=#refsXHR>[XHR]</a></dd>
 
    <dt><dfn id=attr-body-alink title=attr-body-alink><code>alink</code></dfn> on <code><a href=#the-body-element>body</a></code> elements</dt>
    <dt><dfn id=attr-body-bgcolor title=attr-body-bgcolor><code>bgcolor</code></dfn> on <code><a href=#the-body-element>body</a></code> elements</dt>

Modified: source
===================================================================
--- source	2013-11-12 21:07:15 UTC (rev 8268)
+++ source	2013-11-12 21:10:10 UTC (rev 8269)
@@ -2608,18 +2608,14 @@
 
    <dd>
 
-    <p>This specification references the XMLHttpRequest specification to define how the two
+    <p>This specification references the XMLHttpRequest specification to describe how the two
     specifications interact and to use its <code>ProgressEvent</code> features. The following
     features and terms are defined in the XMLHttpRequest specification: <a
     href="#refsXHR">[XHR]</a></p>
 
     <ul class="brief">
 
-     <li><dfn>Document response entity body</dfn>
-     <li><dfn><code>XMLHttpRequest</code> base URL</dfn>
-     <li><dfn><code>XMLHttpRequest</code> origin</dfn>
-     <li><dfn><code>XMLHttpRequest</code> referrer source</dfn>
-
+     <li><dfn><code>XMLHttpRequest</code></dfn>
      <li><dfn><code>ProgressEvent</code></dfn>
      <li><dfn data-x="fire a progress event">Fire a progress event named <var data-x="">e</var></dfn>
 




More information about the Commit-Watchers mailing list