Bug 37348 - Certain HTML structure causes parse error in Chrome and Safari
Summary: Certain HTML structure causes parse error in Chrome and Safari
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.6
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-09 12:03 PDT by Robert Schultz
Modified: 2010-04-09 16:34 PDT (History)
3 users (show)

See Also:


Attachments
HTML that causes a parse error (269 bytes, text/html)
2010-04-09 12:03 PDT, Robert Schultz
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Schultz 2010-04-09 12:03:23 PDT
Created attachment 52973 [details]
HTML that causes a parse error

This only happens in Chrome and Safari.

Firefox loads it just fine.

See the attached test case HTML file.

Attempting to load it in Chrome or Safari causes a parse error.

If you remove the conditional comment block, OR the empty script block below the conditional comment, the page parses correctly.
Comment 1 Alexey Proskuryakov 2010-04-09 16:34:15 PDT
Firefox 3.6.3 parses this file exactly like Safari does, and also logs an error to console.

The problem with this test is that "--\\\>" doesn't (and shouldn't) close a comment.