Skip to content

Commit

Permalink
[aci] (0) With great reluctance, admit X-UA-Compatible exists.
Browse files Browse the repository at this point in the history
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=27091
Affected topics: HTML, HTML Syntax and Parsing

git-svn-id: https://svn.whatwg.org/webapps@8870 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Dec 3, 2014
1 parent fa0940f commit 86cf490
Show file tree
Hide file tree
Showing 3 changed files with 58 additions and 5 deletions.
20 changes: 18 additions & 2 deletions complete.html
Expand Up @@ -9728,6 +9728,9 @@ <h5 id=pragma-directives>4.2.5.3 Pragma directives</h5>
<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>


Expand Down Expand Up @@ -9925,9 +9928,22 @@ <h5 id=pragma-directives>4.2.5.3 Pragma directives</h5>
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>


Expand Down Expand Up @@ -77649,7 +77665,7 @@ <h3 id=parsing-xhtml-documents>13.2 Parsing XHTML documents</h3><div class=statu

<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
Expand Down
20 changes: 18 additions & 2 deletions index
Expand Up @@ -9728,6 +9728,9 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
<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>


Expand Down Expand Up @@ -9925,9 +9928,22 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
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>


Expand Down Expand Up @@ -77649,7 +77665,7 @@ document.body.appendChild(text);

<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
Expand Down
23 changes: 22 additions & 1 deletion source
Expand Up @@ -14168,6 +14168,10 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
<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>

<!--
Expand Down Expand Up @@ -14542,6 +14546,23 @@ people expect to have work and what is necessary.

</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
Expand Down Expand Up @@ -106142,7 +106163,7 @@ document.body.appendChild(text);

<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
Expand Down

0 comments on commit 86cf490

Please sign in to comment.