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

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

From: François REMY <fremycompany_pub@yahoo.fr>
Date: Tue, 17 Jan 2012 18:29:53 +0100
Message-ID: <81BEFC957B8A48E39A72433147393CD2@FREMYD2>
To: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>, "CSS 3 W3C Group" <www-style@w3.org>
Yes, sorry about that. It's not really my fault, it's due to Yahoo that add 
"[Bulk]" to message' subjects when it detect that those messages are 
distributed "in bulk" to many people. The problem is that mailing list 
messages are in this category. I find it very annoying too, but I did not 
find a way to change that behavior.

To be fair, I must admit I didn't search a lot since I hardly ever use the 
online interface of that mail address, I exclusively use for receiving 
mailing lists (and it's very recent that my activity inside mailing list has 
reached a point where I should try to fix the problem).

I'll have another look at that problem today.
François




-----Message d'origine----- 
From: Marat Tanalin | tanalin.com
Sent: Tuesday, January 17, 2012 6:10 PM
To: François REMY
Cc: Tab Atkins Jr. ; www-style@w3.org
Subject: [Bulk] Re: [Bulk] Re: @import -- allow at any place in stylesheet.

François, what does that "[Bulk]" prefix in subject mean? Why do you add 
this to original message-subjects?


17.01.2012, 20:53, "François REMY" <fremycompany_pub@yahoo.fr>:
> As a side note, it's also an optimization. As soon as the CSS file is
> received, the browser can know if there will be additionnal files to
> download. The more at the top the url is, the more quickly the new 
> download
> can start. Also, the browser know at the first non-@import rule that he
> don't need to download new (css) files. This can help to make decisions 
> for
> questions like "do I need to keep that TCP connection open?".
>
> Sometimes, enforcing rules is better than try to get people writing good
> code. It may be the case here.
>
> Regards,
> François
>
> -----Message d'origine-----
> From: Tab Atkins Jr.
> Sent: Tuesday, January 17, 2012 5:14 PM
> To: Marat Tanalin | tanalin.com
> Cc: www-style@w3.org
> Subject: [Bulk] Re: @import -- allow at any place in stylesheet.
>
> On Mon, Jan 16, 2012 at 7:36 AM, Marat Tanalin | tanalin.com
> <mtanalin@yandex.ru> wrote:
>
>>  Hello. It makes sense to allow @import at any place in CSS stylesheet.
>>
>>  For example, if we have:
>>
>>     .rule-before-example {...}
>>     .example {...}
>>     .rule-after-example {...}
>>
>>  We could have same expressed with @import:
>>
>>     @import "before-example.css";
>>     .example {...}
>>     @import "after-example.css";
>>
>>  where "after-example.css" contains:
>>
>>     .rule-after-example {...}
>>
>>  (Real-world imported stylesheets are, of course, much larger.)
>>
>>  So why should @import be disallowed here for importing
>>  "after-example.css"? This just makes development less usable/flexible.
>
> What does this help with?
>
> The restriction that @import has to appear at the top of a file is
> meant, I believe, to make it easier to understand that other files are
> being imported.  A lone @import in the middle of a file is easy to
> accidentally skip over for a human.
>
> Note that if you really want to interleave some imported code, you can
> do so by just using *more* imports, like:
>
> ---top of file---
> @import "before-example.css";
> @import "example.css";
> @import "after-example.css";
>
> ~TJ 
Received on Tuesday, 17 January 2012 17:30:33 GMT

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