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

Re: Extending Class Proposal

From: Chris Eppstein <chris@eppsteins.net>
Date: Fri, 1 Feb 2013 11:41:33 -0800
Message-ID: <CANyEp6UWguFZWemT5-=xUQdJHJufkTfeXkRRTQ28Nc4WiQt15A@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Philip Walton <philip@philipwalton.com>, www-style list <www-style@w3.org>

As the co-creator of Sass @extend feature, I fully endorse bringing it to
CSS and have been calling for this when I speak at conferences and blog.
I'm glad that Philip agrees. Our preprocessor implementation of the feature
is great, but the fundamental limitations are many as Philip has pointed
out. Another limitation that was missed is that in Sass, the @extend
directive is scoped to a single css file, but in the browser, the extend
could transcend files which makes it much easier to be more efficient with
the serving of stylesheets.

If anyone has questions about our implementation or the "theory" behind it,
please don't hesitate to ask me.

Chris Eppstein

On Thu, Jan 31, 2013 at 10:29 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> On Thu, Jan 31, 2013 at 10:20 PM, Philip Walton <philip@philipwalton.com>
> wrote:
> > On Thu, Jan 31, 2013 at 1:10 PM, Tab Atkins Jr. <jackalmage@gmail.com>
> > wrote:
> >> No, we wouldn't break anyone, *because you can't extend anything yet*.
> >
> > I wasn't accusing you or Chrome of breaking anything, I was simply
> pointing
> > out why the current Sass syntax, which you were promoting in a previous
> > email, wouldn't lend itself well to a querySelectorAll function.
> Sorry, I wasn't trying to imply that.  I'm saying that adding the
> ability won't break anything for anyone.  It *can't*.  You can't get
> "expanded results" until you actually start *using* the new feature,
> at which point it's your own fault if anything goes wrong.
> ~TJ
Received on Friday, 1 February 2013 19:42:01 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:08 UTC