[html5] r8870 - [aci] (0) With great reluctance, admit X-UA-Compatible exists. Fixing https://ww [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Dec 3 13:48:48 PST 2014
Author: ianh
Date: 2014-12-03 13:48:44 -0800 (Wed, 03 Dec 2014)
New Revision: 8870
Modified:
complete.html
index
source
Log:
[aci] (0) With great reluctance, admit X-UA-Compatible exists.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=27091
Affected topics: HTML, HTML Syntax and Parsing
Modified: complete.html
===================================================================
--- complete.html 2014-12-03 21:32:26 UTC (rev 8869)
+++ complete.html 2014-12-03 21:48:44 UTC (rev 8870)
@@ -9728,6 +9728,9 @@
<tr><td><a href=#attr-meta-http-equiv-set-cookie id=pragma-directives:attr-meta-http-equiv-set-cookie>Cookie setter</a>
<td><code>set-cookie</code>
<td>Non-conforming
+ <tr><td><span>X-UA-Compatible</span>
+ <td><code>x-ua-compatible</code>
+ <td>
</table>
@@ -9925,9 +9928,22 @@
consisting of the value of the element's <code id=pragma-directives:attr-meta-content-11><a href=#attr-meta-content>content</a></code>
attribute encoded as UTF-8. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsENCODING>[ENCODING]</a></ol>
+ <dt><dfn id=attr-meta-http-equiv-x-ua-compatible>X-UA-Compatible state</dfn> (<code>http-equiv="x-ua-compatible"</code>)
+
+ <dd>
+
+ <p>In practice, this pragma encourages Internet Explorer to more closely follow the
+ specifications.</p>
+
+ <p>For <code id=pragma-directives:the-meta-element-15><a href=#the-meta-element>meta</a></code> elements with an <code id=pragma-directives:attr-meta-http-equiv-8><a href=#attr-meta-http-equiv>http-equiv</a></code>
+ attribute in the <span>X-UA-Compatible state</span>, the
+ <code id=pragma-directives:attr-meta-content-12><a href=#attr-meta-content>content</a></code> attribute must have the value "<code>IE=edge</code>".</p>
+
+ <p>User agents are required to ignore this pragma.</p>
+
</dl><div class=status><input onclick=toggleStatus(this) value=⋰ type=button><p class=bugs><strong>Spec bugs:</strong> <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27164" title="API to cancel <meta refresh>, so that XHTML content can use it as a script fallback">27164</a></div>
- <p>There must not be more than one <code id=pragma-directives:the-meta-element-15><a href=#the-meta-element>meta</a></code> element with any particular state in the
+ <p>There must not be more than one <code id=pragma-directives:the-meta-element-16><a href=#the-meta-element>meta</a></code> element with any particular state in the
document at a time.</p>
@@ -77649,7 +77665,7 @@
<p>When an <a href=#xml-parser id=parsing-xhtml-documents:xml-parser-11>XML parser</a> reaches the end of its input, it must <a href=#stop-parsing id=parsing-xhtml-documents:stop-parsing>stop
parsing</a>, following the same rules as the <a href=#html-parser id=parsing-xhtml-documents:html-parser-2>HTML parser</a>. An <a href=#xml-parser id=parsing-xhtml-documents:xml-parser-12>XML
- parser</a> can also be <a href=#abort-a-parser id=parsing-xhtml-documents:abort-a-parser>aborted</a>, which must again by done in
+ parser</a> can also be <a href=#abort-a-parser id=parsing-xhtml-documents:abort-a-parser>aborted</a>, which must again be done in
the same way as for an <a href=#html-parser id=parsing-xhtml-documents:html-parser-3>HTML parser</a>.</p>
<p>For the purposes of conformance checkers, if a resource is determined to be in <a href=#the-xhtml-syntax id=parsing-xhtml-documents:the-xhtml-syntax>the XHTML
Modified: index
===================================================================
--- index 2014-12-03 21:32:26 UTC (rev 8869)
+++ index 2014-12-03 21:48:44 UTC (rev 8870)
@@ -9728,6 +9728,9 @@
<tr><td><a href=#attr-meta-http-equiv-set-cookie id=pragma-directives:attr-meta-http-equiv-set-cookie>Cookie setter</a>
<td><code>set-cookie</code>
<td>Non-conforming
+ <tr><td><span>X-UA-Compatible</span>
+ <td><code>x-ua-compatible</code>
+ <td>
</table>
@@ -9925,9 +9928,22 @@
consisting of the value of the element's <code id=pragma-directives:attr-meta-content-11><a href=#attr-meta-content>content</a></code>
attribute encoded as UTF-8. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsENCODING>[ENCODING]</a></ol>
+ <dt><dfn id=attr-meta-http-equiv-x-ua-compatible>X-UA-Compatible state</dfn> (<code>http-equiv="x-ua-compatible"</code>)
+
+ <dd>
+
+ <p>In practice, this pragma encourages Internet Explorer to more closely follow the
+ specifications.</p>
+
+ <p>For <code id=pragma-directives:the-meta-element-15><a href=#the-meta-element>meta</a></code> elements with an <code id=pragma-directives:attr-meta-http-equiv-8><a href=#attr-meta-http-equiv>http-equiv</a></code>
+ attribute in the <span>X-UA-Compatible state</span>, the
+ <code id=pragma-directives:attr-meta-content-12><a href=#attr-meta-content>content</a></code> attribute must have the value "<code>IE=edge</code>".</p>
+
+ <p>User agents are required to ignore this pragma.</p>
+
</dl><div class=status><input onclick=toggleStatus(this) value=⋰ type=button><p class=bugs><strong>Spec bugs:</strong> <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27164" title="API to cancel <meta refresh>, so that XHTML content can use it as a script fallback">27164</a></div>
- <p>There must not be more than one <code id=pragma-directives:the-meta-element-15><a href=#the-meta-element>meta</a></code> element with any particular state in the
+ <p>There must not be more than one <code id=pragma-directives:the-meta-element-16><a href=#the-meta-element>meta</a></code> element with any particular state in the
document at a time.</p>
@@ -77649,7 +77665,7 @@
<p>When an <a href=#xml-parser id=parsing-xhtml-documents:xml-parser-11>XML parser</a> reaches the end of its input, it must <a href=#stop-parsing id=parsing-xhtml-documents:stop-parsing>stop
parsing</a>, following the same rules as the <a href=#html-parser id=parsing-xhtml-documents:html-parser-2>HTML parser</a>. An <a href=#xml-parser id=parsing-xhtml-documents:xml-parser-12>XML
- parser</a> can also be <a href=#abort-a-parser id=parsing-xhtml-documents:abort-a-parser>aborted</a>, which must again by done in
+ parser</a> can also be <a href=#abort-a-parser id=parsing-xhtml-documents:abort-a-parser>aborted</a>, which must again be done in
the same way as for an <a href=#html-parser id=parsing-xhtml-documents:html-parser-3>HTML parser</a>.</p>
<p>For the purposes of conformance checkers, if a resource is determined to be in <a href=#the-xhtml-syntax id=parsing-xhtml-documents:the-xhtml-syntax>the XHTML
Modified: source
===================================================================
--- source 2014-12-03 21:32:26 UTC (rev 8869)
+++ source 2014-12-03 21:48:44 UTC (rev 8870)
@@ -14168,6 +14168,10 @@
<td><span data-x="attr-meta-http-equiv-set-cookie">Cookie setter</span>
<td><code data-x="">set-cookie</code>
<td>Non-conforming
+ <tr>
+ <td><span data-x="attr-meta-http-x-ua-compatible">X-UA-Compatible</span>
+ <td><code data-x="">x-ua-compatible</code>
+ <td>
</table>
<!--
@@ -14542,6 +14546,23 @@
</dd>
+
+ <dt><dfn data-x="attr-meta-http-equiv-x-ua-compatible">X-UA-Compatible state</dfn> (<code data-x="">http-equiv="x-ua-compatible"</code>)
+
+ <dd>
+
+ <p>In practice, this pragma encourages Internet Explorer to more closely follow the
+ specifications.</p>
+
+ <p>For <code>meta</code> elements with an <code data-x="attr-meta-http-equiv">http-equiv</code>
+ attribute in the <span data-x="attr-meta-http-x-ua-compatible">X-UA-Compatible state</span>, the
+ <code data-x="attr-meta-content">content</code> attribute must have the value "<code
+ data-x="">IE=edge</code>".</p>
+
+ <p>User agents are required to ignore this pragma.</p>
+
+ </dd>
+
</dl>
<p>There must not be more than one <code>meta</code> element with any particular state in the
@@ -106142,7 +106163,7 @@
<p>When an <span>XML parser</span> reaches the end of its input, it must <span>stop
parsing</span>, following the same rules as the <span>HTML parser</span>. An <span>XML
- parser</span> can also be <span data-x="abort a parser">aborted</span>, which must again by done in
+ parser</span> can also be <span data-x="abort a parser">aborted</span>, which must again be done in
the same way as for an <span>HTML parser</span>.</p>
<p>For the purposes of conformance checkers, if a resource is determined to be in <span>the XHTML
More information about the Commit-Watchers
mailing list