Christopher Schultz-2 wrote:
>
> You're right in that @import appears to serialize CSS fetching in many
> browsers, and that's bad. On the other hand, why not use Steve's
> suggestion and use the LINK LINK technique?
>
> Presumably you have separate stylesheets for a reason. Why not keep them
>
I suggest you read the links I posted if you're interested in the why.
Curtis Garman wrote:
>
> What does it matter if you are allowing your css to cache in the user's
> browser?
>
> On Fri, Oct 23, 2009 at 3:19 PM, rowlando wrote:
>>
>> I'm a fron
I'm a front-end developer rather than a back-end dev so this might explain my
silly questions. "80% of the end-user response time is spent on the
front-end", so says the YUI performance blog. Anything that can be done on
the front-end to aid better performance is simply good practice.
The reason
Pid Ster wrote:
>
> On 23/10/2009 11:50, rowlando wrote:
>
> Why?
>
> - Why do this with a JSP/Servlet?
>
> - Why not concatenate it into a single CSS file at build time, prior to
> deployment?
>
> - Why not use the CSS import directive?
>
> Servin
Hi there,
For maintenance purposes I want to keep stylesheets in separate files.
However, when served, they should be concatenated together as a single file.
Simply, I have a file called global.css with the following:
<%@ include file="../global/i_base.css" %>
<%@ include file="../global/i_heade
