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

RE: [css3-multicol] pseudo-algorithm

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Mon, 14 Feb 2011 22:55:00 +0000
To: Håkon Wium Lie <howcome@opera.com>
CC: Stephen Zilles <szilles@adobe.com>, Brad Kemper <brad.kemper@gmail.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <045A765940533D4CA4933A4A7E32597E2AB5E8AC@TK5EX14MBXC120.redmond.corp.microsoft.com>

[Håkon Wium Lie:]
> The primary use case is best handled by setting 'column-width' to a value
> other than auto. And then we will not get into this part of the code.

I know. But we're discussing what happens when one gets in this part of the
code :) I don't think it's that difficult, frankly.

>  > One that could be triggered by something as simple as the viewport  >
> being resized to half its size by the window manager. As specified,  > I
> think the current fallback pretty much forces the author to  > define a
> media query to handle the result.
> 
> Media queries is an option. But setting 'column-width' is easier.

We support column-width:auto. I don't think of 'auto' as being 'auto-ugly'...

>  > >This will not be the most common case, and we  > > shouldn't really
> encouage its use -- unless author really wants a specific  > > number of
> columns.
>  >
>  > Experience indicates that 'encouragements' have limited influence on
> what  > authors do in practice.
> 
> Sure. But if they chose to set column-count and column-gap to specific
> values, perhaps they mean it?

Perhaps they mean what ? That the result should look fine when the window
is maximized, that it should look awful when it is resized, or both ?
 
> In a few cases this will be what the designer wants.

Sure. That doesn't help in those cases where that is not what they want.
My assumption, of course, is that there are more of those.

> 3) could be expressed as:
> 
>     if (column-width = auto) then
>         N := column-count;
>         W := max(0, (available-width - ((N - 1) * column-gap))/N);
>     fi
> 
> So, 'column-width' would work as 'width', and 'column-gap' would work as
> 'padding'.
> 
> What's your preferred solution?

That's even worse; this means the content is effectively gone for the user.

Of the ones you have suggest, I prefer leaving the current algorithm alone as 
this is the least bad in terms of outcome.
Received on Monday, 14 February 2011 22:55:33 GMT

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