[e] (0) Fly your flags at half mast for E4X.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=20391 Affected topics: HTML git-svn-id: http://svn.whatwg.org/webapps@7625 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Dec 31, 2012 · 307be9c · 307be9c
1 parent 8549e1c
commit 307be9c
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 7 deletions.
diff --git a/complete.html b/complete.html
@@ -16735,8 +16735,10 @@ <h5 id=scriptingLanguages><span class=secno>4.3.1.1 </span>Scripting languages</
    <dt>"<code>text/x-javascript</code>"</dt>
    <dd>JavaScript. <a href=#refsECMA262>[ECMA262]</a></dd>
 
+<!--(historical footnote)
    <dt>"<code>text/javascript;e4x=1</code>"</dt>
-   <dd>JavaScript with ECMAScript for XML. <a href=#refsECMA357>[ECMA357]</a></dd>
+   <dd>JavaScript with ECMAScript for XML. <a href="#refsECMA357">[ECMA357]</a></dd>
+-->
 
   </dl><div class=impl>
 
@@ -16770,7 +16772,7 @@ <h5 id=scriptingLanguages><span class=secno>4.3.1.1 </span>Scripting languages</
   <p>When examining types to determine if they represent supported languages, user agents must not
   ignore MIME parameters. Types are to be compared including all parameters.</p> <!-- whether the
   order of parameters matters is left undefined until such time as it matters; so far the only
-  relevant parameter is 'e4x' -->
+  relevant parameter was 'e4x', and it's gone for now -->
 
   <p class=note>For example, types that include the <code title="">charset</code> parameter will
   not be recognized as referencing any of the scripting languages listed above.</p>
@@ -36281,7 +36283,7 @@ <h6 id=text-styles><span class=secno>4.8.11.2.5 </span>Text styles</h6>
   attribute's allowed keywords correspond to alignment points in the
   font:</p>
 
-  <p><img alt="The top of the em square is roughly at the top of the glyphs in a font, the hanging baseline is where some glyphs like &#2310; are anchored, the middle is half-way between the top of the em square and the bottom of the em square, the alphabetic baseline is where characters like &Aacute;, &yuml;, f, and &Omega; are anchored, the ideographic baseline is where glyphs like &#31169; and &#36948; are anchored, and the bottom of the em square is roughly at the bottom of the glyphs in a font. The top and bottom of the bounding box can be far from these baselines, due to glyphs extending far outside the em square." height=300 src=http://images.whatwg.org/baselines.png width=738></p>
+  <p><img alt="The top of the em square is roughly at the top of the glyphs in a font, the hanging baseline is where some glyphs like &#2310; are anchored, the middle is half-way between the top of the em square and the bottom of the em square, the alphabetic baseline is where characters like &Aacute;, &yuml;, f, and " height=300 src=http://images.whatwg.org/baselines.png width=738>03A9; are anchored, the ideographic baseline is where glyphs like &#31169; and &#36948; are anchored, and the bottom of the em square is roughly at the bottom of the glyphs in a font. The top and bottom of the bounding box can be far from these baselines, due to glyphs extending far outside the em square."&gt;</p>
 
   <p>The keywords map to these alignment points as follows:</p>
 

diff --git a/index b/index
@@ -16735,8 +16735,10 @@ o............A....e
    <dt>"<code>text/x-javascript</code>"</dt>
    <dd>JavaScript. <a href=#refsECMA262>[ECMA262]</a></dd>
 
+<!--(historical footnote)
    <dt>"<code>text/javascript;e4x=1</code>"</dt>
-   <dd>JavaScript with ECMAScript for XML. <a href=#refsECMA357>[ECMA357]</a></dd>
+   <dd>JavaScript with ECMAScript for XML. <a href="#refsECMA357">[ECMA357]</a></dd>
+-->
 
   </dl><div class=impl>
 
@@ -16770,7 +16772,7 @@ o............A....e
   <p>When examining types to determine if they represent supported languages, user agents must not
   ignore MIME parameters. Types are to be compared including all parameters.</p> <!-- whether the
   order of parameters matters is left undefined until such time as it matters; so far the only
-  relevant parameter is 'e4x' -->
+  relevant parameter was 'e4x', and it's gone for now -->
 
   <p class=note>For example, types that include the <code title="">charset</code> parameter will
   not be recognized as referencing any of the scripting languages listed above.</p>
@@ -36281,7 +36283,7 @@ hairline width with transform. ack Shaun Morris.  --></div>
   attribute's allowed keywords correspond to alignment points in the
   font:</p>
 
-  <p><img alt="The top of the em square is roughly at the top of the glyphs in a font, the hanging baseline is where some glyphs like &#2310; are anchored, the middle is half-way between the top of the em square and the bottom of the em square, the alphabetic baseline is where characters like &Aacute;, &yuml;, f, and &Omega; are anchored, the ideographic baseline is where glyphs like &#31169; and &#36948; are anchored, and the bottom of the em square is roughly at the bottom of the glyphs in a font. The top and bottom of the bounding box can be far from these baselines, due to glyphs extending far outside the em square." height=300 src=http://images.whatwg.org/baselines.png width=738></p>
+  <p><img alt="The top of the em square is roughly at the top of the glyphs in a font, the hanging baseline is where some glyphs like &#2310; are anchored, the middle is half-way between the top of the em square and the bottom of the em square, the alphabetic baseline is where characters like &Aacute;, &yuml;, f, and " height=300 src=http://images.whatwg.org/baselines.png width=738>03A9; are anchored, the ideographic baseline is where glyphs like &#31169; and &#36948; are anchored, and the bottom of the em square is roughly at the bottom of the glyphs in a font. The top and bottom of the bounding box can be far from these baselines, due to glyphs extending far outside the em square."&gt;</p>
 
   <p>The keywords map to these alignment points as follows:</p>
 

diff --git a/source b/source
@@ -17659,8 +17659,10 @@ o............A....e
    <dt>"<code>text/x-javascript</code>"</dt>
    <dd>JavaScript. <a href="#refsECMA262">[ECMA262]</a></dd>
 
+<!--(historical footnote)
    <dt>"<code>text/javascript;e4x=1</code>"</dt>
    <dd>JavaScript with ECMAScript for XML. <a href="#refsECMA357">[ECMA357]</a></dd>
+-->
 
   </dl>
 
@@ -17700,7 +17702,7 @@ o............A....e
   <p>When examining types to determine if they represent supported languages, user agents must not
   ignore MIME parameters. Types are to be compared including all parameters.</p> <!-- whether the
   order of parameters matters is left undefined until such time as it matters; so far the only
-  relevant parameter is 'e4x' -->
+  relevant parameter was 'e4x', and it's gone for now -->
 
   <p class="note">For example, types that include the <code title="">charset</code> parameter will
   not be recognized as referencing any of the scripting languages listed above.</p>