[html5] r7679 - [c] (0) Make <a href='?guitar=2&amp=1&pedal=6'> a parse error since IE9 misparse [...]

whatwg at whatwg.org whatwg at whatwg.org
Wed Jan 30 16:36:59 PST 2013


Author: ianh
Date: 2013-01-30 16:36:58 -0800 (Wed, 30 Jan 2013)
New Revision: 7679

Modified:
   complete.html
   index
   source
Log:
[c] (0) Make <a href='?guitar=2&amp=1&pedal=6'> a parse error since IE9 misparses it '?guitar=2&=1&pedal=6' apparently.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=19102
Affected topics: HTML Syntax and Parsing

Modified: complete.html
===================================================================
--- complete.html	2013-01-31 00:18:22 UTC (rev 7678)
+++ complete.html	2013-01-31 00:36:58 UTC (rev 7679)
@@ -90137,9 +90137,14 @@
     SEMICOLON character (;), and the next character is either a U+003D EQUALS SIGN character (=) or
     an <a href=#alphanumeric-ascii-characters title="alphanumeric ASCII characters">alphanumeric ASCII character</a>, then, for
     historical reasons, all the characters that were matched after the U+0026 AMPERSAND character
-    (&) must be unconsumed, and nothing is returned.</p> <!-- "=" added because of
+    (&) must be unconsumed, and nothing is returned. <!-- "=" added because of
     http://www.w3.org/Bugs/Public/show_bug.cgi?id=9207#c5 -->
 
+    However, if this next character is in fact a U+003D EQUALS SIGN character (=), then this is a
+    <a href=#parse-error>parse error</a>, because some legacy user agents <!-- IE, version 9 and before --> will
+    misinterpret the markup in those cases.</p> <!-- v2: should make this no longer a conformance
+    error at some point in the future; revisit in 2015? -->
+
     <p>Otherwise, a character reference is parsed. If the last
     character matched is not a U+003B SEMICOLON character (;), there
     is a <a href=#parse-error>parse error</a>.</p>

Modified: index
===================================================================
--- index	2013-01-31 00:18:22 UTC (rev 7678)
+++ index	2013-01-31 00:36:58 UTC (rev 7679)
@@ -90137,9 +90137,14 @@
     SEMICOLON character (;), and the next character is either a U+003D EQUALS SIGN character (=) or
     an <a href=#alphanumeric-ascii-characters title="alphanumeric ASCII characters">alphanumeric ASCII character</a>, then, for
     historical reasons, all the characters that were matched after the U+0026 AMPERSAND character
-    (&) must be unconsumed, and nothing is returned.</p> <!-- "=" added because of
+    (&) must be unconsumed, and nothing is returned. <!-- "=" added because of
     http://www.w3.org/Bugs/Public/show_bug.cgi?id=9207#c5 -->
 
+    However, if this next character is in fact a U+003D EQUALS SIGN character (=), then this is a
+    <a href=#parse-error>parse error</a>, because some legacy user agents <!-- IE, version 9 and before --> will
+    misinterpret the markup in those cases.</p> <!-- v2: should make this no longer a conformance
+    error at some point in the future; revisit in 2015? -->
+
     <p>Otherwise, a character reference is parsed. If the last
     character matched is not a U+003B SEMICOLON character (;), there
     is a <a href=#parse-error>parse error</a>.</p>

Modified: source
===================================================================
--- source	2013-01-31 00:18:22 UTC (rev 7678)
+++ source	2013-01-31 00:36:58 UTC (rev 7679)
@@ -104601,9 +104601,14 @@
     SEMICOLON character (;), and the next character is either a U+003D EQUALS SIGN character (=) or
     an <span title="alphanumeric ASCII characters">alphanumeric ASCII character</span>, then, for
     historical reasons, all the characters that were matched after the U+0026 AMPERSAND character
-    (&) must be unconsumed, and nothing is returned.</p> <!-- "=" added because of
+    (&) must be unconsumed, and nothing is returned. <!-- "=" added because of
     http://www.w3.org/Bugs/Public/show_bug.cgi?id=9207#c5 -->
 
+    However, if this next character is in fact a U+003D EQUALS SIGN character (=), then this is a
+    <span>parse error</span>, because some legacy user agents <!-- IE, version 9 and before --> will
+    misinterpret the markup in those cases.</p> <!-- v2: should make this no longer a conformance
+    error at some point in the future; revisit in 2015? -->
+
     <p>Otherwise, a character reference is parsed. If the last
     character matched is not a U+003B SEMICOLON character (;), there
     is a <span>parse error</span>.</p>




More information about the Commit-Watchers mailing list