- From: Alex Mogilevsky <alexmog@microsoft.com>
- Date: Wed, 3 Jun 2009 02:59:30 -0700
- To: Håkon Wium Lie <howcome@opera.com>
- CC: "www-style@w3.org" <www-style@w3.org>
I think "column-span:all" is equivalent to a sequence of multicol elements:
h2 { columns:1}
bodytext { columns:3 }
With column-span, the behavior is equivalent to adding anonymous multicol elements before and after column-span, which is pretty much what an implementation would have to do. Anonymous anything is an implementation hassle though, so if it could be avoided it would make our life esier;)
-----Original Message-----
From: Håkon Wium Lie [mailto:howcome@opera.com]
Sent: Monday, June 01, 2009 2:40 PM
To: Alex Mogilevsky
Cc: www-style@w3.org
Subject: RE: [css3-multicol] column-span property
Also sprach Alex Mogilevsky:
> Column-span prevously allowed values other than '1' and 'all' but > it was scaled down because of added complexity of cases where span > has more columns than available.
Right. My intention, however, is to scale it back up again in level 4 or something.
> IMO the property in its current form is unnecessary. All use cases > I can think of are covered by either page floats in GCPM or nested > multicolumn elements.
How would you express the use case in the spec?:
h2 { column-span: all }
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Wednesday, 3 June 2009 10:00:11 UTC