WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED DUPLICATE of
bug 34067
18612
parsing of unclosed strings fail
https://bugs.webkit.org/show_bug.cgi?id=18612
Summary
parsing of unclosed strings fail
jasneet
Reported
2008-04-18 19:01:54 PDT
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
Attachments
Add attachment
proposed patch, testcase, etc.
Tony Gentilcore
Comment 1
2011-01-05 10:32:51 PST
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
Comment 2
2011-01-05 10:56:00 PST
(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
Comment 3
2011-01-05 11:04:58 PST
*** This bug has been marked as a duplicate of
bug 34067
***
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug