- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Mon, 01 Jul 2013 12:52:06 -0700
- To: "www-style@w3.org" <www-style@w3.org>
So, while creating examples for the 'default' keyword,
Tab and I realized two things:
1. There is no good use case for this. There are some problems
it halfway solves (like undoing display: none), but will be
better solved by other mechanisms we have in the pipeline.
2. Default is a terrible name for "initial-or-inherit". Consider:
html { font: 16px Authors Favorite Font; }
article.main { font: default; /* use user's default */ }
You'd think that would work, right? But it doesn't work,
because 'default' in this case resolves to 'inherit'.
So the proposal is twofold:
A. Drop 'default'.
B. Introduce initial-or-inherit as both keywords, thus:
<common-keywords> = initial || inherit
B could be bikeshedded a bit more, but this a) uses only reserved
keywords and b) isn't as confusing as 'default'.
~fantasai and TJ
Received on Monday, 1 July 2013 19:52:36 UTC