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/howcomeReceived on Monday, 1 June 2009 12:40:39 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:36 UTC