[e] (0) More purely editorial cleanup in section 3 (infrastructure st…

…uff)... Affected topics: HTML git-svn-id: http://svn.whatwg.org/webapps@8533 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Mar 6, 2014 · 84529e6 · 84529e6
1 parent 11b8c60
commit 84529e6
Show file tree

Hide file tree

Showing 3 changed files with 73 additions and 83 deletions.
diff --git a/complete.html b/complete.html
@@ -9946,9 +9946,8 @@ <h6 id=interactive-content-0><span class=secno>3.2.4.1.7 </span>Interactive cont
 http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0A%3Cform%20action%3D%22http%3A//google.com/%22%3EX%3C/form%3E%0A%3Cscript%3E%0Avar%20evt%20%3D%20document.createEvent%28%22Events%22%29%3B%0Aevt.initEvent%28%22submit%22%2C%20true%2C%20true%29%3B%0Adocument.getElementsByTagName%28%27form%27%29%5B0%5D.dispatchEvent%28evt%29%3B%0A%3C/script%3E
 -->
 
-<!--CLEANUP-->
-  <p><dfn id=interactive-content>Interactive content</dfn> is content that is specifically
-  intended for user interaction.</p>
+  <p><dfn id=interactive-content>Interactive content</dfn> is content that is specifically intended for user
+  interaction.</p>
 
   <!-- when updating this also update the category index -->
   <ul class="brief category-list"><li><code><a href=#the-a-element>a</a></code></li>
@@ -9974,9 +9973,8 @@ <h6 id=interactive-content-0><span class=secno>3.2.4.1.7 </span>Interactive cont
   <h6 id=palpable-content-0><span class=secno>3.2.4.1.8 </span>Palpable content</h6>
 
   <p>As a general rule, elements whose content model allows any <a href=#flow-content>flow content</a> or
-  <a href=#phrasing-content>phrasing content</a> should have at least one node in its <a href=#concept-html-contents title=concept-html-contents>contents</a> that is <dfn id=palpable-content>palpable
-  content</dfn> and that does not have the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute
-  specified.</p>
+  <a href=#phrasing-content>phrasing content</a> should have at least one node in its <a href=#concept-html-contents title=concept-html-contents>contents</a> that is <dfn id=palpable-content>palpable content</dfn> and that does
+  not have the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute specified.</p>
 
   <p>This requirement is not a hard requirement, however, as there are many cases where an element
   can be empty legitimately, for example when it is used as a placeholder which will later be filled
@@ -10065,8 +10063,8 @@ <h6 id=palpable-content-0><span class=secno>3.2.4.1.8 </span>Palpable content</h
    <li><a href=#text-content title="text content">Text</a> that is not <a href=#inter-element-whitespace>inter-element whitespace</a></li>
   </ul><h6 id=script-supporting-elements-0><span class=secno>3.2.4.1.9 </span>Script-supporting elements</h6>
 
-  <p><dfn id=script-supporting-elements>Script-supporting elements</dfn> are those that do not <a href=#represents title=represents>represent</a> anything themselves (i.e. they are not rendered), but are used
-  to support scripts, e.g. to provide functionality for the user.</p>
+  <p><dfn id=script-supporting-elements>Script-supporting elements</dfn> are those that do not <a href=#represents title=represents>represent</a> anything themselves (i.e. they are not rendered), but are
+  used to support scripts, e.g. to provide functionality for the user.</p>
 
   <p>The following elements are script-supporting elements:</p>
 
@@ -10094,8 +10092,8 @@ <h6 id=palpable-content-0><span class=secno>3.2.4.1.8 </span>Palpable content</h
      without first violating the earlier requirement)
   <p>Furthermore, when a content model includes a part that is "transparent", those parts must not
   contain content that would not be conformant if all transparent elements in the tree were
-  replaced, in their parent element, by the <span title="concept-html-contents">contents</span> in the "transparent" part of their content
-  model, retaining order.</p>
+  replaced, in their parent element, by the <span title="concept-html-contents">contents</span> in
+  the "transparent" part of their content model, retaining order.</p>
 
   <div class="example">
 
