Bug 18612 – parsing of unclosed strings fail

• Component: CSS
• Status: RESOLVED DUPLICATE

[jasneet]

I Steps:
Go to http://www.hixie.ch/tests/adhoc/css/parsing/core-syntax/strings/investigation/002.html

II Issue:
* fails to span multiple lines
* unterminated strings and content after unclosed strings not supported
* ignores unclosed strings

III Conclusion:
issue with parsing of unclosed strings

IV Other browsers:
IE7: ok
FF3: not ok
Opera9.24: not ok

V Nightly tested: 32005

[Tony Gentilcore]

This came up in http://code.google.com/p/chromium/issues/detail?id=68594

Hixie's test is more thorough, but here's my little case that will show a blue page in WebKit but a red page in Firefox:
<style>
body{background:red}
foo{bar"}
body{background:blue}
</style>

[Tony Gentilcore]

(In reply to comment #1)
> This came up in http://code.google.com/p/chromium/issues/detail?id=68594
> 
> Hixie's test is more thorough, but here's my little case that will show a blue page in WebKit but a red page in Firefox:
> <style>
> body{background:red}
> foo{bar"}
> body{background:blue}
> </style>

Here is the relevant part of the spec:
http://www.w3.org/TR/CSS21/syndata.html#parsing-errors (see "Unexpected end of string").

In the case above, Firefox gets it right. The blue declaration should be dropped and the page should be red.

[Tony Gentilcore]

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