So it's been 9 months since I put in a proposal here [1]. Arron
responded on behalf of Microsoft with some quite valid criticism of the
wording details and some mistakes in the logic [2] and there was some
discussion about whether it's better to change how display computes for
kids of table-column and table-column-group elements or to discard the
relevant kids in spite of them having a computed display != none. Then
there was a decision made at some point to defer this to domain experts
or something, if I recall correctly, but I can't find the mail saying that.
I'm happy to make edits to address the issues Arron raised. I think it
makes more sense to leave the column behavior as-is instead of changing
display computation; at least in Gecko's case it's more efficient to
implement it that way than by changing the computed display value.
Other implementors should chime in on this, of course.
Past that, what needs to happen to make this move forward?
http://wiki.csswg.org/spec/css2.1#issue-109 and
http://wiki.csswg.org/spec/css2.1#issue-110 seem to be on my plate if I
read the notation correctly, and the above proposal was meant to address
those issues... but now it seems to be blocked on something, and I can't
tell what.
-Boris
[1] http://lists.w3.org/Archives/Public/www-style/2009May/0213.html
[2] http://lists.w3.org/Archives/Public/www-style/2009Jul/0099.html