- From: Florian Rivoal <florian@rivoal.net>
- Date: Sat, 20 Jun 2015 16:36:53 +0200
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: Marat Tanalin <mtanalin@yandex.ru>, "www-style@w3.org" <www-style@w3.org>
> On 20 Jun 2015, at 13:26, fantasai <fantasai.lists@inkedblade.net> wrote: > > On 06/19/2015 09:14 PM, Marat Tanalin wrote: >> 20.06.2015, 01:51, "fantasai" <fantasai.lists@inkedblade.net>: >>> Cascading L4 has one major open issue: >>> the keyword name 'default' conflicts with a value of the 'cursor' property >>> So we need a new keyword. Opinions and suggestions welcome. >> >> `ua-default` looks most clear and natural (this is the first option that came to my mind _before_ reading the related discussion you've mentioned). There is a user agent (not necessarily a browser, so `browser-default` would be just incorrect), there are default values specific to each user agent, expanded `user-agent-default` would be too long, just `user-agent` (without the `-default` part) would probably be somewhat ambiguous/unclear (e.g. someone could expect that `user-agent` value means "put the user-agent string here"). >> >> `default-value` is acceptable too, though probably not as straightforward as `ua-default`. > > The problem with ua-default or any such thing is that it's only > correct terminology for the effect when it's used in a user-level > style sheet. If it's used in a author- or user-level style sheet, > it does not return the value to the UA default value. > > The problem with 'default-value' is that it's inconsistent with > the other global keywords, which are not called 'unset-value', > 'initial-value', etc. Given that we are constrained, if we cannot find anything better, I prefer naming inconsistency (default-value) over naming inaccuracy (au-default). - Florian
Received on Saturday, 20 June 2015 14:37:24 UTC