W3C home > Mailing lists > Public > www-style@w3.org > April 2007

RE: [css3-multicol] should 'column-count' accept negative values?

From: Paul Nelson (ATC) <paulnel@winse.microsoft.com>
Date: Sun, 15 Apr 2007 16:13:39 -0700
Message-ID: <49C257E2C13F584790B2E302E021B6F9130E4662@winse-msg-01.segroup.winse.corp.microsoft.com>
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.


-----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


Perhaps we should. For other properties, we say (in prose) that
"negative values are not allowed":


Do you propose to address this the same way? That is, by adding prose?

              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Sunday, 15 April 2007 23:12:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:50 GMT