When the @import rule is used in the html markup to hide advanced css
from older browsers, is that css downloaded with every page from a
site? (which would be redundant)

Or is it different if you link to, say, simple.css, which then
"@imports" advanced.css?

How can I reduce the bandwidth load (i.e. client get the css from the
client cache) or is it not an option with @import?

TIA

Dave Higgins

google@higginsnet.com (Dave Higgins) wrote:
[color=blue]
>When the @import rule is used in the html markup to hide advanced css
>from older browsers, is that css downloaded with every page from a
>site? (which would be redundant)[/color]

No it can be cached, same as any other file.
[color=blue]
>Or is it different if you link to, say, simple.css, which then
>"@imports" advanced.css?[/color]

They can both be cached.
[color=blue]
>How can I reduce the bandwidth load (i.e. client get the css from the
>client cache) or is it not an option with @import?[/color]

Nothing you need to do, normally. If your server is sending out http
headers with .css files that discourage caching then that would be a
problem.

Steve

--
"My theories appal you, my heresies outrage you,
I never answer letters and you don't like my tie." - The Doctor

Steve Pugh <steve@pugh.net> <http://steve.pugh.net/>

On 20 Jan 2004 00:22:25 -0800, google@higginsnet.com (Dave Higgins)
wrote:
[color=blue]
>When the @import rule is used in the html markup to hide advanced css
>from older browsers, is that css downloaded with every page from a
>site? (which would be redundant)[/color]

No. In fact I make use of that to determine what percentage of my
visitors are using older browsers, based on the site logs. (Still around
3%).

--
Stephen Poley

http://www.xs4all.nl/~sbpoley/webmatters/