- From: Paul Nelson (ATC) <paulnel@winse.microsoft.com>
- Date: Sun, 15 Apr 2007 16:13:39 -0700
- To: Håkon Wium Lie <howcome@opera.com>, "L. David Baron" <dbaron@dbaron.org>
- CC: <www-style@w3.org>
We should really make this not only say this cannot be negative. We should explicitly state that value must be 1 or greater.
Paul
-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Håkon Wium Lie
Sent: Monday, April 16, 2007 6:58 AM
To: L. David Baron
Cc: www-style@w3.org
Subject: Re: [css3-multicol] should 'column-count' accept negative values?
Also sprach L. David Baron:
 > The current definition of 'column-count' [1] describes a property
 > that accepts any <integer> values.  Since negative values (and
 > zero?) aren't meaningful, I think the property should be revised so
 > that they are syntax errors that cause the declaration to be
 > dropped.
I agree that negative valued don't make sense. The same can be said
for widows and orphans, but we don't disallow negative values for
those:
  http://www.w3.org/TR/2006/WD-CSS21-20061106/page.html#propdef-orphans
Perhaps we should. For other properties, we say (in prose) that
"negative values are not allowed":
  http://www.w3.org/TR/2006/WD-CSS21-20061106/visudet.html#propdef-line-height
Do you propose to address this the same way? That is, by adding prose?
-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Sunday, 15 April 2007 23:12:59 UTC