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

RE: [css3-multicol] pseudo-algorithm

From: Stephen Zilles <szilles@adobe.com>
Date: Tue, 8 Feb 2011 11:26:10 -0800
To: Håkon Wium Lie <howcome@opera.com>, Sylvain Galineau <sylvaing@microsoft.com>
CC: Alex Mogilevsky <alexmog@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <CE2F61DA5FA23945A4EA99A212B1579537CDA58235@nambx03.corp.adobe.com>
Keeping the algorithm simple at the cost of having really bad presentations hardly seems like the right trade-off. Most CSS fallbacks have focused on doing something reasonable with unreasonable inputs, such as column-count: 999999.

Steve Zilles


> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf
> Of Håkon Wium Lie
> Sent: Tuesday, February 08, 2011 11:18 AM
> To: Sylvain Galineau
> Cc: Alex Mogilevsky; www-style@w3.org
> Subject: RE: [css3-multicol] pseudo-algorithm
> 
> Also sprach Sylvain Galineau:
> 
>  > I was wondering about that. Taking another look
>  > at this branch of the algorithm it certainly seems
>  > to be designed to preserve the specified column-gap,
> 
> The whole algorithm is -- and has always been -- partial to
> 'column-gap'; it may give new values to 'column-width' and
> 'column-count', but not to 'column-gap'. This is good, I believe. It
> keeps the algorighm (relatively) simple, and column gaps will
> typically be narrow so there isn't much space to gain by reducing
> their width.
> 
> -h&kon
>               Håkon Wium Lie                          CTO °þe®ª
> howcome@opera.com                  http://people.opera.com/howcome
Received on Tuesday, 8 February 2011 19:26:56 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:37 GMT