News for hackers. Stuff that matters.
Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS... by nikatwork on Friday October 16, 2015 @08:41PM (#10402891)
> display:table

The delicious irony is that CSS had to emulate the old table model to overcome its default layout deficiencies. And IIRC it still can't natively handle mixing relative and fixed widths, and consistent vertical centering.

> html tables never displayed identically

My bread and butter used to be slicing photoshop comps into websites. My table layouts were pixel perfect on every browser without hacks. I do agree there were a few things that had to be accomodated using   and spacer gifs - but it was painless compared to elaborate and fragile CSS hacks.

I shouldn't still care about this stuff - I moved to IOS dev thank goodness - but I still nuture a burning hatred of CSS years later :)

Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS... by olavk on Sunday October 18, 2015 @02:44PM (#10409229)
There is no irony. CSS replicate the table layout model in order allow you to separate markup from presentation but still be able to show tables. Otherwise, how should the default style sheet for table-elements look? CSS obviously needed to to have at least the same presentational power as presentational HTML to be backwards compatible.