W3C home > Mailing lists > Public > www-style@w3.org > February 2011

Re: [css3-multicol] pseudo-algorithm

From: Brad Kemper <brad.kemper@gmail.com>
Date: Wed, 16 Feb 2011 10:29:02 -0800
Cc: Håkon Wium Lie <howcome@opera.com>, Stephen Zilles <szilles@adobe.com>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <6B335B05-5717-4152-82F2-762BB2F18D48@gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>

On Feb 16, 2011, at 9:53 AM, Sylvain Galineau wrote:

> Whether it is a better solution or not depends on the requirements you
> set, and how you rank them. I don't think anyone is arguing that  
> column-width:auto should not mean 'adjust column widths'. What I am 
> definitely arguing - and Steve also, I think - is that column-width:auto
> cannot be assumed to mean the author cares so little about the content 
> that it can disappear entirely. 

There are plenty of times when I create a single column DIV in which the content is entirely hidden by overflow:hidden (and height:0). I am generally against the UA deciding what I _really_ want when I specify something rather exactly. If I do have a multicol element that can be sized downwards towards zero column widths, and if I do care about not letting it disappear entirely, and if I do want to prevent that by reducing the number of columns on narrow devices, then I can take care of that easily via media queries. Or, if I want to keep the column count but not let the columns get to narrow, then I can set a min-width on the multicol element. The point being, that is my choice.
Received on Wednesday, 16 February 2011 18:29:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:56 UTC