On Sep 16, 2010, at 1:38 PM, Thierry Koblentz wrote: >>> I think there'd have to be a third element in there to set as >> display: table-row. >>> >>> ---Tim >> >> >> Not quite true. If display: table-row is not given then, an anonymous >> table-row is generated [1]. >> >> >> | If the parent P of a 'table-cell' box T is not a 'table-row', >> | a box corresponding to a 'table-row' will be generated between P >> | and T. This box will span all consecutive 'table-cell' sibling >> | boxes of T. > > I'd agree with Tim, it is better to have an element to create an explicit > row as the implicit row is not enough to prevent some browsers from dropping > the last item (cell). > I ran into this issue before. If you check the archives you should find a > few posts where I discuss this with Ingo (or was it Philippe?).
(older) Gecko (1.9.1 and older) are especially affected by that 'drop'. I _think_ I've seen something similar happening with IE 8, if my memory isn't failing completely. But yeah, explicitly setting an element to display:table-row usually solves it (and was the recommended method in some gecko bugzilla entry). The display: table element will then be automatically generated (if you don't set it). Philippe --- Philippe Wittenbergh http://l-c-n.com/ ______________________________________________________________________ css-discuss [cs...@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/
