Bug 19084 - HTMLTokenizer::addAttribute does not check for all the specification violation
Summary: HTMLTokenizer::addAttribute does not check for all the specification violation
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-15 12:59 PDT by Julien Chaffraix
Modified: 2010-09-20 02:43 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Chaffraix 2008-05-15 12:59:17 PDT 
According to the HTML5 specification (section 8.1.2.3. Attributes):

"Attribute names must consist of one character other than the space characters, U+003E GREATER-THAN SIGN (>), and U+002F SOLIDUS (/), followed by zero or more characters other than the space characters, U+003E GREATER-THAN SIGN (>), U+002F SOLIDUS (/), and U+003D EQUALS SIGN (=)."

Currently we only check for the presence of '/' in attribute in HTMLTokenizer::addAttribute.
Comment 1 Julien Chaffraix 2008-05-15 13:49:05 PDT 
Whoever handles this bug, changes in the assertion should be matched with changes in the parser code to avoid hitting the assertion.
Check bug 13942 for the details.
Comment 2 Adam Barth 2010-09-20 02:43:45 PDT 
The spec has changed not to include the text you quote, but I believe you're quoting an authoring requirement and not a user agent conformance requirement.  If that's not accurate, please re-open this bug with a reference to the user agent conformance requirement you believe we violate.