[csswg-drafts] [css-multicol] Contradictions about whether zero is allowed for 'column-width'

rachelandrew has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-multicol] Contradictions about whether zero is allowed for 'column-width' ==
In May 2011 @dbaron raised [this issue](https://lists.w3.org/Archives/Public/www-style/2011May/0338.html) against multicol:

> [http://dev.w3.org/csswg/css3-multicol/#cw](http://dev.w3.org/csswg/css3-multicol/#cw) seems to give two different answers as to whether zero is a legal value for column-width:
>   _Computed value: the absolute length, zero or larger_
> and then:
>  _Specified values must be greater than 0._

> I feel quite strongly that zero should be allowed, because I'm strongly opposed to CSS having any value range restrictions that require an open range (i.e., one where the endpoints are not allowed).

> I think open ranges are a problem both because:

> (1) They seem likely to lead to interoperability problems if people want to try to get the "minimal value", since rounding may vary between implementations.

> (2) We have multiple features that require clamping values to the allowed range:
> (a) calc()
> (b) interpolation in transitions or animations, when the cubic-bezier() timing function has Y1 or Y2 values outside of the 0-1 range and clamping to an open range does not make sense.  Sensible clamping requires a closed range.

> So I think either '0' needs to be allowed or, if that makes the algorithm nonsensical, the range restriction needs to be changed to start at some other value.

As far as I can tell this wasn't addressed, opening here for further discussion.






Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1741 using your GitHub account

Received on Saturday, 19 August 2017 11:54:03 UTC