W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: Thinking about mixins as a new type of selector

From: François REMY <fremycompany_pub@yahoo.fr>
Date: Thu, 16 Aug 2012 13:12:45 +0200
Message-ID: <823D4528EC8A4AB787269D175C0DD562@FREMYD2>
To: "Pete Boere" <pete@the-echoplex.net>, "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "Chris Eppstein" <chris@eppsteins.net>, "Brian Kardell" <bkardell@gmail.com>, <www-style@w3.org>, "L. David Baron" <dbaron@dbaron.org>
|  Is there any reason mixins/extends shouldn't use property
|  syntax? Since variables will be using property:value
|  notation, why not use it for this use-case as well.

Yes, there is. Because CSS “variables” are custom properties, meaning they 
are properties like any other: they cascade, they're inherited, they're tied 
to an element (not a rule or a stylesheet). As such, it makes sense to use 
the propery syntax for them.

To the contrary, @extend and mixins are not property declarations. 
Received on Thursday, 16 August 2012 11:13:11 UTC

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