[html5] r7263 - [e] (0) Misc cleanup Affected topics: Canvas, DOM APIs, HTML, Microdata, Video a [...]

whatwg at whatwg.org whatwg at whatwg.org
Thu Aug 23 17:23:12 PDT 2012


Author: ianh
Date: 2012-08-23 17:23:11 -0700 (Thu, 23 Aug 2012)
New Revision: 7263

Modified:
   complete.html
   index
   source
Log:
[e] (0) Misc cleanup
Affected topics: Canvas, DOM APIs, HTML, Microdata, Video and Audio, WebSocket API

Modified: complete.html
===================================================================
--- complete.html	2012-08-23 22:41:11 UTC (rev 7262)
+++ complete.html	2012-08-24 00:23:11 UTC (rev 7263)
@@ -246,7 +246,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 23 August 2012</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 24 August 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -1379,8 +1379,6 @@
         but for now we are living with them. --><h2 id=introduction><span class=secno>1 </span>Introduction</h2>
 
 
-
-
   <h3 id=abstract><span class=secno>1.1 </span>Where does this specification fit?</h3>
 
   <p>This specification defines a big part of the Web platform, in
@@ -1444,22 +1442,24 @@
   are specified using identical text, except for the following
   differences:</p><!--FORK-->
 
-  <ul><!--
-   <li>Instead of this section, the W3C HTML specification has a
-   different paragraph explaining the difference between the W3C and
-   WHATWG versions of HTML.</li>
---><!-- in the status section --><li>The W3C HTML specification lacks any of the fixes made to this
-   specification since late June 2012. (Specifically, <a href="http://html5.org/tools/web-apps-tracker?from=7147">changes
-   from revision r7148 onwards</a> have not yet been applied to the
-   W3C HTML specification.)</li>
+  <ul><li>The W3C HTML specification does not include this section.</li>
 
+   <li>The W3C HTML specification lacks some of the fixes made to this
+   specification since late June 2012. (Specifically, after <a href="http://html5.org/tools/web-apps-tracker?from=7147">revision
+   r7148</a> changes were only adopted into the W3C HTML specification
+   on a piecemeal basis.) No precise list of these difference
+   currently exists.</li>
+
    <li>The W3C HTML specification refers to the technology as HTML5,
    rather than just HTML.</li><!--VERSION-->
 
+<!--(dunno if the policies changed or something, but the examples in question actually are in the w3c copy at the moment)
    <li>Examples that use features from HTML5 are not present in the
    W3C specifications since the W3C specifications are published as
-   HTML4 due to <a href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
-   publication policies</a>.</li><!--HTML4POLICE-->
+   HTML4 due to <a
+   href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
+   publication policies</a>.</li>
+-->
 
    <li>The W3C HTML specification omits an example as part of a
    compromise intended to resolve larger issues of divergence between
@@ -1519,11 +1519,6 @@
    working group chair decision from June 2011</a>.</li><!--bug
    12906-->
 
-   <li>The W3C HTML specification contradicts the ARIA specification
-   because of a <a href=http://lists.w3.org/Archives/Public/public-html/2012Feb/0066.html>working
-   group chair request from February
-   2012</a>.</li><!--HIDDENARIA--><!--FORK-->
-
    <li>The W3C HTML specification does not define the term <a href=#rel-sidebar-hyperlink title=rel-sidebar-hyperlink>sidebar hyperlink</a>, forcing the
    definition of the <code title=rel-sidebar>sidebar</code> link
    type in the microformats wiki to rely on this copy of the spec
@@ -1550,6 +1545,26 @@
    place of "WebVTT file" in certain places, because of a <a href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0557.html>working
    group chair decision from March 2012</a>.</li>
 
+   <li>The W3C HTML specification redundantly repeats requirements
+   from the ARIA specification relating to the ARIA attributes, due to
+   a working group chair decision.</li>
+
+   <li>In the W3C 2D Context specification, the <code title=dom-context-2d-createPattern><a href=#dom-context-2d-createpattern>createPattern()</a></code>
+   method's definition treats a null second argument as the empty
+   string, like IE and WebKit, rather than as an unknown value, like
+   Opera and Firefox. (This specification treats it as an unknown
+   value, since there doesn't seem to be any value to treating it as
+   the empty string.)</li>
+
+   <li>The W3C HTML specification sometimes does not give the official
+   Unicode names of characters, due to a working group chair
+   decision.</li>
+
+   <li>The W3C HTML specification allows <code title=attr-hyperlink-rel><a href=#attr-hyperlink-rel>rel</a></code> attributes to contain
+   unregistered URLs as tokens, even though they are not treated as
+   URLs (e.g. they are handled case-insensitively), due to a working
+   group chair decision.</li>
+
   </ul><p>The following sections are only published in the WHATWG
   specifications and are not currently available anywhere else:</p>
 
@@ -3981,6 +3996,8 @@
      <li><dfn id=dom-element-id title=dom-Element-id><code>id</code></dfn> attribute</li>
      <li><dfn id=textcontent><code>textContent</code></dfn> attribute</li>
 
+     <li>The <dfn id=concept-node-insert title=concept-node-insert>insert</dfn> algorithm for nodes</li>
+
      <li><dfn id=event><code>Event</code></dfn> interface</li>
      <li><dfn id=eventtarget><code>EventTarget</code></dfn> interface</li>
      <li><dfn id=eventinit><code>EventInit</code></dfn> dictionary type</li>
@@ -4282,6 +4299,9 @@
     <dfn id=top-layer>top layer</dfn> concept, are used to define the rendering of
     the <code><a href=#the-dialog-element>dialog</a></code> element. <a href=#refsFULLSCREEN>[FULLSCREEN]</a>
 
+    <p>The term <dfn id=css-styling-attribute>CSS styling attribute</dfn> is defined in the
+    <cite>CSS Style Attributes</cite> specification. <a href=#refsCSSATTR>[CSSATTR]</a></p>
+
    </dd>
 
 
@@ -4330,13 +4350,45 @@
 
 <!--TOPIC:HTML-->
 
+
+   <dt>ARIA</dt>
+
+   <dd>
+
+    <p>The terms <dfn id=strong-native-semantics>strong native semantics</dfn> is used as defined
+    in the ARIA specification. The term <dfn id=default-implied-aria-semantics>default implied ARIA
+    semantics</dfn> has the same meaning as the term <i>implicit
+    WAI-ARIA semantics</i> as used in the ARIA specification. <a href=#refsARIA>[ARIA]</a></p>
+
+    <p>The <dfn id=attr-aria-role title=attr-aria-role><code>role</code></dfn> and
+    <code title="">aria-*</code> attributes are defined in the ARIA
+    specification. <a href=#refsARIA>[ARIA]</a></p>
+
+
+   </dd>
+
+
+   <dt>XMLHttpRequest</dt>
+
+   <dd>
+
+    <p>This specification references the XMLHttpRequest specification
+    to define how the two specifications interact. The terms
+    <dfn id=document-response-entity-body>document response entity body</dfn>,
+    <dfn id=xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</dfn>, and
+    <dfn id=xmlhttprequest-origin><code>XMLHttpRequest</code> origin</dfn> are defined in that
+    specification. <a href=#refsXHR>[XHR]</a></p>
+
+   </dd>
+
   </dl><p>This specification does not <em>require</em> support of any
   particular network protocol, style sheet language, scripting
-  language, or any of the DOM specifications beyond those described
-  above. However, the language described by this specification is
-  biased towards CSS as the styling language, JavaScript as the
-  scripting language, and HTTP as the network protocol, and several
-  features assume that those languages and protocols are in use.</p>
+  language, or any of the DOM specifications beyond those required in
+  the list above. However, the language described by this
+  specification is biased towards CSS as the styling language,
+  JavaScript as the scripting language, and HTTP as the network
+  protocol, and several features assume that those languages and
+  protocols are in use.</p>
 
   <p class=note>This specification might have certain additional
   requirements on character encodings, image formats, audio formats,
@@ -9457,7 +9509,7 @@
   <pre class=idl>interface <dfn id=htmlpropertiescollection>HTMLPropertiesCollection</dfn> : <a href=#htmlcollection>HTMLCollection</a> {
   // inherits <span title=dom-HTMLCollection-length>length</span> and <span title=dom-HTMLCollection-item>item</span>()
   legacycaller getter <a href=#propertynodelist>PropertyNodeList</a>? <a href=#dom-htmlpropertiescollection-nameditem title=dom-HTMLPropertiesCollection-namedItem>namedItem</a>(DOMString name); // overrides inherited namedItem()
-  readonly attribute <span>DOMString</span>[] <a href=#dom-htmlpropertiescollection-names title=dom-HTMLPropertiesCollection-names>names</a>;
+  readonly attribute DOMString[] <a href=#dom-htmlpropertiescollection-names title=dom-HTMLPropertiesCollection-names>names</a>;
 };
 
 typedef sequence<any> <dfn id=propertyvaluearray>PropertyValueArray</dfn>;
@@ -11033,7 +11085,7 @@
   requirements,</span> is the <code><a href=#htmlelement>HTMLElement</a></code> interface.</p>
 
   <pre class=idl>interface <dfn id=htmlelement>HTMLElement</dfn> : <a href=#element>Element</a> {
-  // <span>metadata attributes</span>
+  // metadata attributes
            attribute DOMString <a href=#dom-title title=dom-title>title</a>;
            attribute DOMString <a href=#dom-lang title=dom-lang>lang</a>;
            attribute boolean <a href=#dom-translate title=dom-translate>translate</a>;
@@ -11073,7 +11125,7 @@
   readonly attribute boolean? <a href=#dom-command-ro-commandchecked title=dom-command-ro-commandChecked>commandChecked</a>;<!-- v2COMMAND
   readonly attribute <span>HTMLCollection</span> <span title="dom-command-ro-commandTriggers">commandTriggers</span>;-->
 
-  // <span>styling</span>
+  // styling
   readonly attribute <a href=#cssstyledeclaration>CSSStyleDeclaration</a> <a href=#dom-style title=dom-style>style</a>;
 
   // <a href=#event-handler-idl-attributes>event handler IDL attributes</a>
@@ -11311,7 +11363,7 @@
   fine-grained interface than is otherwise possible with HTML elements
   and attributes, a set of <a href=#wai-aria title=WAI-ARIA>annotations for
   assistive technology products</a> can be specified (the ARIA
-  <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes).</p>
+  <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes).</p>
 
 
   <h5 id=the-id-attribute><span class=secno>3.2.3.1 </span>The <dfn title=attr-id><code>id</code></dfn> attribute</h5>
@@ -11886,7 +11938,7 @@
   <h5 id=the-style-attribute><span class=secno>3.2.3.8 </span>The <dfn title=attr-style><code>style</code></dfn> attribute</h5>
 
   <p>All <a href=#html-elements>HTML elements</a> may have the <code title=attr-style><a href=#the-style-attribute>style</a></code> content attribute set. This is a
-  <span>CSS styling attribute</span> as defined by the CSS Styling
+  <a href=#css-styling-attribute>CSS styling attribute</a> as defined by the CSS Styling
   Attribute Syntax specification. <a href=#refsCSSATTR>[CSSATTR]</a></p>
 
   <div class=impl>
@@ -13250,23 +13302,23 @@
 
   <h4 id=wai-aria><span class=secno>3.2.7 </span><dfn>WAI-ARIA</dfn></h4>
 
-  <p>Authors may use the ARIA <code title=attr-aria-role>role</code>
+  <p>Authors may use the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code>
   and <code title=attr-aria-*>aria-*</code> attributes on <a href=#html-elements>HTML
   elements</a>, in accordance with the requirements described in
   the ARIA specifications, except where these conflict with the
-  <span>strong native semantics</span>
+  <a href=#strong-native-semantics>strong native semantics</a>
 <!--FORK--><!--bug 11557-->
-  or are equal to the <span>default implied ARIA semantics</span>
+  or are equal to the <a href=#default-implied-aria-semantics>default implied ARIA semantics</a>
 <!--FORK--><!--bug 11557-->
   described below. These exceptions are intended to prevent authors
   from making assistive technology products report nonsensical states
   that do not represent the actual state of the document. <a href=#refsARIA>[ARIA]</a></p>
 
 <!--FORK--><!--bug 11557-->
-  <p>Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
+  <p>Authors must not set the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
   conflicts with the semantics described in the following table,
   except that the <code title=attr-aria-role-presentation>presentation</code> role may
-  always be used. Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes to values that match
+  always be used. Authors must not set the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes to values that match
   the <span>default implicit ARIA semantics</span> defined in the
   following two tables.</p>
 <!--FORK--><!--bug 11557-->
@@ -13280,7 +13332,7 @@
   <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
 
   <p class=note>The ARIA attributes defined in the ARIA
-  specifications, and the <span>strong native semantics</span> and
+  specifications, and the <a href=#strong-native-semantics>strong native semantics</a> and
   <span>default implicit ARIA semantics</span> defined below, do not
   have any effect on CSS pseudo-class matching, user interface
   modalities that don't use assistive technologies, or the default
@@ -13292,8 +13344,8 @@
 
   </div>
 
-  <p>The following table defines the <span>strong native
-  semantics</span> and corresponding <span>default implicit ARIA
+  <p>The following table defines the <a href=#strong-native-semantics>strong native
+  semantics</a> and corresponding <span>default implicit ARIA
   semantics</span> that apply to <a href=#html-elements>HTML elements</a>. Each
   language feature (element or attribute) in a cell in the first
   column implies the ARIA semantics (role, states, and/or properties)
@@ -13302,7 +13354,7 @@
   properties from all the rows must be combined.</span></p>
 
   <table id=table-aria-strong><thead><tr><th>Language feature
-     <th><span>Strong native semantics</span> and <span>default implied ARIA semantics</span>
+     <th><a href=#strong-native-semantics>Strong native semantics</a> and <a href=#default-implied-aria-semantics>default implied ARIA semantics</a>
 
    <tbody><tr><td><code><a href=#the-area-element>area</a></code> element that creates a <a href=#hyperlink>hyperlink</a>
      <td><code title=attr-aria-role-link>link</code> role
@@ -13665,10 +13717,10 @@
      <td>Role must be either <code title=attr-aria-role-document>document</code> or <code title=attr-aria-role-application>application</code>
 
   </table><p>The entry "<dfn id=concept-role-none title=concept-role-none>no role</dfn>", when
-  used as a <span title="strong native semantics">strong native
-  semantic</span>, means that no role other than <code title=attr-aria-role-presentation>presentation</code> can be used.
-  When used as a <span title="default implied ARIA semantics">default
-  implied ARIA semantic</span>, it means the user agent has no default
+  used as a <a href=#strong-native-semantics title="strong native semantics">strong native
+  semantic</a>, means that no role other than <code title=attr-aria-role-presentation>presentation</code> can be used.
+  When used as a <a href=#default-implied-aria-semantics title="default implied ARIA semantics">default
+  implied ARIA semantic</a>, it means the user agent has no default
   mapping to ARIA roles. (However, it probably will have its own
   mappings to the accessibility layer.)</p>
 
@@ -16545,7 +16597,7 @@
 
    <li>The <code><a href=#the-script-element>script</a></code> element is <a href=#in-a-document>in a
    <code>Document</code></a> and a node or document fragment is
