- From: Shelby Moore <shelby@coolpage.com>
- Date: Mon, 25 Oct 2010 03:15:28 -0400
- To: shelby@coolpage.com
- Cc: "Håkon Wium Lie" <howcome@opera.com>, "Alex Mogilevsky" <alexmog@microsoft.com>, www-style@w3.org
Shelby Moore wrote: >> [snip] >> >>> Håkon Wium Lie wrote >>>> 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? >>> >>> Why should go underneath? Rather we must do what the designer >>> specificed, >>> and it should span all the three columns at the top. >>> >>> Copyright © 1900-2000000000000 >>> 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 >> >> It spans at the top because the Copyright © 1900-2000000000000 was >> pushed >> to the top of the next column box in inline direction. It can't be at >> the >> bottom because there were column breaks that terminated those prior 3 >> column boxes. I am arguing that we remain consistent. The column span >> block direction position is based on the position of the spanning >> element. > > Thus we may need a "do not span me" setting. And we may need a column-span:all-not-before? Tangentially, the current spec does not seem to support spanning only 2 columns, such as when wanting to float an image or quotation straddling 2 columns and have the inline content flow around it (float:right on the left colum and float:left on the right column).
Received on Monday, 25 October 2010 07:15:56 UTC