Bug 35010 – Mishandling of \\ in 'content' property

• Status: RESOLVED
• Resolution: FIXED
• Component: CSS

[Simon Fraser (smfr)]

From: 	Boris Zbarsky <[e-mail]>
	Subject: 	Re: [css2.1] Content of a string containing a backslash followed immediately by EOF
	Date: 	February 16, 2010 4:29:07 PM PST
	To: 	Zack Weinberg <[e-mail]>
	Cc: 	[e-mail] list <[e-mail]>
	Message-Id: 	<[e-mail]>

Not sure about IE, but it looks like Webkit somehow messes up \\ at the end of the before content no matter what.  |content: "\\m";| shows a backslash followed by an 'm', but |content: "whatever\\"| shows nothing.

And even more clearly, something like this:

 <style>.a:before { content: "m\\"; } .a { content: "o\\" }</style>
 <div>a:'<span class="a">'</span></div>

Renders as:

 a:'m\"; } .a { content: '

in Webkit.  So it looks like the \\ is somehow managing to escape the '"' in Webkit's parser.

-Boris

[Han]

Created attachment 100345 [details]
jsFiddle test cases

[Han]

Actually, \\ at the end of the the quoted string works fine as long as there's no more of the same kind of quote (single or double) on the same line. See http://jsfiddle.net/gfLDV/8/ .

This is actually really annoying because that means (the way I discovered it) if every declaration is on it's own like there's no problem, but then CSS compressor removes newlines and suddenly WebKit thinks the content is a gigantic string of compressed CSS up to the last matching quote.

(Test case is identical if you replace before with after or the single quotes with double quotes.)

[Elliott Sprehn]

The test case passes in Webkit nightlies/Chrome 20, this was probably fixed a while ago.