The Anti-hero of CSS Layout – “display:table”

Re:The Anti-hero of CSS Layout – “display:table” by pcwalton on Monday October 27, 2014 @11:00AM (#8515835)

As someone who just implemented automatic table layout and is now intimately familiar with the details of how it works, I'd like to suggest that the problem with table-based layout is that it's excessively complex and largely undocumented and unspecified. The results will differ between browsers. Even the parts that have draft specs (which don't include, for example, percentage heights) are much more complex than CSS blocks and inlines: look at sections 4.1 through 4.4 of [1] for example.

[1]: http://dbaron.org/css/intrinsic/

[ Parent | on HN ]

Re:The Anti-hero of CSS Layout – “display:table” by mariusc23 on Monday October 27, 2014 @11:45AM (#8516179)

Yes! I remember running into a really obscure bug that was caused by having an element nested into a parent with display: table. I don't remember the details, but I remember we were using the sticky footer technique described in the article.

[ Parent | on HN ]

Re:The Anti-hero of CSS Layout – “display:table” by macNchz on Monday October 27, 2014 @03:46PM (#8517738)

I ran into a similar situation a while back while building an internal dashboard that had a fairly complex nested-table layout. It wouldn't render properly because of a bug in Firefox that had been open since 2000. I think this was the one (it seems they've fixed it): https://bugzilla.mozilla.org/show_bug.cgi?id=63895

[ Parent | on HN ]