18612 2008-04-18 19:01:54 -0700 parsing of unclosed strings fail 2011-01-05 11:04:58 -0800 1 1 1 Unclassified WebKit CSS 525.x (Safari 3.1) PC Windows XP RESOLVED DUPLICATE 34067 http://www.hixie.ch/tests/adhoc/css/parsing/core-syntax/strings/investigation/002.html P2 Normal --- 1 jasneet webkit-unassigned jasneet tabatkins tonyg oldest_to_newest 78205 0 jasneet 2008-04-18 19:01:54 -0700 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 329644 1 tonyg 2011-01-05 10:32:51 -0800 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> 329657 2 tonyg 2011-01-05 10:56:00 -0800 (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. 329669 3 tonyg 2011-01-05 11:04:58 -0800 *** This bug has been marked as a duplicate of bug 34067 ***