@@ -10198,14 +10196,14 @@ <h5 id=paragraphs><span class=secno>3.2.4.3 </span>Paragraphs</h5>
   <div class=impl>
 
   <p>Let <var title="">view</var> be a view of the DOM that replaces all <code><a href=#the-a-element>a</a></code>,
-  <code><a href=#the-ins-element>ins</a></code>, <code><a href=#the-del-element>del</a></code>, and <code><a href=#the-map-element>map</a></code> elements in the document with their
-  <a href=#concept-html-contents title=concept-html-contents>contents</a>. Then, in <var title="">view</var>, for each run of sibling <a href=#phrasing-content>phrasing content</a>
-  nodes uninterrupted by other types of content, in an element that accepts content other than
-  <a href=#phrasing-content>phrasing content</a> as well as <a href=#phrasing-content>phrasing content</a>, let <var title="">first</var> be the first node of the run, and let <var title="">last</var> be the last
-  node of the run. For each such run that consists of at least one node that is neither
-  <a href=#embedded-content-category>embedded content</a> nor <a href=#inter-element-whitespace>inter-element whitespace</a>, a paragraph exists in the
-  original DOM from immediately before <var title="">first</var> to immediately after <var title="">last</var>. (Paragraphs can thus span across <code><a href=#the-a-element>a</a></code>, <code><a href=#the-ins-element>ins</a></code>,
-  <code><a href=#the-del-element>del</a></code>, and <code><a href=#the-map-element>map</a></code> elements.)</p>
+  <code><a href=#the-ins-element>ins</a></code>, <code><a href=#the-del-element>del</a></code>, and <code><a href=#the-map-element>map</a></code> elements in the document with their <a href=#concept-html-contents title=concept-html-contents>contents</a>. Then, in <var title="">view</var>, for each run
+  of sibling <a href=#phrasing-content>phrasing content</a> nodes uninterrupted by other types of content, in an
+  element that accepts content other than <a href=#phrasing-content>phrasing content</a> as well as <a href=#phrasing-content>phrasing
+  content</a>, let <var title="">first</var> be the first node of the run, and let <var title="">last</var> be the last node of the run. For each such run that consists of at least one
+  node that is neither <a href=#embedded-content-category>embedded content</a> nor <a href=#inter-element-whitespace>inter-element whitespace</a>, a
+  paragraph exists in the original DOM from immediately before <var title="">first</var> to
+  immediately after <var title="">last</var>. (Paragraphs can thus span across <code><a href=#the-a-element>a</a></code>,
+  <code><a href=#the-ins-element>ins</a></code>, <code><a href=#the-del-element>del</a></code>, and <code><a href=#the-map-element>map</a></code> elements.)</p>
 
   <p>Conformance checkers may warn authors of cases where they have paragraphs that overlap each
   other (this can happen with <code><a href=#the-object-element>object</a></code>, <code><a href=#the-video-element>video</a></code>, <code><a href=#the-audio-element>audio</a></code>, and
@@ -11410,25 +11408,23 @@ <h5 id=user-agent-conformance-criteria><span class=secno>3.2.6.2 </span>User age
 
   <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><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
+  <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
   <a href=#strong-native-semantics>strong native semantics</a> or are equal to the <a href=#default-implicit-aria-semantics>default implicit ARIA
   semantics</a> 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>
 
   <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><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code>
-  attributes to values that match the <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined in the
-  following two tables.</p>
+  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 <a href=#default-implicit-aria-semantics>default implicit ARIA
+  semantics</a> defined in the following two tables.</p>
 
   <div class=impl>
 
-<!--CLEANUP-->
-  <p>User agents must implement ARIA semantics on all <a href=#html-elements>HTML elements</a>, as
-  defined in the ARIA specifications. The <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below
-  must be recognized by implementations for the purposes of ARIA processing. <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
+  <p>User agents must implement ARIA semantics on all <a href=#html-elements>HTML elements</a>, as defined in the
+  ARIA specifications. The <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below must be
+  recognized by implementations for the purposes of ARIA processing. <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
 
   <p class=note>The ARIA attributes defined in the ARIA specifications, and the <a href=#strong-native-semantics>strong
   native semantics</a> and <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below, do not

diff --git a/index b/index
@@ -9946,9 +9946,8 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
 http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0A%3Cform%20action%3D%22http%3A//google.com/%22%3EX%3C/form%3E%0A%3Cscript%3E%0Avar%20evt%20%3D%20document.createEvent%28%22Events%22%29%3B%0Aevt.initEvent%28%22submit%22%2C%20true%2C%20true%29%3B%0Adocument.getElementsByTagName%28%27form%27%29%5B0%5D.dispatchEvent%28evt%29%3B%0A%3C/script%3E
 -->
 
-<!--CLEANUP-->
-  <p><dfn id=interactive-content>Interactive content</dfn> is content that is specifically
-  intended for user interaction.</p>
+  <p><dfn id=interactive-content>Interactive content</dfn> is content that is specifically intended for user
+  interaction.</p>
 
   <!-- when updating this also update the category index -->
   <ul class="brief category-list"><li><code><a href=#the-a-element>a</a></code></li>
@@ -9974,9 +9973,8 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   <h6 id=palpable-content-0><span class=secno>3.2.4.1.8 </span>Palpable content</h6>
 
   <p>As a general rule, elements whose content model allows any <a href=#flow-content>flow content</a> or
-  <a href=#phrasing-content>phrasing content</a> should have at least one node in its <a href=#concept-html-contents title=concept-html-contents>contents</a> that is <dfn id=palpable-content>palpable
-  content</dfn> and that does not have the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute
-  specified.</p>
+  <a href=#phrasing-content>phrasing content</a> should have at least one node in its <a href=#concept-html-contents title=concept-html-contents>contents</a> that is <dfn id=palpable-content>palpable content</dfn> and that does
+  not have the <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute specified.</p>
 
   <p>This requirement is not a hard requirement, however, as there are many cases where an element
   can be empty legitimately, for example when it is used as a placeholder which will later be filled
@@ -10065,8 +10063,8 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
    <li><a href=#text-content title="text content">Text</a> that is not <a href=#inter-element-whitespace>inter-element whitespace</a></li>
   </ul><h6 id=script-supporting-elements-0><span class=secno>3.2.4.1.9 </span>Script-supporting elements</h6>
 
-  <p><dfn id=script-supporting-elements>Script-supporting elements</dfn> are those that do not <a href=#represents title=represents>represent</a> anything themselves (i.e. they are not rendered), but are used
-  to support scripts, e.g. to provide functionality for the user.</p>
+  <p><dfn id=script-supporting-elements>Script-supporting elements</dfn> are those that do not <a href=#represents title=represents>represent</a> anything themselves (i.e. they are not rendered), but are
+  used to support scripts, e.g. to provide functionality for the user.</p>
 
   <p>The following elements are script-supporting elements:</p>
 
@@ -10094,8 +10092,8 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
      without first violating the earlier requirement)
   <p>Furthermore, when a content model includes a part that is "transparent", those parts must not
   contain content that would not be conformant if all transparent elements in the tree were
-  replaced, in their parent element, by the <span title="concept-html-contents">contents</span> in the "transparent" part of their content
-  model, retaining order.</p>
+  replaced, in their parent element, by the <span title="concept-html-contents">contents</span> in
+  the "transparent" part of their content model, retaining order.</p>
 
   <div class="example">
 
@@ -10198,14 +10196,14 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   <div class=impl>
 
   <p>Let <var title="">view</var> be a view of the DOM that replaces all <code><a href=#the-a-element>a</a></code>,
-  <code><a href=#the-ins-element>ins</a></code>, <code><a href=#the-del-element>del</a></code>, and <code><a href=#the-map-element>map</a></code> elements in the document with their
-  <a href=#concept-html-contents title=concept-html-contents>contents</a>. Then, in <var title="">view</var>, for each run of sibling <a href=#phrasing-content>phrasing content</a>
-  nodes uninterrupted by other types of content, in an element that accepts content other than
-  <a href=#phrasing-content>phrasing content</a> as well as <a href=#phrasing-content>phrasing content</a>, let <var title="">first</var> be the first node of the run, and let <var title="">last</var> be the last
-  node of the run. For each such run that consists of at least one node that is neither
-  <a href=#embedded-content-category>embedded content</a> nor <a href=#inter-element-whitespace>inter-element whitespace</a>, a paragraph exists in the
-  original DOM from immediately before <var title="">first</var> to immediately after <var title="">last</var>. (Paragraphs can thus span across <code><a href=#the-a-element>a</a></code>, <code><a href=#the-ins-element>ins</a></code>,
-  <code><a href=#the-del-element>del</a></code>, and <code><a href=#the-map-element>map</a></code> elements.)</p>
+  <code><a href=#the-ins-element>ins</a></code>, <code><a href=#the-del-element>del</a></code>, and <code><a href=#the-map-element>map</a></code> elements in the document with their <a href=#concept-html-contents title=concept-html-contents>contents</a>. Then, in <var title="">view</var>, for each run
+  of sibling <a href=#phrasing-content>phrasing content</a> nodes uninterrupted by other types of content, in an
+  element that accepts content other than <a href=#phrasing-content>phrasing content</a> as well as <a href=#phrasing-content>phrasing
+  content</a>, let <var title="">first</var> be the first node of the run, and let <var title="">last</var> be the last node of the run. For each such run that consists of at least one
+  node that is neither <a href=#embedded-content-category>embedded content</a> nor <a href=#inter-element-whitespace>inter-element whitespace</a>, a
+  paragraph exists in the original DOM from immediately before <var title="">first</var> to
+  immediately after <var title="">last</var>. (Paragraphs can thus span across <code><a href=#the-a-element>a</a></code>,
+  <code><a href=#the-ins-element>ins</a></code>, <code><a href=#the-del-element>del</a></code>, and <code><a href=#the-map-element>map</a></code> elements.)</p>
 
   <p>Conformance checkers may warn authors of cases where they have paragraphs that overlap each
   other (this can happen with <code><a href=#the-object-element>object</a></code>, <code><a href=#the-video-element>video</a></code>, <code><a href=#the-audio-element>audio</a></code>, and
@@ -11410,25 +11408,23 @@ plaintext     = *( %x0000-2029 / %x202F-2065 / %x206A-10FFFF )
 
   <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><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
+  <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
   <a href=#strong-native-semantics>strong native semantics</a> or are equal to the <a href=#default-implicit-aria-semantics>default implicit ARIA
   semantics</a> 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>
 
   <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><a href=#attr-aria-role>role</a></code> and <code title=attr-aria-*>aria-*</code>
-  attributes to values that match the <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined in the
-  following two tables.</p>
+  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 <a href=#default-implicit-aria-semantics>default implicit ARIA
+  semantics</a> defined in the following two tables.</p>
 
   <div class=impl>
 
-<!--CLEANUP-->
-  <p>User agents must implement ARIA semantics on all <a href=#html-elements>HTML elements</a>, as
-  defined in the ARIA specifications. The <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below
-  must be recognized by implementations for the purposes of ARIA processing. <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
+  <p>User agents must implement ARIA semantics on all <a href=#html-elements>HTML elements</a>, as defined in the
+  ARIA specifications. The <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below must be
+  recognized by implementations for the purposes of ARIA processing. <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
 
   <p class=note>The ARIA attributes defined in the ARIA specifications, and the <a href=#strong-native-semantics>strong
   native semantics</a> and <a href=#default-implicit-aria-semantics>default implicit ARIA semantics</a> defined below, do not