Re: [css3-animations][css3-conditional][css3-syntax] spaces after ATKEYWORD should not be required

(12/08/07 0:01), Tab Atkins Jr. wrote:
> On Mon, Aug 6, 2012 at 3:54 AM, Kang-Hao (Kenny) Lu
> <kennyluck@csail.mit.edu> wrote:
>> (12/08/06 15:16), L. David Baron wrote:
>>> That might make sense in many cases, but I'm not sure it works as a
>>> general rule; there are places in CSS where white space between
>>> tokens does make a difference (in particular, in selectors:
>>> "div/**/p" is not a valid selector while "div p" is).
>>
>> This reminds me that css3-animations and css3-conditional probably
>> shouldn't require spaces after ATKEYWORD. Namely,
> [snip]
>> I think css3-syntax should have normative statement about this as it's
>> not a good idea to reason based on something we intend to make
>> deprecated, namely, CSS 2.1 Appendix G.
> 
> Is a statement actually required in Syntax?  This falls out of the
> definition of the tokenizer - there are a lot of places where a
> comment can be inserted between things to separate tokens, where
> whitespace would otherwise be required.
> 
> What I would like to do in Syntax, though, is provide more grammar
> primitives a la property definitions, so that at-rules can be defined
> more abstractly without having to worry about the details of the
> tokenizer.

That's fine as long as mediaqueries4 defines @media. It currently
doesn't supposedly because Media Queries was thought of as something CSS
independent and @media was intentionally left to CSS 2.1, and the
details of the syntax in Appendix G.

Now that Appendix G and all syntax related parts in CSS 2.1 are supposed
to be deprecated by css3-syntax, we can reconsider that. In the
meanwhile, I would suggest css3-syntax actively try to cover this part
before some coordination between mediaqueries4 and css3-syntax happen.



Cheers,
Kenny
-- 
Web Specialist, Oupeng Browser, Beijing
Try Oupeng: http://www.oupeng.com/

Received on Tuesday, 7 August 2012 02:00:09 UTC