Summary: | Tokenizer stuck in ScriptDataDoubleEscapedState | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Tony Gentilcore <tonyg> | ||||
Component: | WebCore Misc. | Assignee: | Tony Gentilcore <tonyg> | ||||
Status: | RESOLVED WONTFIX | ||||||
Severity: | Normal | CC: | abarth, eric, gregsimon, ian | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 41115 | ||||||
Attachments: |
|
Crazy. That makes very little sense. No, you're just in ScriptDataDoubleEscapedState. It's a comment inside of the script tag. I don't remember why we have all these escape states, but it's to model something. tests16.dat (line 1498) has nearly this exact test case. I'm going to fire up the debugger and see what it is doing. Amusingly, but bug is a victim of itself. Filed spec bug http://www.w3.org/Bugs/Public/show_bug.cgi?id=12398 This is working as intended per http://www.w3.org/Bugs/Public/show_bug.cgi?id=12398 |
Created attachment 87441 [details] testcase See attached test case. FF4 behaves the same way so this is likely a spec bug. IE7-9: PASS SF5: PASS OP11: PASS FF3.6: PASS FF4: FAIL CR10-12: FAIL