W3C home > Mailing lists > Public > www-style@w3.org > February 2009

Re: [css21] @import parsing

From: Peter Linss <peter.linss@hp.com>
Date: Wed, 4 Feb 2009 13:43:08 -0800
Message-Id: <0338D0CB-CC3F-46A1-934F-D0730CEF5D41@hp.com>
To: www-style@w3.org

Agreed. Perhaps the text should read: "after any well-formed  
statement", or simply "after any statement".

Peter

On Feb 4, 2009, at 9:01 AM, Håkon Wium Lie wrote:

>
> Also sprach Anne van Kesteren:
>
>> One of the tests Microsoft has is testing this:
>>
>>   1am { so:awesome }
>>   @import "me";
>>
>> It expects "me" to be loaded.
>>
>> CSS 2.1 4.1.5 says: "CSS 2.1 user agents must ignore any '@import'  
>> rule
>> that occurs inside a block or after any valid statement other than an
>> @charset or an @import rule."
>>
>> "1am { so:awesome }" is a valid statement per the CSS core syntax.
>> However, it is also not valid CSS 2.1. The text should be clarified  
>> in
>> some way since implementors ended up doing different things.
>
> I'd argue that we should not import in this case. If we do import,
> extensions in the syntax may change the behavior of imports; in this
> case, the import will stop working once "1am { so:awesome }" becomes
> legal CSS syntax.
>
> -h&kon
>              Håkon Wium Lie                          CTO °þe®ª
> howcome@opera.com                  http://people.opera.com/howcome
>
Received on Wednesday, 4 February 2009 21:43:53 GMT

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