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

Re: [css-hierarchies] Why require the & character?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 3 Sep 2013 14:43:20 -0700
Message-ID: <CAAWBYDCuDtBFXKmD=HHwWPQyYwmgusAKftTAmDcypbJe8UpE1A@mail.gmail.com>
To: Lea Verou <lea@verou.me>
Cc: Brad Kemper <brad.kemper@gmail.com>, www-style list <www-style@w3.org>
On Tue, Sep 3, 2013 at 12:56 PM, Lea Verou <lea@verou.me> wrote:
> On Sep 2, 2013, at 22:36, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> or figure out a
>> "good enough" parsing compromise that lets us tell selectors and
>> properties apart within a small, bounded number of tokens at the
>> parser level, at the cost of sometimes misinterpreting
>> previously-valid CSS.
>
> This sounds interesting but I guess it depends on how common the previously-valid CSS is. Do you have any ideas? A while back you suggested requiring a space after the colon for properties, but I pointed out that this would break every single example of minified CSS in the wild. Do you have any other ideas in mind?

Nope, that's pretty much my only idea.  I think the only feasible idea
is to have a wrapper of some kind.  I'm partial to a simple unadorned
{} block, which I forgot to list as an option in my first email (it's
been suggested before), but Marat and Brad suggested in response.

~TJ
Received on Tuesday, 3 September 2013 21:44:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:34 UTC