[e] (0) make ms2ger and gsnedders happier (minor editorial stuff in p…

…arser and elsewhere) Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=24360 Affected topics: HTML, HTML Syntax and Parsing git-svn-id: http://svn.whatwg.org/webapps@8418 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jan 24, 2014 · d77cc71 · d77cc71
1 parent f52b67e
commit d77cc71
Show file tree

Hide file tree

Showing 3 changed files with 27 additions and 9 deletions.
diff --git a/complete.html b/complete.html
@@ -298,7 +298,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 22 January 2014</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 24 January 2014</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>
@@ -11477,7 +11477,7 @@ <h5 id=user-agent-conformance-criteria><span class=secno>3.2.6.2 </span>User age
   or, alternatively, the user agent must act as if it implemented just the aforementioned properties
   and had a user agent style sheet that included all the aforementioned rules, but without letting
   style sheets specified in documents override them, or, alternatively, the user agent must
-  implement another styling language with equivalent semantics. <a href=#CSSWM>[CSSWM]</a> <a href=#CSSGC>[CSSGC]</a></p>
+  implement another styling language with equivalent semantics. <a href=#refsCSSWM>[CSSWM]</a> <a href=#refsCSSGC>[CSSGC]</a></p>
 
   <p id=bidireq>The following elements and attributes have requirements defined by the <a href=#rendering>rendering</a> section that, due to the requirements in this section, are
   requirements on all user agents (not just those that <a href=#renderingUA>support the suggested
@@ -45517,6 +45517,7 @@ <h4 id=the-textarea-element><span class=secno>4.10.11 </span>The <dfn><code>text
 Love,
 Daddy"&gt;&lt;/textarea&gt;</pre>
 
+<!--CLEANUP-->
    <p>To have the browser submit <a href=#the-directionality>the directionality</a> of
    the element along with the value, the <code title=attr-fe-dirname><a href=#attr-fe-dirname>dirname</a></code> attribute can be
    specified:</p>
@@ -87268,7 +87269,8 @@ <h5 id=rawtext-state><span class=secno>12.2.4.5 </span><dfn>RAWTEXT state</dfn><
   token; if there is already an attribute on the token with the exact same name, then this is a
   <a href=#parse-error>parse error</a> and the new attribute must be removed from the token.</p>
 
-  <p class=note>If an attribute is so removed from a token, it, along with the value that gets
+<!--CLEANUP-->
+  <p class=note>If an attribute is so removed from a token, it, and the value that gets
   associated with it, if any, are never subsequently used by the parser, and are therefore
   effectively discarded. Removing the attribute in this way does not change its status as the
   "current attribute" for the purposes of the tokenizer, however.</p>
@@ -101887,6 +101889,9 @@ <h2 class=no-num id=references>References</h2><!--REFS-->
    <dt id=refsCSSFONTS>[CSSFONTS]</dt>
    <dd><cite><a href=http://dev.w3.org/csswg/css3-fonts/>CSS Fonts</a></cite>, J. Daggett. W3C.</dd>
 
+   <dt id=refsCSSGC>[CSSGC]</dt>
+   <dd><cite><a href=http://dev.w3.org/csswg/css-content>CSS Generated Content</a></cite>, H. Lie, E. Etemad, I. Hickson. W3C.</dd>
+
    <dt id=refsCSSIMAGES>[CSSIMAGES]</dt>
    <dd><cite><a href=http://dev.w3.org/csswg/css-images/>CSS Image Values and Replaced Content Module</a></cite>, E. Etemad, T. Atkins. W3C.</dd>
 
@@ -101915,6 +101920,9 @@ <h2 class=no-num id=references>References</h2><!--REFS-->
    <dt id=refsCSSVALUES>[CSSVALUES]</dt>
    <dd><cite><a href=http://dev.w3.org/csswg/css3-values/>CSS3 Values and Units</a></cite>, H. Lie, T. Atkins, E. Etemad. W3C.</dd>
 
+   <dt id=refsCSSWM>[CSSWM]</dt>
+   <dd><cite><a href=http://dev.w3.org/csswg/css-writing-modes>CSS Writing Modes</a></cite>, E. Etemad, K. Ishii. W3C.</dd>
+
    <dt id=refsCUSTOM>[CUSTOM]</dt>
    <dd><cite><a href=http://w3c.github.io/webcomponents/spec/custom/>Custom Elements</a></cite>, D. Glazkov. W3C.</dd>
 

diff --git a/index b/index
@@ -298,7 +298,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 22 January 2014</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 24 January 2014</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>
@@ -11477,7 +11477,7 @@ plaintext     = *( %x0000-2029 / %x202F-2065 / %x206A-10FFFF )
   or, alternatively, the user agent must act as if it implemented just the aforementioned properties
   and had a user agent style sheet that included all the aforementioned rules, but without letting
   style sheets specified in documents override them, or, alternatively, the user agent must
-  implement another styling language with equivalent semantics. <a href=#CSSWM>[CSSWM]</a> <a href=#CSSGC>[CSSGC]</a></p>
+  implement another styling language with equivalent semantics. <a href=#refsCSSWM>[CSSWM]</a> <a href=#refsCSSGC>[CSSGC]</a></p>
 
   <p id=bidireq>The following elements and attributes have requirements defined by the <a href=#rendering>rendering</a> section that, due to the requirements in this section, are
   requirements on all user agents (not just those that <a href=#renderingUA>support the suggested
@@ -45517,6 +45517,7 @@ meet your there. Should we just have dinner?
 Love,
 Daddy"&gt;&lt;/textarea&gt;</pre>
 
+<!--CLEANUP-->
    <p>To have the browser submit <a href=#the-directionality>the directionality</a> of
    the element along with the value, the <code title=attr-fe-dirname><a href=#attr-fe-dirname>dirname</a></code> attribute can be
    specified:</p>
@@ -87268,7 +87269,8 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
   token; if there is already an attribute on the token with the exact same name, then this is a
   <a href=#parse-error>parse error</a> and the new attribute must be removed from the token.</p>
 
-  <p class=note>If an attribute is so removed from a token, it, along with the value that gets
+<!--CLEANUP-->
+  <p class=note>If an attribute is so removed from a token, it, and the value that gets
   associated with it, if any, are never subsequently used by the parser, and are therefore
   effectively discarded. Removing the attribute in this way does not change its status as the
   "current attribute" for the purposes of the tokenizer, however.</p>
@@ -101887,6 +101889,9 @@ if (s = prompt('What is your name?')) {
    <dt id=refsCSSFONTS>[CSSFONTS]</dt>
    <dd><cite><a href=http://dev.w3.org/csswg/css3-fonts/>CSS Fonts</a></cite>, J. Daggett. W3C.</dd>
 
+   <dt id=refsCSSGC>[CSSGC]</dt>
+   <dd><cite><a href=http://dev.w3.org/csswg/css-content>CSS Generated Content</a></cite>, H. Lie, E. Etemad, I. Hickson. W3C.</dd>
+
    <dt id=refsCSSIMAGES>[CSSIMAGES]</dt>
    <dd><cite><a href=http://dev.w3.org/csswg/css-images/>CSS Image Values and Replaced Content Module</a></cite>, E. Etemad, T. Atkins. W3C.</dd>
 
@@ -101915,6 +101920,9 @@ if (s = prompt('What is your name?')) {
    <dt id=refsCSSVALUES>[CSSVALUES]</dt>
    <dd><cite><a href=http://dev.w3.org/csswg/css3-values/>CSS3 Values and Units</a></cite>, H. Lie, T. Atkins, E. Etemad. W3C.</dd>
 
+   <dt id=refsCSSWM>[CSSWM]</dt>
+   <dd><cite><a href=http://dev.w3.org/csswg/css-writing-modes>CSS Writing Modes</a></cite>, E. Etemad, K. Ishii. W3C.</dd>
+
    <dt id=refsCUSTOM>[CUSTOM]</dt>
    <dd><cite><a href=http://w3c.github.io/webcomponents/spec/custom/>Custom Elements</a></cite>, D. Glazkov. W3C.</dd>
 

diff --git a/source b/source
@@ -11515,8 +11515,8 @@ plaintext     = *( %x0000-2029 / %x202F-2065 / %x206A-10FFFF )
   or, alternatively, the user agent must act as if it implemented just the aforementioned properties
   and had a user agent style sheet that included all the aforementioned rules, but without letting
   style sheets specified in documents override them, or, alternatively, the user agent must
-  implement another styling language with equivalent semantics. <a href="#CSSWM">[CSSWM]</a> <a
-  href="#CSSGC">[CSSGC]</a></p>
+  implement another styling language with equivalent semantics. <a href="#refsCSSWM">[CSSWM]</a> <a
+  href="#refsCSSGC">[CSSGC]</a></p>
 
   <p id="bidireq">The following elements and attributes have requirements defined by the <a
   href="#rendering">rendering</a> section that, due to the requirements in this section, are
@@ -49913,6 +49913,7 @@ meet your there. Should we just have dinner?
 Love,
 Daddy">&lt;/textarea></pre>
 
+<!--CLEANUP-->
    <p>To have the browser submit <span>the directionality</span> of
    the element along with the value, the <code
    data-x="attr-fe-dirname">dirname</code> attribute can be
@@ -97293,7 +97294,8 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   token; if there is already an attribute on the token with the exact same name, then this is a
   <span>parse error</span> and the new attribute must be removed from the token.</p>
 
-  <p class="note">If an attribute is so removed from a token, it, along with the value that gets
+<!--CLEANUP-->
+  <p class="note">If an attribute is so removed from a token, it, and the value that gets
   associated with it, if any, are never subsequently used by the parser, and are therefore
   effectively discarded. Removing the attribute in this way does not change its status as the
   "current attribute" for the purposes of the tokenizer, however.</p>