[icedchai]

The problem is it was easy to center things with tables. Then once CSS was popular, that was the "wrong way" to handle layout. I find CSS the worst part of web development, and it's what turned me off of front-end work. Glad flexbox has finally made things simpler again.

[autoexec]

I like CSS but I'd agree that tables got a bad rap. They were very easy, very effective, and only occasionally turned into a nightmare of nesting that was impossible to maintain

My problem with CSS now is that it's gotten too bloated to the point where it's introducing privacy and security risks. I really want an add-on that restricts CSS by default to only a sane subset of features.

[yreg]

Using tables for layouts is an accessibility nightmare.

[progmetaldev]

They're also awful to maintain over time, if you're needing to add new elements and require new columns or cells (and then there's the need to nest tables when using them for layout).

I attempted to fix a website by adding closing table cells that were missing, and finally got the page to validate as XHTML Strict and Transitional. The entire layout shifted, and was completely based on those missing end tags.

[ryathal]

it's really not. It requires adding a single attribute to tables that exist for layout.

[yreg]

What attribute? And how do you affect the reading order? Say on a page with a side navigation?

[ryathal]

https://developer.mozilla.org/en-US/docs/Web/Accessibility/A...

[yreg]

How does that solve anything? Your dom order is still tied to your presentation.

[assimpleaspossi]

Google for "The Web is Ruined and I Ruined It" written by the guy who first came up with the idea to use tables for layout.

[icedchai]

There weren't really many other options in the 90's.

[assimpleaspossi]

Not the point. The point was that some people still think there is nothing wrong with using tables for layout. The guy who started it all would like to have a word with them.