HN Hall of Fame Weekly email

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

colintoh.com Essays & writing Essays & articles Web & internet Candidate

Resurfaced independently across 5 calendar years, with breakout response in 2 of them.

submissions
6
submitters
2
observed span
2014–2025
peak thread · 67 comments
130 pts
latest 20+ return · 2017-02-11
93 pts

Submission timeline

2007–2026

One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.

First comments on top threads

HN comment order

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]…

It is fascinating how a perfectly sensible rule-of-thumb "you shouldn't use html tables for something which is not semantically a table" gradually morphed into various superstitions like "you shouldn't use html tables" or "you shouldn't use tables for layout" or even "you shouldn't use tables". I don't think people have a hard time understanding that you shouldn't use the <blockquote>-element for something which is not a quote. But html tables had a more troubled history because for a long time…

olavk·93-point thread·

The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.

Breakout years
2

100+ points or 50+ comments

Total points
228

reference only — not used in Hall rules or ranking

Total comments
124

reference only — not used in Hall rules or ranking

Every submission