Summary: | parsing of unclosed strings fail | ||
---|---|---|---|
Product: | WebKit | Reporter: | jasneet <jasneet> |
Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | jasneet, tabatkins, tonyg |
Priority: | P2 | ||
Version: | 525.x (Safari 3.1) | ||
Hardware: | PC | ||
OS: | Windows XP | ||
URL: | http://www.hixie.ch/tests/adhoc/css/parsing/core-syntax/strings/investigation/002.html |
Description
jasneet
2008-04-18 19:01:54 PDT
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> (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. |