On May 28, 2011, at 6:50 PM, Joergen W. Lang wrote: > I re-checked with the spec [1]. There it says: > > Name: column-width > Initial: auto > Percentages: N/A > > No percentage in sight. Instead the value is reset to 'auto'. So apparently > we're stuck with inconsistent behaviour if we're trying to set an explicit > column-width. Schade!
Yeah, I was going to send a follow up on that. I obviously should have double checked the spec :-(. Anyway, as far as the column-width is concerned, the situation is improving, given that the most recent rendering engine versions are all consistent for _that_ [*]. And specifying a column-width is clearly a hint, as the width is adjusted to the width of the container. [*] there are other inconsistencies between rendering engines that are more annoying, such as what happens to the top margin of the first child of a multi-column element (and bottom margin for its las child) – it shouldn't collapse through with the top/bottom margin of the multi-col element according to the spec. And issues with floated blocks, absolute positioning, and so more. Philippe -- Philippe Wittenbergh http://l-c-n.com/ ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
