3 ms·

It's nice, but using tables for layout is so 1990s. How about making it nicer by moving to CSS for layout. If you need help, just ask here on HN. Good luck.

Shamiq 17y ago
Hehe...ever looked at the HN HTML?
kd5bjo 17y ago
If you actually look at what I use tables for, it's: 1) Laying out the calendar (programmatically generated) 2) Having an element with a working 'vertical-align' CSS property 3) The layout of the form on the initial page. Everything else is done with CSS. Except for 3, which was because I was running out of time, I don't see how getting rid of the <table> tags helps things. I hope you don't want me to encode the positions of all the calendar dates in the CSS file.
- bluesmoon 17y ago
  na, a calendar should be a table.
jeromec 17y ago
Just so you know, Google, one of the most successful sites on the Internet, uses layout tables, and so does HN for that matter. I also use tables, and I've visited popular, funded, and cutting edge TechCrunch50 websites with over 100 errors in their markup while my code passes xhtml strict with 0 errors.
jfarmer 17y ago
When evaluating product/business decisions I use what I call the live-or-die criteria. Will my company (or product, in this case) live or die by this decision? If not, move on to something more important. HTML tables vs. CSS is one of those decisions that really doesn't matter. No product has ever failed because they used HTML tables, so why worry about it? Use whichever helps you get the job done faster.
- jeromec 17y ago
  I agree. Ideally, pure CSS is certainly the way to go, but it's not yet supported well enough to be used exclusively IMHO in every situation. I get a kick out seeing "savvy" people demand "table-less" web development, but with no mention of cross-compatibility or w3c validity.
- bluesmoon 17y ago
  it matters from the accessibility point of view. too bad that so many people don't care.

Shamiq 17y ago

Hehe...ever looked at the HN HTML?

kd5bjo 17y ago

If you actually look at what I use tables for, it's: 1) Laying out the calendar (programmatically generated) 2) Having an element with a working 'vertical-align' CSS property 3) The layout of the form on the initial page. Everything else is done with CSS. Except for 3, which was because I was running out of time, I don't see how getting rid of the <table> tags helps things. I hope you don't want me to encode the positions of all the calendar dates in the CSS file.

bluesmoon 17y ago
na, a calendar should be a table.

jeromec 17y ago

Just so you know, Google, one of the most successful sites on the Internet, uses layout tables, and so does HN for that matter. I also use tables, and I've visited popular, funded, and cutting edge TechCrunch50 websites with over 100 errors in their markup while my code passes xhtml strict with 0 errors.

jfarmer 17y ago

When evaluating product/business decisions I use what I call the live-or-die criteria. Will my company (or product, in this case) live or die by this decision? If not, move on to something more important. HTML tables vs. CSS is one of those decisions that really doesn't matter. No product has ever failed because they used HTML tables, so why worry about it? Use whichever helps you get the job done faster.

jeromec 17y ago
I agree. Ideally, pure CSS is certainly the way to go, but it's not yet supported well enough to be used exclusively IMHO in every situation. I get a kick out seeing "savvy" people demand "table-less" web development, but with no mention of cross-compatibility or w3c validity.
bluesmoon 17y ago
it matters from the accessibility point of view. too bad that so many people don't care.