This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21508 - For example, the parsing of certain named character references in attributes happens even with the closing semicolon being omitted. It is safe to include an ampersand followed by letters that do not f [...]
Summary: For example, the parsing of certain named character references in attributes ...
Status: RESOLVED DUPLICATE of bug 21507
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-02 10:34 UTC by contributor
Modified: 2013-04-10 21:51 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-04-02 10:34:32 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html
Multipage: http://www.whatwg.org/C#syntax-errors
Complete: http://www.whatwg.org/c#syntax-errors

Comment:
For example, the parsing of certain named character references in attributes
happens even with the closing semicolon being omitted. It is safe to include
an ampersand followed by letters that do not form a named character reference,
but if the letters are changed to a string that does form a named character
reference, they will be interpreted as that character instead.	In this
fragment, the attribute's value is "?bill&ted":  <a href="?bill&ted">Bill and
Ted</a>

Posted from: 59.90.159.160
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0
Comment 1 Ian 'Hixie' Hickson 2013-04-10 21:51:43 UTC 

*** This bug has been marked as a duplicate of bug 21507 ***