Hi,

There are some known issues with CSS handler that would be difficult to fix and are unlikely to be fixed unless someone comes along who is much more skilled with regular expressions than myself and is able to provide a fix.

What I can tell you is that the problem happens because of the way we must change css background images to have urls that are relative to the root of the site and we use regex to find them and insert the base url.

In general the css handler is able to process them correctly so long as the opening and closing parenthesis are on the same line within the raw css and if no 2 sets of parenthesis are on any single line.

So for example I "think" it should work if the raw css is formatted like this:

#ctl00_mainContent_OrderDetailView1_lblTicketPrice:after { 
content:' (not really! The actual amount will be on your invoice) ';
 }

so that both the opening parenthesis and closing parenthesis are on the same line with no other parenthesis on that line.

But if it doesn't work I don't know  how to fix it.

I do know that when using multiple comma separated background images in css there are problems which can be fixed by putting each image on its own line with its own parenthesis so hopefully the same solution would work for this problem.

Hope that helps,

Joe

Hi Crispin,

The relevant code is in CSSHandler.cs (stylesheet combiner doesn't really do the combining it just links to the csshandler), yes as far as a I recall its all about resolving background image urls to make them either fully qualified or relative to the site root. The regex expression is defined near the top so if you have a guru who can make the expression work better that would be cool with me. We could potentially move the regex expression into a web.config setting to make it easier to modify.

In general myself I am moving away from use of csshandler with my sites choosing instead to copy the combined and minified css output from the handler into a static css file and linking that directly instead of csshandler to reduce the overhead of processing the css. I'll be doing that soon on this site and writing some documentation about how to do it. CSSHandler is convenient but once the design is completed and won't be changing I think it makes sense to remove css handler from the equation for best performance because even though the css is cached it is a fairly heavy request to process when it isn't cached or when the cache is expired.

Best,

Joe