- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 29 Mar 2010 08:47:36 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9351
Maciej Stachowiak <mjs@apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Do not interpret & followed |Do not interpret & followed
|by an entity name followed |by an entity name followed
|by = as an entity reference |by = as an entity reference
|(possibly just in attribute |in attribute values (maybe
|values) |in text content too)
--- Comment #4 from Maciej Stachowiak <mjs@apple.com> 2010-03-29 08:47:35 ---
Further correction: the "additional allowed character" is a pretty minor
difference, because it applies only right after the ampersand. The actual key
difference is:
"If the character reference is being consumed as part of an attribute, and the
last character matched is not a U+003B SEMICOLON character (;), and the next
character is in the range U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9),
U+0041 LATIN CAPITAL LETTER A to U+005A LATIN CAPITAL LETTER Z, or U+0061 LATIN
SMALL LETTER A to U+007A LATIN SMALL LETTER Z, then, for historical reasons,
all the characters that were matched after the U+0026 AMPERSAND character (&)
must be unconsumed, and nothing is returned."
Adding = to that list would effect the change proposed here, but only for
attribute values, not for text. However, since processing of entities is
already quite a bit different between attribute values and text content, I am
no longer so sure that making this change for text content too is warranted.
Updating title to bias it a bit the other way.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 29 March 2010 08:47:37 UTC