Intent to Remove: CSS Variables

Showing 1-10 of 10 messages
Intent to Remove: CSS Variables Alan Cutter 2/9/14 3:15 PM

Primary eng (and PM) emails

alanc...@chromium.org

mikel...@chromium.org


Summary

Remove unfinished implementation of the CSS Variables spec.

http://www.w3.org/TR/css-variables-1/


Motivation

Our CSS Variables implementation in its current state needs a rewrite before it is ready to ship.

Our Bison CSS Parser is slated to be rewritten from scratch, this would result in another rewrite of the variables implementation.

If we were to ship CSS Variables with our current parser we would see little performance benefit over using a Javascript framework to accomplish the same thing.

Our priority for Blink this year is performance on mobile, CSS Variables will be revisited after we tackle our performance deficiencies.

Usage information from UseCounter

CSS Variables usage is not counted.


Compatibility Risk

CSS Variables is not shipped, removal poses minimal disruption to the web.

Firefox has an implementation in progress available on their Nightly channel.

https://hacks.mozilla.org/2013/12/css-variables-in-firefox-nightly/

Webkit has removed their implementation (which we inherited).

https://bugs.webkit.org/show_bug.cgi?id=114119


Row on feature dashboard

http://www.chromestatus.com/features/6401356696911872


Re: [blink-dev] Intent to Remove: CSS Variables Kenneth Rohde Christiansen 2/10/14 2:23 AM
lgtm
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+...@chromium.org.



--
Kenneth Rohde Christiansen
Web Platform Architect, Intel Corporation.
Phone  +45 4294 9458 ﹆﹆﹆
Re: [blink-dev] Intent to Remove: CSS Variables Tab Atkins Jr. 2/10/14 3:19 PM
lgtm2

On Sun, Feb 9, 2014 at 3:15 PM, Alan Cutter <alanc...@google.com> wrote:
> Motivation
>
> Our CSS Variables implementation in its current state needs a rewrite before
> it is ready to ship.
>
> Our Bison CSS Parser is slated to be rewritten from scratch, this would
> result in another rewrite of the variables implementation.
>
> If we were to ship CSS Variables with our current parser we would see little
> performance benefit over using a Javascript framework to accomplish the same
> thing.
>
> Our priority for Blink this year is performance on mobile, CSS Variables
> will be revisited after we tackle our performance deficiencies.

To make it clearer to those watching at home, our current Variables
impl is pretty hacky, and kinda intrusive and slow (of the "everything
slows down when you use it" variety).  We know roughly how to
implement it faster, but doing it right depends on some other rewrites
we intend on doing, so we'll re-add this later when they're done.

This is definitely not a judgement on the feature itself.

~TJ
Re: [blink-dev] Intent to Remove: CSS Variables Elliott Sprehn 2/10/14 3:22 PM

+1, lgtm.
Re: [blink-dev] Intent to Remove: CSS Variables Ojan Vafai 2/10/14 3:29 PM
lgtm

:(

+1 to not being a judgment on the feature itself.
Re: [blink-dev] Intent to Remove: CSS Variables Alex Russell 2/10/14 4:21 PM
Same. Sad to see this delayed, but if this speeds it along, so be it.


To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

Re: [blink-dev] Intent to Remove: CSS Variables Dimitri 2/11/14 9:01 AM
LGTM3. It's not good bye. It's see you later.
Re: [blink-dev] Intent to Remove: CSS Variables Kent Tamura 2/11/14 9:16 PM
lgtm with sadness.

--
TAMURA Kent
Software Engineer, Google


Re: Intent to Remove: CSS Variables Daniel Elebash 11/17/14 12:04 PM
Any update on if this feature is being worked on or is it still on hold for the originally stated reasons?

Thanks,
Dan
Re: Intent to Remove: CSS Variables Alan Cutter 11/17/14 1:40 PM
This feature is still on hold pending replacing the Bison parser. See meta tracking bug for the parser refactor: crbug.com/330389