W3C home > Mailing lists > Public > www-style@w3.org > June 2015

Re: [css-variables] Why we can not use 'var()' function for normal property

From: Shane Stephens <shans@google.com>
Date: Fri, 05 Jun 2015 23:48:34 +0000
Message-ID: <CAGTfzwQDO=1fxD_pMCQbwCYzS-hT_YmkhKSeOonkd4O9B9_iMw@mail.gmail.com>
To: Chris Lilley <chris@w3.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, Sebastian Zartner <sebastianzartner@gmail.com>
Cc: Lea Verou <lea@verou.me>, "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>, Boris Zbarsky <bzbarsky@mit.edu>, www-style list <www-style@w3.org>
On Sat, Jun 6, 2015 at 8:48 AM Chris Lilley <chris@w3.org> wrote:

> Hello Tab,
>
> Friday, June 5, 2015, 11:23:30 PM, you wrote:
> > And they likely won't, either.  Applications grow to fill the memory
> > available to them.  Adding an eff-ton more memory usage to every page
> > all of a sudden will never be something ignorable.
>
> May be worth pointing out that the DOM is an API, not a memory model.
>
> Low latency/high memory vs higher latency calc-on-demand/lower memory
> tradeoffs can be made by the implementation as it sees fit.
>

Lea, Chris, anyone else who's interested:

I'll be at the F2F in Paris. I'll very happily sit down with you and
explain in detail why we think there are fundamental algorithmic reasons
that this can't work. I'll even buy the beer/wine/soft beverage of choice.
I'm only suggesting we do this face-to-face because we're going to need
lots of diagrams and Q/A back-and-forth.

If I convince you - great! You'll know that we're not just being bad actors
here. If you can convince me that there's a way forward - even better!

Does this sounds reasonable?

Cheers,
    -Shane


> --
> Best regards,
>  Chris  Lilley
>  Technical Director, W3C Interaction Domain
>
>
>
Received on Friday, 5 June 2015 23:49:12 UTC

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