- From: François REMY <francois.remy.dev@outlook.com>
- Date: Tue, 18 Mar 2014 17:21:40 +0100
- To: "Brian Kardell" <bkardell@gmail.com>, "Marat Tanalin" <mtanalin@yandex.ru>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "www-style list" <www-style@w3.org>
> As far as I understand, the main reason of > why Tab's original idea of using `$` has > eventually been dropped was some > uncertainty about its possible extensibility > for being used in property _names_ besides > property _values_. The reason it got dropped is that some people (including Tab) do believe we should reserve $ for mixins and other preprocessor-like operations which may potentially be added to the language at some point (e.g. futuristic things like: @define apply-2d-transform(initial-scale, initial-rotation, ...) { ... my-transform-scaling: $initial-scale; my-transform-rotation: $initial-rotation; ... transform: scale(get(my-transform-scaling)) rotate(get(my-transform-rotation)) translate(get(my-transform-translation)); will-change[]: transform; } .some-element { $apply-2d-transform(...); transition[]: transform 0.5s ease-in-out; } .some-element:hover { my-transform-scale: 1.1; } but this syntax was just made for this example, final milage may look completely different and/or offer different features)
Received on Tuesday, 18 March 2014 16:22:11 UTC