- From: Sylvain Galineau <galineau@adobe.com>
- Date: Sat, 13 Apr 2013 18:38:10 -0700
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- CC: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On 4/13/13 5:06 PM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote: >* Sylvain Galineau wrote: >>On 4/13/13 3:57 PM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote: >>>* fantasai wrote: >>>>So, at Rename the Web Forward [1], Sylvain and I concluded that it >>>>just might be better to use 'set-' as the prefix and 'get()' as the >>>>function name instead of 'var-' and 'var()'. > >>>Well, `get` and `set` as used here are imperative, while CSS tries to be >>>a declarative language, so this seems rather confusing to me. > >>What, specifically, would an end-user be confused about and how would >>this >>confusion manifest itself? > >The `var-` prefix exists only because a namespacing mechanism is needed >to avoid clashes between pre-defined and author-defined properties. The >`set-` prefix conveys that even less than `var-`. We call `color: blue` >a declaration, but `set` does not "declare", it "sets"; obviously there >would be a reason why the designers of this syntax chose "set" as name, >rather than something with more declarative semantics, so custom proper- >ties work differently than normal properties. Obviously `get` would get >the value associated with the name when it was last `set`, and "when" is >temporal, so in order to understand what value `get` retrieves, I have >to understand the execution order of the `set` instructions... >-- This sounds like a lot of overthinking that will not even occur to most web developers.
Received on Sunday, 14 April 2013 01:38:38 UTC