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

Re: [css3-syntax] EOF and } in at-rule preludes and selectors

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 31 Jan 2013 13:52:15 -0800
Message-ID: <CAAWBYDC=OMrRECgDP03UOMNkBvcqRNNUr7as-CSUMLrP_yzTsg@mail.gmail.com>
To: Simon Sapin <simon.sapin@kozea.fr>
Cc: "www-style@w3.org" <www-style@w3.org>
On Thu, Jan 31, 2013 at 12:23 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Tue, Jan 29, 2013 at 11:03 PM, Simon Sapin <simon.sapin@kozea.fr> wrote:
>> Le 30/01/2013 05:16, Tab Atkins Jr. a écrit :
>>> Okay, should be fixed now.  If a } occurs in a selector or an at-rule
>>> prelude, it changes behavior based on whether you're currently parsing
>>> a top-level rule or not, usually throwing the rule away.
>>
>> This is minor, but I think an unpaired } (so only for top-level rules)
>> should be consistent with an unpaired ] or ). If they are preserve tokens,
>> just append them to a selector/prelude. If not, let "consume a primitive"
>> fail and handle that.
>
> Hmm, that's a good point.  I think I'd prefer to just make them all
> syntax errors.  I guess I'll bite the bullet and make "consume a
> primitive" capable of failing.

Done.

~TJ
Received on Thursday, 31 January 2013 21:53:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:05 GMT