Re: [css3-multicol] new editor's draft

Also sprach Shelby Moore:

 > >  > >   http://lists.w3.org/Archives/Public/www-style/2010Aug/0492.html

 > >  > http://lists.w3.org/Archives/Public/www-style/2010Aug/att-0492/image001.png

 > >  > Is that an arbitrary choice you have made to violate the designer's
 > >  > directive? For what benefit do you put this tsuris on the designer?
 > >
 > > The decision was made by the Working Group and my role, as editor, is
 > > to implement the WG's decision. I'm not sure the WG wants to reopen
 > > the issue. If you feel strongly about it, you may want to start by
 > > convincing Alex.
 > 
 > I will leave it to Alex's discretion. Alex perhaps if have time you might
 > ponder my point and see if it sways you, which is I think we should
 > minimize text that would be hidden, and respecting the designer's decision
 > otherwise. Please see my prior post for details. I am probably not aware
 > of some factor that caused you to choose a different tradeoff.

Maybe I can help you. At least, I think I have a use case for
'column-span: all' when it appears in an overflow column.

Say, you'd like this three-column design with a copyright text at the
bottom:

    Menu    | main article | another
    item 1  | text and so  | box with 
    item 2  | forth just   | some 
    item 3  | some words   | content 
            | you know     | over here

     Copyright © 1900-2000000000000

Your markup could be:

  <div class=menu>..</div>
  <div class=article>..</div>
  <div class=box>..</div>
  <p class=copyright>...</p>

You could achieve the above with this style sheet:

  body { columns: 3 }
  div { break-after: column }
  p.copyright { column-span: all }

However, since the p.copyright element will end up in an overflow
column the 'column-span' property will -- as per the current CR --
not have any effect.

(Now, you could argue that the use case isn't terribly interesting as
there is no way to set different widths on the columns. But that may
be added in the future.)

Hmm. I belive Alex' concern is that a stray element far out into the
overflow area shouldn't re-enter the multicol box and cause the layout
to be reflowed.

However, if we specify that 'column-span: all' in an overflow area
just takes the element back in, underneath the content that has
already been laid out, and stretches across the columns inside the
multicol box, it seems doable. No?

Cheers,

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome

Received on Sunday, 24 October 2010 18:40:46 UTC