-   <span title=concept-node-insert>inserted</span> into the
+   <a href=#concept-node-insert title=concept-node-insert>inserted</a> into the
    <code><a href=#the-script-element>script</a></code> element.</li>
 
    <li>The <code><a href=#the-script-element>script</a></code> element is <a href=#in-a-document>in a
@@ -29021,7 +29073,7 @@
   void <a href=#dom-media-pause title=dom-media-pause>pause</a>();
 
   // media controller
-           attribute <span>DOMString</span> <a href=#dom-media-mediagroup title=dom-media-mediaGroup>mediaGroup</a>;
+           attribute DOMString <a href=#dom-media-mediagroup title=dom-media-mediaGroup>mediaGroup</a>;
            attribute <a href=#mediacontroller>MediaController</a>? <a href=#dom-media-controller title=dom-media-controller>controller</a>;
 
   // controls
@@ -36568,14 +36620,14 @@
 dictionary <dfn id=hitregionoptions>HitRegionOptions</dfn> {
   <a href=#path>Path</a>? <span title=dom-HitRegionOptions-path>path</span> = null;
 <!--  <span>SVGMatrix</span>? <span title="dom-HitRegionOptions-transform">transform</span> = null;
--->  <span>DOMString</span> <span title=dom-HitRegionOptions-id>id</span> = "";
-  <span>DOMString</span>? <span title=dom-HitRegionOptions-parentID>parentID</span> = null;
-  <span>DOMString</span> <span title=dom-HitRegionOptions-cursor>cursor</span> = "inherit";
+-->  DOMString <span title=dom-HitRegionOptions-id>id</span> = "";
+  DOMString? <span title=dom-HitRegionOptions-parentID>parentID</span> = null;
+  DOMString <span title=dom-HitRegionOptions-cursor>cursor</span> = "inherit";
   // for control-backed regions:
   <a href=#element>Element</a>? <span title=dom-HitRegionOptions-control>control</span> = null;
   // for unbacked regions:
-  <span>DOMString</span>? <span title=dom-HitRegionOptions-label>label</span> = null;
-  <span>DOMString</span>? <span title=dom-HitRegionOptions-role>role</span> = null;
+  DOMString? <span title=dom-HitRegionOptions-label>label</span> = null;
+  DOMString? <span title=dom-HitRegionOptions-role>role</span> = null;
 };
 
 interface <dfn id=imagedata>ImageData</dfn> {
@@ -42666,7 +42718,7 @@
 
   <table><thead><tr><th>Feature
      <th>Indication
-   <tbody><tr><td>The use of the <code title=attr-aria-role>role</code> attribute with the value <code title=attr-aria-role-presentation>presentation</code>
+   <tbody><tr><td>The use of the <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> attribute with the value <code title=attr-aria-role-presentation>presentation</code>
      <td>Probably a layout table
     <tr><td>The use of the non-conforming <code title=attr-table-border><a href=#attr-table-border>border</a></code> attribute with the non-conforming value 0
      <td>Probably a layout table
@@ -77337,21 +77389,13 @@
   <h3 id=the-hidden-attribute><span class=secno>8.1 </span>The <dfn title=attr-hidden><code>hidden</code></dfn> attribute</h3>
 
   <p>All <a href=#html-elements>HTML elements</a> may have the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> content attribute set. The <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute is a <a href=#boolean-attribute>boolean
-  attribute</a>.
+  attribute</a>. When specified on an element, it indicates that
+  the element is not yet, or is no longer, directly relevant to the
+  page's current state, or that it is being used to declare content to
+  be reused by other parts of the page as opposed to being directly
+  accessed by the user. <span class=impl>User agents should not
+  render elements that have the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute specified.</span></p>
 
-<!--HIDDENARIA--><!--FORK-->
-
-  When specified on an element, it indicates that the element is not
-  yet, or is no longer, directly relevant to the page's current state,
-  or that it is being used to declare content to be reused by other
-  parts of the page as opposed to being directly accessed by the user.
-
-
-  <span class=impl>User agents should not render elements that have
-  the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute
-  specified.</span></p>
-
-
   <div class=example>
 
    <p>In the following skeletal example, the attribute is used to hide
@@ -77391,8 +77435,6 @@
   <!-- for example, "<a hidden href=#content>Skip to content</a>" would be inappropriate. -->
   <!-- (but only add that example if you first add some more good valid examples -->
 
-<!--HIDDENARIA--><!--FORK-->
-
   <p>Elements that are not themselves <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> must not <a href=#hyperlink>hyperlink</a> to
   elements that are <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code>. The <code title="">for</code> attributes of <code><a href=#the-label-element>label</a></code> and
   <code><a href=#the-output-element>output</a></code> elements that are not themselves <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> must similarly not refer to
@@ -77402,7 +77444,6 @@
   <p>Elements and scripts may, however, refer to elements that are
   <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> in other contexts.</p>
 
-
   <div class=example>
 
    <p>For example, it would be incorrect to use the <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute to link to a
@@ -77410,8 +77451,6 @@
    attribute. If the content is not applicable or relevant, then there
    is no reason to link to it.</p>
 
-<!--HIDDENARIA--><!--FORK-->
-
    <p>It would be fine, however, to use the ARIA <code title=attr-aria-describedby>aria-describedby</code> attribute to
    refer to descriptions that are themselves <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code>. While hiding the descriptions
    implies that they are not useful alone, they could be written in
@@ -77423,7 +77462,6 @@
    control could refer to a hidden <code><a href=#the-form-element>form</a></code> element using its
    <code title=attr-fae-form><a href=#attr-fae-form>form</a></code> attribute.</p>
 
-
   </div>
 
   <p>Elements in a section hidden by the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute are still active,
@@ -78954,7 +78992,7 @@
   void <a href=#dom-datatransfer-addelement title=dom-DataTransfer-addElement>addElement</a>(Element element);
 
   /* old interface */
-  readonly attribute <span>DOMString</span>[] <a href=#dom-datatransfer-types title=dom-DataTransfer-types>types</a>;
+  readonly attribute DOMString[] <a href=#dom-datatransfer-types title=dom-DataTransfer-types>types</a>;
   DOMString <a href=#dom-datatransfer-getdata title=dom-DataTransfer-getData>getData</a>(DOMString format);
   void <a href=#dom-datatransfer-setdata title=dom-DataTransfer-setData>setData</a>(DOMString format, DOMString data);
   void <a href=#dom-datatransfer-cleardata title=dom-DataTransfer-clearData>clearData</a>(optional DOMString format);
@@ -83315,10 +83353,10 @@
 
   <ul><li><p><code>XMLHttpRequest</code> and all interface objects and
    constructors defined by the XMLHttpRequest specifications, except
-   that the <span>document response entity body</span> must always be
-   null. The <span><code>XMLHttpRequest</code> base URL</span> is the
+   that the <a href=#document-response-entity-body>document response entity body</a> must always be
+   null. The <a href=#xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</a> is the
    <a href="#script's-base-url">script's base URL</a>; the
-   <span><code>XMLHttpRequest</code> origin</span> is the script's
+   <a href=#xmlhttprequest-origin><code>XMLHttpRequest</code> origin</a> is the script's
    <a href=#origin>origin</a>. <a href=#refsXHR>[XHR]</a></li>
 
    <li><p>The interface objects and constructors defined by this
@@ -85175,7 +85213,7 @@
 interface <dfn id=closeevent>CloseEvent</dfn> : <a href=#event>Event</a> {
   readonly attribute boolean <a href=#dom-closeevent-wasclean title=dom-CloseEvent-wasClean>wasClean</a>;
   readonly attribute unsigned short <a href=#dom-closeevent-code title=dom-CloseEvent-code>code</a>;
-  readonly attribute DOMString <span title=dom-WebSocket-reason>reason</span>;
+  readonly attribute DOMString <a href=#dom-closeevent-reason title=dom-CloseEvent-reason>reason</a>;
 };
 
 dictionary <dfn id=closeeventinit>CloseEventInit</dfn> : <a href=#eventinit>EventInit</a> {

Modified: index
===================================================================
--- index	2012-08-23 22:41:11 UTC (rev 7262)
+++ index	2012-08-24 00:23:11 UTC (rev 7263)
@@ -246,7 +246,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 23 August 2012</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 24 August 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -1379,8 +1379,6 @@
         but for now we are living with them. --><h2 id=introduction><span class=secno>1 </span>Introduction</h2>
 
 
-
-
   <h3 id=abstract><span class=secno>1.1 </span>Where does this specification fit?</h3>
 
   <p>This specification defines a big part of the Web platform, in
@@ -1444,22 +1442,24 @@
   are specified using identical text, except for the following
   differences:</p><!--FORK-->
 
-  <ul><!--
-   <li>Instead of this section, the W3C HTML specification has a
-   different paragraph explaining the difference between the W3C and
-   WHATWG versions of HTML.</li>
---><!-- in the status section --><li>The W3C HTML specification lacks any of the fixes made to this
-   specification since late June 2012. (Specifically, <a href="http://html5.org/tools/web-apps-tracker?from=7147">changes
-   from revision r7148 onwards</a> have not yet been applied to the
-   W3C HTML specification.)</li>
+  <ul><li>The W3C HTML specification does not include this section.</li>
 
+   <li>The W3C HTML specification lacks some of the fixes made to this
+   specification since late June 2012. (Specifically, after <a href="http://html5.org/tools/web-apps-tracker?from=7147">revision
+   r7148</a> changes were only adopted into the W3C HTML specification
+   on a piecemeal basis.) No precise list of these difference
+   currently exists.</li>
+
    <li>The W3C HTML specification refers to the technology as HTML5,
    rather than just HTML.</li><!--VERSION-->
 
+<!--(dunno if the policies changed or something, but the examples in question actually are in the w3c copy at the moment)
    <li>Examples that use features from HTML5 are not present in the
    W3C specifications since the W3C specifications are published as
-   HTML4 due to <a href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
-   publication policies</a>.</li><!--HTML4POLICE-->
+   HTML4 due to <a
+   href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
+   publication policies</a>.</li>
+-->
 
    <li>The W3C HTML specification omits an example as part of a
    compromise intended to resolve larger issues of divergence between
@@ -1519,11 +1519,6 @@
    working group chair decision from June 2011</a>.</li><!--bug
    12906-->
 
-   <li>The W3C HTML specification contradicts the ARIA specification
-   because of a <a href=http://lists.w3.org/Archives/Public/public-html/2012Feb/0066.html>working
-   group chair request from February
-   2012</a>.</li><!--HIDDENARIA--><!--FORK-->
-
    <li>The W3C HTML specification does not define the term <a href=#rel-sidebar-hyperlink title=rel-sidebar-hyperlink>sidebar hyperlink</a>, forcing the
    definition of the <code title=rel-sidebar>sidebar</code> link
    type in the microformats wiki to rely on this copy of the spec
@@ -1550,6 +1545,26 @@
    place of "WebVTT file" in certain places, because of a <a href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0557.html>working
    group chair decision from March 2012</a>.</li>
 
+   <li>The W3C HTML specification redundantly repeats requirements
+   from the ARIA specification relating to the ARIA attributes, due to
+   a working group chair decision.</li>
+
+   <li>In the W3C 2D Context specification, the <code title=dom-context-2d-createPattern><a href=#dom-context-2d-createpattern>createPattern()</a></code>
+   method's definition treats a null second argument as the empty
+   string, like IE and WebKit, rather than as an unknown value, like
+   Opera and Firefox. (This specification treats it as an unknown
+   value, since there doesn't seem to be any value to treating it as
+   the empty string.)</li>
+
+   <li>The W3C HTML specification sometimes does not give the official
+   Unicode names of characters, due to a working group chair
+   decision.</li>
+
+   <li>The W3C HTML specification allows <code title=attr-hyperlink-rel><a href=#attr-hyperlink-rel>rel</a></code> attributes to contain
+   unregistered URLs as tokens, even though they are not treated as
+   URLs (e.g. they are handled case-insensitively), due to a working
+   group chair decision.</li>
+
   </ul><p>The following sections are only published in the WHATWG
   specifications and are not currently available anywhere else:</p>
 
@@ -3981,6 +3996,8 @@
      <li><dfn id=dom-element-id title=dom-Element-id><code>id</code></dfn> attribute</li>
      <li><dfn id=textcontent><code>textContent</code></dfn> attribute</li>
 
+     <li>The <dfn id=concept-node-insert title=concept-node-insert>insert</dfn> algorithm for nodes</li>
+
      <li><dfn id=event><code>Event</code></dfn> interface</li>
      <li><dfn id=eventtarget><code>EventTarget</code></dfn> interface</li>
      <li><dfn id=eventinit><code>EventInit</code></dfn> dictionary type</li>
@@ -4282,6 +4299,9 @@
     <dfn id=top-layer>top layer</dfn> concept, are used to define the rendering of
     the <code><a href=#the-dialog-element>dialog</a></code> element. <a href=#refsFULLSCREEN>[FULLSCREEN]</a>
 
+    <p>The term <dfn id=css-styling-attribute>CSS styling attribute</dfn> is defined in the
+    <cite>CSS Style Attributes</cite> specification. <a href=#refsCSSATTR>[CSSATTR]</a></p>
+
    </dd>
 
 
@@ -4330,13 +4350,45 @@
 
 <!--TOPIC:HTML-->
 
+
+   <dt>ARIA</dt>
+
+   <dd>
+
+    <p>The terms <dfn id=strong-native-semantics>strong native semantics</dfn> is used as defined
+    in the ARIA specification. The term <dfn id=default-implied-aria-semantics>default implied ARIA
+    semantics</dfn> has the same meaning as the term <i>implicit
+    WAI-ARIA semantics</i> as used in the ARIA specification. <a href=#refsARIA>[ARIA]</a></p>
+
+    <p>The <dfn id=attr-aria-role title=attr-aria-role><code>role</code></dfn> and
+    <code title="">aria-*</code> attributes are defined in the ARIA
+    specification. <a href=#refsARIA>[ARIA]</a></p>
+
+
+   </dd>
+
+
+   <dt>XMLHttpRequest</dt>
+
+   <dd>
+
+    <p>This specification references the XMLHttpRequest specification
+    to define how the two specifications interact. The terms
+    <dfn id=document-response-entity-body>document response entity body</dfn>,
+    <dfn id=xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</dfn>, and
+    <dfn id=xmlhttprequest-origin><code>XMLHttpRequest</code> origin</dfn> are defined in that
+    specification. <a href=#refsXHR>[XHR]</a></p>
+
+   </dd>
+
   </dl><p>This specification does not <em>require</em> support of any
   particular network protocol, style sheet language, scripting
-  language, or any of the DOM specifications beyond those described
-  above. However, the language described by this specification is
-  biased towards CSS as the styling language, JavaScript as the
-  scripting language, and HTTP as the network protocol, and several
-  features assume that those languages and protocols are in use.</p>
+  language, or any of the DOM specifications beyond those required in
+  the list above. However, the language described by this
+  specification is biased towards CSS as the styling language,
+  JavaScript as the scripting language, and HTTP as the network
+  protocol, and several features assume that those languages and
+  protocols are in use.</p>
 
   <p class=note>This specification might have certain additional
   requirements on character encodings, image formats, audio formats,
@@ -9457,7 +9509,7 @@
   <pre class=idl>interface <dfn id=htmlpropertiescollection>HTMLPropertiesCollection</dfn> : <a href=#htmlcollection>HTMLCollection</a> {
   // inherits <span title=dom-HTMLCollection-length>length</span> and <span title=dom-HTMLCollection-item>item</span>()
   legacycaller getter <a href=#propertynodelist>PropertyNodeList</a>? <a href=#dom-htmlpropertiescollection-nameditem title=dom-HTMLPropertiesCollection-namedItem>namedItem</a>(DOMString name); // overrides inherited namedItem()
-  readonly attribute <span>DOMString</span>[] <a href=#dom-htmlpropertiescollection-names title=dom-HTMLPropertiesCollection-names>names</a>;
+  readonly attribute DOMString[] <a href=#dom-htmlpropertiescollection-names title=dom-HTMLPropertiesCollection-names>names</a>;
 };
 
 typedef sequence<any> <dfn id=propertyvaluearray>PropertyValueArray</dfn>;
