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

AW: CSS: grouping sub-element styles for a specific class/id/tag in CSS3?

From: Sascha Meyer <harlequin2@gmx.de>
Date: Thu, 30 Sep 2010 10:42:19 +0200
To: "'Tab Atkins Jr.'" <jackalmage@gmail.com>
Cc: <www-style@w3.org>
Message-ID: <005701cb607b$64ebf3e0$2ec3dba0$@de>
Goog morning TJ,

I understand that a change like my suggested one is not easy to implement, 
I hadn't thought about CSS's core grammar and which impact such a change 
would have.
Thank you for the comprehensive explanation and the link to lesscss.org, 
will take a closer look at CSS compilers.

Best regards,


-----Urspr√ľngliche Nachricht-----
Von: Tab Atkins Jr. [mailto:jackalmage@gmail.com] 
Gesendet: Mittwoch, 29. September 2010 21:24
An: Sascha Meyer
Cc: www-style@w3.org
Betreff: Re: CSS: grouping sub-element styles for a specific class/id/tag in CSS3?

On Wed, Sep 29, 2010 at 7:53 AM, Sascha Meyer <harlequin2@gmx.de> wrote:
> Hi W3C-list,
> I am wondering if CSS3 will have a mechanism to group child rules for one
> class/id/tag? I had the idea this morning when I had to write rules similar
> to this:
> [CSS]
> #header #navigation {. }
> #header #navigation ul {. }
> #header #navigation ul li {. }
> [/CSS]
> So I thought that a syntax similar to the following could be pretty handy
> because you'd find all rules for sub-elements inside the parent's css rule:
> [CSS]
> #header #navigation {
>  ul {
>    li {
>      /* li's css rules */
>      ...
>    }
>    /* ul's css rules */
>    ...
>  }
>  /* #header #navigation's css rules */
>  ...
> }
> [/CSS]
> Less writing, more structure, the sequence of appearance could also be
> predefined (i.e. if a class defines sub-element rules, these have to be
> defined first, after this the class' own style rules have to be defined)
> which could help reading longer CSS stylesheets much more easy.

This has been suggested a few times.  I agree that it's a fairly
useful sort of thing to have; I've often had big blocks of selectors
repeated over and over again with changes just to the last bit of it.

However, this is a major violation of CSS's Core Grammar, the thing
that specifies how CSS is parsed in general.  We try to minimize the
changes to the Core Grammar, because it constitutes a sort of contract
with implementors.

Luckily, there are tools that can help with this.  There are CSS
compilers, like LESS (http://lesscss.org/), that can handle nested
blocks like this and will translate it into vanilla CSS for you.  They
also offer other useful abilities, like Variables and Mixins, which
haven't made it into CSS yet.  Perhaps you can try using one of those?

Received on Thursday, 30 September 2010 09:09:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:49:48 UTC