W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: @import -- allow at any place in stylesheet.

From: Ambrose LI <ambrose.li@gmail.com>
Date: Tue, 17 Jan 2012 17:54:25 -0500
Message-ID: <CADJvFOWeEcdCmPcczZD+2tGk61RSCxipFs1jLD9xBMpQz8WGZg@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>, www-style@w3.org
2012/1/17 Tab Atkins Jr. <jackalmage@gmail.com>:
> 2012/1/17 Marat Tanalin | tanalin.com <mtanalin@yandex.ru>:
>> 18.01.2012, 01:35, "Tab Atkins Jr." <jackalmage@gmail.com>:
>>> Stepping outside this problem, you shouldn't really be using @import
>>> in your stylesheets anyway.  It's bad for performance, since it makes
>>> your stylesheets download one-by-one instead of in parallel.  Making
>>> @import more powerful might encourage more use of this, which I'd
>>> personally prefer to avoid.  It's better to either link in multiple
>>> stylesheets via multiple <link> elements (so the browser can start
>>> downloading all of them at once), or use a preprocessor to munge the
>>> sheets together into a single file so you can pull them all down with
>>> a single request.
>>
>> As I've already said, there are different situations: internet, intRAnet, local webpages opened from CD. Delay concern is generally applicable to former one only, but current limitation is applied forcedly and harmfully to all of them.
>
> We only really care about the web, since the vast vast majority of
> pages using our tech are web pages.  Making choices that are bad for
> the web but offer a minor benefit to non-web usage isn't a good
> tradeoff.
>

If we cared “only about the web” then we can throw a whole bunch of
W3C initiatives out of the window. As it is, CSS is now caring about
things that even some professional typesetting systems are unable to
currently do.



-- 
cheers,
-ambrose
Received on Tuesday, 17 January 2012 22:54:53 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:48 GMT