@@ -11033,7 +11085,7 @@
   requirements,</span> is the <code><a href=#htmlelement>HTMLElement</a></code> interface.</p>
 
   <pre class=idl>interface <dfn id=htmlelement>HTMLElement</dfn> : <a href=#element>Element</a> {
-  // <span>metadata attributes</span>
+  // metadata attributes
            attribute DOMString <a href=#dom-title title=dom-title>title</a>;
            attribute DOMString <a href=#dom-lang title=dom-lang>lang</a>;
            attribute boolean <a href=#dom-translate title=dom-translate>translate</a>;
@@ -11073,7 +11125,7 @@
   readonly attribute boolean? <a href=#dom-command-ro-commandchecked title=dom-command-ro-commandChecked>commandChecked</a>;<!-- v2COMMAND
   readonly attribute <span>HTMLCollection</span> <span title="dom-command-ro-commandTriggers">commandTriggers</span>;-->
 
-  // <span>styling</span>
+  // styling
   readonly attribute <a href=#cssstyledeclaration>CSSStyleDeclaration</a> <a href=#dom-style title=dom-style>style</a>;
 
   // <a href=#event-handler-idl-attributes>event handler IDL attributes</a>
@@ -11311,7 +11363,7 @@
   fine-grained interface than is otherwise possible with HTML elements
   and attributes, a set of <a href=#wai-aria title=WAI-ARIA>annotations for
   assistive technology products</a> can be specified (the ARIA
-  <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes).</p>
+  <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes).</p>
 
 
   <h5 id=the-id-attribute><span class=secno>3.2.3.1 </span>The <dfn title=attr-id><code>id</code></dfn> attribute</h5>
