| Summary: | Certain HTML structure causes parse error in Chrome and Safari | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Robert Schultz <robert> | ||||
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED INVALID | ||||||
| Severity: | Normal | CC: | ap, jchaffraix, robert | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | PC | ||||||
| OS: | OS X 10.6 | ||||||
| Attachments: |
|
||||||
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. |
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.