- From: L. David Baron <dbaron@dbaron.org>
- Date: Thu, 9 Jun 2011 14:39:51 -0700
- To: Alex Mogilevsky <alexmog@microsoft.com>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Daniel Holbert <dholbert@mozilla.com>, "www-style@w3.org" <www-style@w3.org>
On Thursday 2011-06-09 21:14 +0000, Alex Mogilevsky wrote: > Is there a precedent for value types like that in other places? > > For example, in CSS2.1 percent is not applicable to border-width. > Is setting a percent value making the property invalid or is it > setting initial value? It's invalid, but that's not really the example we want, since that's a value that just isn't allowed for the property. This is a case of a value that is allowed for the property but doesn't make sense on some elements. In the past I think we've been inconsistent about computed values in those cases, but at least we do specify in each case. Though, actually, in 2.1 I think we've mostly moved towards making the computed values be "as specified" and changing at the handling or used value level, so perhaps we're better off going in the other direction and saying the computed value is still the flex() function, but it just results in the same result as if 'auto' were the computed value. (I can't find an example of computed value mutation of this type in 2.1, though I didn't search exhaustively.) -David -- L. David Baron http://dbaron.org/ Mozilla Corporation http://www.mozilla.com/
Received on Thursday, 9 June 2011 21:40:30 UTC