@@ -11886,7 +11938,7 @@
   <h5 id=the-style-attribute><span class=secno>3.2.3.8 </span>The <dfn title=attr-style><code>style</code></dfn> attribute</h5>
 
   <p>All <a href=#html-elements>HTML elements</a> may have the <code title=attr-style><a href=#the-style-attribute>style</a></code> content attribute set. This is a
-  <span>CSS styling attribute</span> as defined by the CSS Styling
+  <a href=#css-styling-attribute>CSS styling attribute</a> as defined by the CSS Styling
   Attribute Syntax specification. <a href=#refsCSSATTR>[CSSATTR]</a></p>
 
   <div class=impl>
@@ -13250,23 +13302,23 @@
 
   <h4 id=wai-aria><span class=secno>3.2.7 </span><dfn>WAI-ARIA</dfn></h4>
 
-  <p>Authors may use the ARIA <code title=attr-aria-role>role</code>
+  <p>Authors may use the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code>
   and <code title=attr-aria-*>aria-*</code> attributes on <a href=#html-elements>HTML
   elements</a>, in accordance with the requirements described in
   the ARIA specifications, except where these conflict with the
-  <span>strong native semantics</span>
+  <a href=#strong-native-semantics>strong native semantics</a>
 <!--FORK--><!--bug 11557-->
-  or are equal to the <span>default implied ARIA semantics</span>
+  or are equal to the <a href=#default-implied-aria-semantics>default implied ARIA semantics</a>
 <!--FORK--><!--bug 11557-->
   described below. These exceptions are intended to prevent authors
   from making assistive technology products report nonsensical states
   that do not represent the actual state of the document. <a href=#refsARIA>[ARIA]</a></p>
 
 <!--FORK--><!--bug 11557-->
-  <p>Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
+  <p>Authors must not set the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
   conflicts with the semantics described in the following table,
   except that the <code title=attr-aria-role-presentation>presentation</code> role may
-  always be used. Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes to values that match
+  always be used. Authors must not set the ARIA <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code> attributes to values that match
   the <span>default implicit ARIA semantics</span> defined in the
   following two tables.</p>
 <!--FORK--><!--bug 11557-->
@@ -13280,7 +13332,7 @@
   <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
 
   <p class=note>The ARIA attributes defined in the ARIA
-  specifications, and the <span>strong native semantics</span> and
+  specifications, and the <a href=#strong-native-semantics>strong native semantics</a> and
   <span>default implicit ARIA semantics</span> defined below, do not
   have any effect on CSS pseudo-class matching, user interface
   modalities that don't use assistive technologies, or the default
@@ -13292,8 +13344,8 @@
 
   </div>
 
-  <p>The following table defines the <span>strong native
-  semantics</span> and corresponding <span>default implicit ARIA
+  <p>The following table defines the <a href=#strong-native-semantics>strong native
+  semantics</a> and corresponding <span>default implicit ARIA
   semantics</span> that apply to <a href=#html-elements>HTML elements</a>. Each
   language feature (element or attribute) in a cell in the first
   column implies the ARIA semantics (role, states, and/or properties)
@@ -13302,7 +13354,7 @@
   properties from all the rows must be combined.</span></p>
 
   <table id=table-aria-strong><thead><tr><th>Language feature
-     <th><span>Strong native semantics</span> and <span>default implied ARIA semantics</span>
+     <th><a href=#strong-native-semantics>Strong native semantics</a> and <a href=#default-implied-aria-semantics>default implied ARIA semantics</a>
 
    <tbody><tr><td><code><a href=#the-area-element>area</a></code> element that creates a <a href=#hyperlink>hyperlink</a>
      <td><code title=attr-aria-role-link>link</code> role
@@ -13665,10 +13717,10 @@
      <td>Role must be either <code title=attr-aria-role-document>document</code> or <code title=attr-aria-role-application>application</code>
 
   </table><p>The entry "<dfn id=concept-role-none title=concept-role-none>no role</dfn>", when
-  used as a <span title="strong native semantics">strong native
-  semantic</span>, means that no role other than <code title=attr-aria-role-presentation>presentation</code> can be used.
-  When used as a <span title="default implied ARIA semantics">default
-  implied ARIA semantic</span>, it means the user agent has no default
+  used as a <a href=#strong-native-semantics title="strong native semantics">strong native
+  semantic</a>, means that no role other than <code title=attr-aria-role-presentation>presentation</code> can be used.
+  When used as a <a href=#default-implied-aria-semantics title="default implied ARIA semantics">default
+  implied ARIA semantic</a>, it means the user agent has no default
   mapping to ARIA roles. (However, it probably will have its own
   mappings to the accessibility layer.)</p>
 
@@ -16545,7 +16597,7 @@
 
    <li>The <code><a href=#the-script-element>script</a></code> element is <a href=#in-a-document>in a
    <code>Document</code></a> and a node or document fragment is
-   <span title=concept-node-insert>inserted</span> into the
+   <a href=#concept-node-insert title=concept-node-insert>inserted</a> into the
    <code><a href=#the-script-element>script</a></code> element.</li>
 
    <li>The <code><a href=#the-script-element>script</a></code> element is <a href=#in-a-document>in a
@@ -29021,7 +29073,7 @@
   void <a href=#dom-media-pause title=dom-media-pause>pause</a>();
 
   // media controller
-           attribute <span>DOMString</span> <a href=#dom-media-mediagroup title=dom-media-mediaGroup>mediaGroup</a>;
+           attribute DOMString <a href=#dom-media-mediagroup title=dom-media-mediaGroup>mediaGroup</a>;
            attribute <a href=#mediacontroller>MediaController</a>? <a href=#dom-media-controller title=dom-media-controller>controller</a>;
 
   // controls
@@ -36568,14 +36620,14 @@
 dictionary <dfn id=hitregionoptions>HitRegionOptions</dfn> {
   <a href=#path>Path</a>? <span title=dom-HitRegionOptions-path>path</span> = null;
 <!--  <span>SVGMatrix</span>? <span title="dom-HitRegionOptions-transform">transform</span> = null;
--->  <span>DOMString</span> <span title=dom-HitRegionOptions-id>id</span> = "";
-  <span>DOMString</span>? <span title=dom-HitRegionOptions-parentID>parentID</span> = null;
-  <span>DOMString</span> <span title=dom-HitRegionOptions-cursor>cursor</span> = "inherit";
+-->  DOMString <span title=dom-HitRegionOptions-id>id</span> = "";
+  DOMString? <span title=dom-HitRegionOptions-parentID>parentID</span> = null;
+  DOMString <span title=dom-HitRegionOptions-cursor>cursor</span> = "inherit";
   // for control-backed regions:
   <a href=#element>Element</a>? <span title=dom-HitRegionOptions-control>control</span> = null;
   // for unbacked regions:
-  <span>DOMString</span>? <span title=dom-HitRegionOptions-label>label</span> = null;
-  <span>DOMString</span>? <span title=dom-HitRegionOptions-role>role</span> = null;
+  DOMString? <span title=dom-HitRegionOptions-label>label</span> = null;
+  DOMString? <span title=dom-HitRegionOptions-role>role</span> = null;
 };
 
 interface <dfn id=imagedata>ImageData</dfn> {
@@ -42666,7 +42718,7 @@
 
   <table><thead><tr><th>Feature
      <th>Indication
-   <tbody><tr><td>The use of the <code title=attr-aria-role>role</code> attribute with the value <code title=attr-aria-role-presentation>presentation</code>
+   <tbody><tr><td>The use of the <code title=attr-aria-role><a href=#attr-aria-role>role</a></code> attribute with the value <code title=attr-aria-role-presentation>presentation</code>
      <td>Probably a layout table
     <tr><td>The use of the non-conforming <code title=attr-table-border><a href=#attr-table-border>border</a></code> attribute with the non-conforming value 0
      <td>Probably a layout table
@@ -77337,21 +77389,13 @@
   <h3 id=the-hidden-attribute><span class=secno>8.1 </span>The <dfn title=attr-hidden><code>hidden</code></dfn> attribute</h3>
 
   <p>All <a href=#html-elements>HTML elements</a> may have the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> content attribute set. The <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute is a <a href=#boolean-attribute>boolean
-  attribute</a>.
+  attribute</a>. When specified on an element, it indicates that
+  the element is not yet, or is no longer, directly relevant to the
+  page's current state, or that it is being used to declare content to
+  be reused by other parts of the page as opposed to being directly
+  accessed by the user. <span class=impl>User agents should not
+  render elements that have the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute specified.</span></p>
 
-<!--HIDDENARIA--><!--FORK-->
-
-  When specified on an element, it indicates that the element is not
-  yet, or is no longer, directly relevant to the page's current state,
-  or that it is being used to declare content to be reused by other
-  parts of the page as opposed to being directly accessed by the user.
-
-
-  <span class=impl>User agents should not render elements that have
-  the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute
-  specified.</span></p>
-
-
   <div class=example>
 
    <p>In the following skeletal example, the attribute is used to hide
@@ -77391,8 +77435,6 @@
   <!-- for example, "<a hidden href=#content>Skip to content</a>" would be inappropriate. -->
   <!-- (but only add that example if you first add some more good valid examples -->
 
-<!--HIDDENARIA--><!--FORK-->
-
   <p>Elements that are not themselves <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> must not <a href=#hyperlink>hyperlink</a> to
   elements that are <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code>. The <code title="">for</code> attributes of <code><a href=#the-label-element>label</a></code> and
   <code><a href=#the-output-element>output</a></code> elements that are not themselves <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> must similarly not refer to
@@ -77402,7 +77444,6 @@
   <p>Elements and scripts may, however, refer to elements that are
   <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> in other contexts.</p>
 
-
   <div class=example>
 
    <p>For example, it would be incorrect to use the <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute to link to a
@@ -77410,8 +77451,6 @@
    attribute. If the content is not applicable or relevant, then there
    is no reason to link to it.</p>
 
-<!--HIDDENARIA--><!--FORK-->
-
    <p>It would be fine, however, to use the ARIA <code title=attr-aria-describedby>aria-describedby</code> attribute to
    refer to descriptions that are themselves <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code>. While hiding the descriptions
    implies that they are not useful alone, they could be written in
@@ -77423,7 +77462,6 @@
    control could refer to a hidden <code><a href=#the-form-element>form</a></code> element using its
    <code title=attr-fae-form><a href=#attr-fae-form>form</a></code> attribute.</p>
 
-
   </div>
 
   <p>Elements in a section hidden by the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute are still active,
@@ -78954,7 +78992,7 @@
   void <a href=#dom-datatransfer-addelement title=dom-DataTransfer-addElement>addElement</a>(Element element);
 
   /* old interface */
-  readonly attribute <span>DOMString</span>[] <a href=#dom-datatransfer-types title=dom-DataTransfer-types>types</a>;
+  readonly attribute DOMString[] <a href=#dom-datatransfer-types title=dom-DataTransfer-types>types</a>;
   DOMString <a href=#dom-datatransfer-getdata title=dom-DataTransfer-getData>getData</a>(DOMString format);
   void <a href=#dom-datatransfer-setdata title=dom-DataTransfer-setData>setData</a>(DOMString format, DOMString data);
   void <a href=#dom-datatransfer-cleardata title=dom-DataTransfer-clearData>clearData</a>(optional DOMString format);
@@ -83315,10 +83353,10 @@
 
   <ul><li><p><code>XMLHttpRequest</code> and all interface objects and
    constructors defined by the XMLHttpRequest specifications, except
-   that the <span>document response entity body</span> must always be
-   null. The <span><code>XMLHttpRequest</code> base URL</span> is the
+   that the <a href=#document-response-entity-body>document response entity body</a> must always be
+   null. The <a href=#xmlhttprequest-base-url><code>XMLHttpRequest</code> base URL</a> is the
    <a href="#script's-base-url">script's base URL</a>; the
-   <span><code>XMLHttpRequest</code> origin</span> is the script's
+   <a href=#xmlhttprequest-origin><code>XMLHttpRequest</code> origin</a> is the script's
    <a href=#origin>origin</a>. <a href=#refsXHR>[XHR]</a></li>
 
    <li><p>The interface objects and constructors defined by this
@@ -85175,7 +85213,7 @@
 interface <dfn id=closeevent>CloseEvent</dfn> : <a href=#event>Event</a> {
   readonly attribute boolean <a href=#dom-closeevent-wasclean title=dom-CloseEvent-wasClean>wasClean</a>;
   readonly attribute unsigned short <a href=#dom-closeevent-code title=dom-CloseEvent-code>code</a>;
-  readonly attribute DOMString <span title=dom-WebSocket-reason>reason</span>;
+  readonly attribute DOMString <a href=#dom-closeevent-reason title=dom-CloseEvent-reason>reason</a>;
 };
 
 dictionary <dfn id=closeeventinit>CloseEventInit</dfn> : <a href=#eventinit>EventInit</a> {

Modified: source
===================================================================
--- source	2012-08-23 22:41:11 UTC (rev 7262)
+++ source	2012-08-24 00:23:11 UTC (rev 7263)
@@ -61,11 +61,9 @@
 <!--SET FINGERPRINT=<a href="#fingerprint" class="fingerprint"><img src="images/fingerprint.png" alt="(This is a fingerprinting vector.)"></a>-->
 <!--END storage-->
 
-<!--START w3c-html-->
+
   <h2 id="introduction">Introduction</h2>
-<!--END w3c-html-->
 
-
 <!--END dev-html-->
   <h3 id="abstract">Where does this specification fit?</h3>
 
@@ -144,26 +142,25 @@
 
   <ul>
 
-<!--
-   <li>Instead of this section, the W3C HTML specification has a
-   different paragraph explaining the difference between the W3C and
-   WHATWG versions of HTML.</li>
---> <!-- in the status section -->
+   <li>The W3C HTML specification does not include this section.</li>
 
-   <li>The W3C HTML specification lacks any of the fixes made to this
-   specification since late June 2012. (Specifically, <a
-   href="http://html5.org/tools/web-apps-tracker?from=7147">changes
-   from revision r7148 onwards</a> have not yet been applied to the
-   W3C HTML specification.)</li>
+   <li>The W3C HTML specification lacks some of the fixes made to this
+   specification since late June 2012. (Specifically, after <a
+   href="http://html5.org/tools/web-apps-tracker?from=7147">revision
+   r7148</a> changes were only adopted into the W3C HTML specification
+   on a piecemeal basis.) No precise list of these difference
+   currently exists.</li>
 
    <li>The W3C HTML specification refers to the technology as HTML5,
    rather than just HTML.</li><!--VERSION-->
 
+<!--(dunno if the policies changed or something, but the examples in question actually are in the w3c copy at the moment)
    <li>Examples that use features from HTML5 are not present in the
    W3C specifications since the W3C specifications are published as
    HTML4 due to <a
    href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
-   publication policies</a>.</li><!--HTML4POLICE-->
+   publication policies</a>.</li>
+-->
 
    <li>The W3C HTML specification omits an example as part of a
    compromise intended to resolve larger issues of divergence between
@@ -233,12 +230,6 @@
    working group chair decision from June 2011</a>.</li><!--bug
    12906-->
 
-   <li>The W3C HTML specification contradicts the ARIA specification
-   because of a <a
-   href="http://lists.w3.org/Archives/Public/public-html/2012Feb/0066.html">working
-   group chair request from February
-   2012</a>.</li><!--HIDDENARIA--><!--FORK-->
-
    <li>The W3C HTML specification does not define the term <span
    title="rel-sidebar-hyperlink">sidebar hyperlink</span>, forcing the
    definition of the <code title="rel-sidebar">sidebar</code> link
@@ -270,6 +261,28 @@
    href="http://lists.w3.org/Archives/Public/public-html/2012Mar/0557.html">working
    group chair decision from March 2012</a>.</li>
 
+   <li>The W3C HTML specification redundantly repeats requirements
+   from the ARIA specification relating to the ARIA attributes, due to
+   a working group chair decision.</li>
+
+   <li>In the W3C 2D Context specification, the <code
+   title="dom-context-2d-createPattern">createPattern()</code>
+   method's definition treats a null second argument as the empty
+   string, like IE and WebKit, rather than as an unknown value, like
+   Opera and Firefox. (This specification treats it as an unknown
+   value, since there doesn't seem to be any value to treating it as
+   the empty string.)</li>
+
+   <li>The W3C HTML specification sometimes does not give the official
+   Unicode names of characters, due to a working group chair
+   decision.</li>
+
+   <li>The W3C HTML specification allows <code
+   title="attr-hyperlink-rel">rel</code> attributes to contain
+   unregistered URLs as tokens, even though they are not treated as
+   URLs (e.g. they are handled case-insensitively), due to a working
+   group chair decision.</li>
+
   </ul>
 
   <p>The following sections are only published in the WHATWG
@@ -2914,6 +2927,8 @@
      <li><dfn title="dom-Element-id"><code>id</code></dfn> attribute</li>
      <li><dfn><code>textContent</code></dfn> attribute</li>
 
+     <li>The <dfn title="concept-node-insert">insert</dfn> algorithm for nodes</li>
+
      <li><dfn><code>Event</code></dfn> interface</li>
      <li><dfn><code>EventTarget</code></dfn> interface</li>
      <li><dfn><code>EventInit</code></dfn> dictionary type</li>
@@ -3267,6 +3282,10 @@
     the <code>dialog</code> element. <a
     href="#refsFULLSCREEN">[FULLSCREEN]</a>
 
+    <p>The term <dfn>CSS styling attribute</dfn> is defined in the
+    <cite>CSS Style Attributes</cite> specification. <a
+    href="#refsCSSATTR">[CSSATTR]</a></p>
+
    </dd>
 
 <!--END dev-html--><!--END w3c-html-->
@@ -3323,15 +3342,48 @@
 
 <!--TOPIC:HTML-->
 
+
+   <dt>ARIA</dt>
+
+   <dd>
+
+    <p>The terms <dfn>strong native semantics</dfn> is used as defined
+    in the ARIA specification. The term <dfn>default implied ARIA
+    semantics</dfn> has the same meaning as the term <i>implicit
+    WAI-ARIA semantics</i> as used in the ARIA specification. <a
+    href="#refsARIA">[ARIA]</a></p>
+
+    <p>The <dfn title="attr-aria-role"><code>role</code></dfn> and
+    <code title="">aria-*</code> attributes are defined in the ARIA
+    specification. <a href="#refsARIA">[ARIA]</a></p>
+
+
+   </dd>
+
+
+   <dt>XMLHttpRequest</dt>
+
+   <dd>
+
+    <p>This specification references the XMLHttpRequest specification
+    to define how the two specifications interact. The terms
+    <dfn>document response entity body</dfn>,
+    <dfn><code>XMLHttpRequest</code> base URL</dfn>, and
+    <dfn><code>XMLHttpRequest</code> origin</dfn> are defined in that
+    specification. <a href="#refsXHR">[XHR]</a></p>
+
+   </dd>
+
   </dl>
 
   <p>This specification does not <em>require</em> support of any
   particular network protocol, style sheet language, scripting
-  language, or any of the DOM specifications beyond those described
-  above. However, the language described by this specification is
-  biased towards CSS as the styling language, JavaScript as the
-  scripting language, and HTTP as the network protocol, and several
-  features assume that those languages and protocols are in use.</p>
+  language, or any of the DOM specifications beyond those required in
+  the list above. However, the language described by this
+  specification is biased towards CSS as the styling language,
+  JavaScript as the scripting language, and HTTP as the network
+  protocol, and several features assume that those languages and
+  protocols are in use.</p>
 
   <p class="note">This specification might have certain additional
   requirements on character encodings, image formats, audio formats,
@@ -9576,7 +9628,7 @@
   <pre class="idl">interface <dfn>HTMLPropertiesCollection</dfn> : <span>HTMLCollection</span> {
   // inherits <span title="dom-HTMLCollection-length">length</span> and <span title="dom-HTMLCollection-item">item</span>()
   legacycaller getter <span>PropertyNodeList</span>? <span title="dom-HTMLPropertiesCollection-namedItem">namedItem</span>(DOMString name); // overrides inherited namedItem()
-  readonly attribute <span>DOMString</span>[] <span title="dom-HTMLPropertiesCollection-names">names</span>;
+  readonly attribute DOMString[] <span title="dom-HTMLPropertiesCollection-names">names</span>;
 };
 
 typedef sequence<any> <dfn>PropertyValueArray</dfn>;
@@ -11405,7 +11457,7 @@
   requirements,</span> is the <code>HTMLElement</code> interface.</p>
 
   <pre class="idl">interface <dfn>HTMLElement</dfn> : <span>Element</span> {
-  // <span>metadata attributes</span>
+  // metadata attributes
            attribute DOMString <span title="dom-title">title</span>;
            attribute DOMString <span title="dom-lang">lang</span>;
            attribute boolean <span title="dom-translate">translate</span>;
@@ -11445,7 +11497,7 @@
   readonly attribute boolean? <span title="dom-command-ro-commandChecked">commandChecked</span>;<!-- v2COMMAND
   readonly attribute <span>HTMLCollection</span> <span title="dom-command-ro-commandTriggers">commandTriggers</span>;-->
 
-  // <span>styling</span>
+  // styling
   readonly attribute <span>CSSStyleDeclaration</span> <span title="dom-style">style</span>;
 
   // <span>event handler IDL attributes</span>
@@ -31397,7 +31449,7 @@
   void <span title="dom-media-pause">pause</span>();
 
   // media controller
-           attribute <span>DOMString</span> <span title="dom-media-mediaGroup">mediaGroup</span>;
+           attribute DOMString <span title="dom-media-mediaGroup">mediaGroup</span>;
            attribute <span>MediaController</span>? <span title="dom-media-controller">controller</span>;
 
   // controls
@@ -42574,14 +42626,14 @@
 dictionary <dfn>HitRegionOptions</dfn> {
   <span>Path</span>? <span title="dom-HitRegionOptions-path">path</span> = null;
 <!--  <span>SVGMatrix</span>? <span title="dom-HitRegionOptions-transform">transform</span> = null;
--->  <span>DOMString</span> <span title="dom-HitRegionOptions-id">id</span> = "";
-  <span>DOMString</span>? <span title="dom-HitRegionOptions-parentID">parentID</span> = null;
-  <span>DOMString</span> <span title="dom-HitRegionOptions-cursor">cursor</span> = "inherit";
+-->  DOMString <span title="dom-HitRegionOptions-id">id</span> = "";
+  DOMString? <span title="dom-HitRegionOptions-parentID">parentID</span> = null;
+  DOMString <span title="dom-HitRegionOptions-cursor">cursor</span> = "inherit";
   // for control-backed regions:
   <span>Element</span>? <span title="dom-HitRegionOptions-control">control</span> = null;
   // for unbacked regions:
-  <span>DOMString</span>? <span title="dom-HitRegionOptions-label">label</span> = null;
-  <span>DOMString</span>? <span title="dom-HitRegionOptions-role">role</span> = null;
+  DOMString? <span title="dom-HitRegionOptions-label">label</span> = null;
+  DOMString? <span title="dom-HitRegionOptions-role">role</span> = null;
 };
 
 interface <dfn>ImageData</dfn> {
@@ -90516,27 +90568,14 @@
   <p>All <span>HTML elements</span> may have the <code
   title="attr-hidden">hidden</code> content attribute set. The <code
   title="attr-hidden">hidden</code> attribute is a <span>boolean
-  attribute</span>.
+  attribute</span>. When specified on an element, it indicates that
+  the element is not yet, or is no longer, directly relevant to the
+  page's current state, or that it is being used to declare content to
+  be reused by other parts of the page as opposed to being directly
+  accessed by the user. <span class="impl">User agents should not
+  render elements that have the <code
+  title="attr-hidden">hidden</code> attribute specified.</span></p>
 
-<!--END w3c-html--><!--HIDDENARIA--><!--FORK-->
-
-  When specified on an element, it indicates that the element is not
-  yet, or is no longer, directly relevant to the page's current state,
-  or that it is being used to declare content to be reused by other
-  parts of the page as opposed to being directly accessed by the user.
-
-<!--START w3c-html--><!--END complete-->
-
-  When specified on an element, it indicates that the element is not
-  yet, or is no longer, relevant.
-
-<!--START complete-->
-
-  <span class="impl">User agents should not render elements that have
-  the <code title="attr-hidden">hidden</code> attribute
-  specified.</span></p>
-
-
   <div class="example">
 
    <p>In the following skeletal example, the attribute is used to hide
@@ -90578,8 +90617,6 @@
   <!-- for example, "<a hidden href=#content>Skip to content</a>" would be inappropriate. -->
   <!-- (but only add that example if you first add some more good valid examples -->
 
-<!--END w3c-html--><!--HIDDENARIA--><!--FORK-->
-
   <p>Elements that are not themselves <code
   title="attr-hidden">hidden</code> must not <span>hyperlink</span> to
   elements that are <code title="attr-hidden">hidden</code>. The <code
@@ -90592,14 +90629,6 @@
   <p>Elements and scripts may, however, refer to elements that are
   <code title="attr-hidden">hidden</code> in other contexts.</p>
 
-<!--START w3c-html--><!--END complete-->
-
-  <p>Elements that are not <code title="attr-hidden">hidden</code>
-  should not link to or refer to elements that are <code
-  title="attr-hidden">hidden</code>.</p>
-
-<!--START complete-->
-
   <div class="example">
 
    <p>For example, it would be incorrect to use the <code
@@ -90608,8 +90637,6 @@
    attribute. If the content is not applicable or relevant, then there
    is no reason to link to it.</p>
 
-<!--END w3c-html--><!--HIDDENARIA--><!--FORK-->
-
    <p>It would be fine, however, to use the ARIA <code
    title="attr-aria-describedby">aria-describedby</code> attribute to
    refer to descriptions that are themselves <code
@@ -90624,18 +90651,6 @@
    control could refer to a hidden <code>form</code> element using its
    <code title="attr-fae-form">form</code> attribute.</p>
 
-<!--START w3c-html--><!--END complete-->
-
-   <p>It would similarly be incorrect to use the ARIA <code
-   title="attr-aria-describedby">aria-describedby</code> attribute to
-   refer to descriptions that are themselves <code
-   title="attr-hidden">hidden</code>. Hiding a section means that it
-   is not applicable or relevant to anyone at the current time, so
-   clearly it cannot be a valid description of content the user can
-   interact with.</p>
-
-<!--START complete-->
-
   </div>
 
   <p>Elements in a section hidden by the <code
@@ -92381,7 +92396,7 @@
   void <span title="dom-DataTransfer-addElement">addElement</span>(Element element);
 
   /* old interface */
-  readonly attribute <span>DOMString</span>[] <span title="dom-DataTransfer-types">types</span>;
+  readonly attribute DOMString[] <span title="dom-DataTransfer-types">types</span>;
   DOMString <span title="dom-DataTransfer-getData">getData</span>(DOMString format);
   void <span title="dom-DataTransfer-setData">setData</span>(DOMString format, DOMString data);
   void <span title="dom-DataTransfer-clearData">clearData</span>(optional DOMString format);
@@ -99070,7 +99085,7 @@
 interface <dfn>CloseEvent</dfn> : <span>Event</span> {
   readonly attribute boolean <span title="dom-CloseEvent-wasClean">wasClean</span>;
   readonly attribute unsigned short <span title="dom-CloseEvent-code">code</span>;
-  readonly attribute DOMString <span title="dom-WebSocket-reason">reason</span>;
+  readonly attribute DOMString <span title="dom-CloseEvent-reason">reason</span>;
 };
 
 dictionary <dfn>CloseEventInit</dfn> : <span>EventInit</span> {




More information about the Commit-Watchers mailing list