safari and tables

[mnkeybsness]

quote from david hyatt's weblog

The next release of Safari will be fully embracing Web standards by dropping all support for tables. From now on, any pages that use tables will cause Safari to play a very loud raspberry sound and refuse to display the page.




Auto width tables will actually cause Safari to crash, accompanied by a loud explosion. Safari will then search your hard drive for all files that contain the word "table" and it will replace them with Egyptian hieroglyphics.




For all sites that attempt to nest tables more than four levels deep, Safari will play a loud flushing sound, and it will remove itself from the dock and erase itself from your system in order to protect itself from your bad taste.




I had the opportunity to announce my plans to drop table support to the WASP (We Annoy Safari Programmers), and they applauded the move. "It's high time someone took a stand and stopped supporting these unpredictable monstrosities," said John Feldman, one of the most outspoken members of the WASP. "Who really knows how to build a site using tables anyway?"




Unfortunately word also leaked to the TAG (Table Advocacy Group), and they were outraged. Jim Lerners-Lee had this to say. "I hate all this newfangled crap. XHTML2, XFORMS, CSS3. It's all so complicated. Me, I like tables. Good old-fashioned tables. Especially when used with the blink tag. Safari is obviously taking a dangerous stance by dropping support for tables, since everyone knows they are the backbone of the modern Web."




Despite protests from some individuals, we're not backing down. You'd better get those pages converted. You have been warned.

this IS and april fools joke

 

[FattyMembrane]

pardon my ignorance, but after reading the comments on that article, i was surprised to find that tables will be replaced by a new standard and was wondering what the "new" method is. i'm glad i found this out before i did any serious work on learning xhtml. to be honest, i use tables now (and they seem to be xhtml 1.0 compliant) but i would like to be as compliant with the new specs as possible. was this an april fools joke too, or is there some new kind of "xtable 1.0" that i should be using?

 

[kishba]

umm... have you ever heard of CSS??

he was implying that safari would be the first browser to be completely cutting-edge and drop tables like a bag of bricks. css can *supposedly* replace tables, but in my opinion css is not nearly as flexible

i thought it was a funny joke.

 

[Rower_CPU]

CSS is plenty flexible, but it falls short of trying to accomplish certain things we expect of tables.

Once we get decent CSS1 support in current browsers, not to mention CSS2, we'll be able to use CSS to create some very nice layouts.

For now, I use simple tables (2x2 tops) for absolute guides and then position with CSS inside them.

 

[tjwett]

dropping tables is silly. CSS is much faster yes but i ALWAYS create a 1x1 table to keep everything sized correctly. one thing i noticed is that Safari does not support borders very well, especially in an iframe.

 

[edesignuk]

Re: safari and tables

Originally posted by mnkeybsness
this IS and april fools joke

Fellas! It's a joke!

 

[FattyMembrane]

CSS is the replacement? i use css out the wazoo, but it's a little too quirky to replace my tables and a lot harder to code for various screen sizes. maybe i'm just stupid (don't answer that ) and should learn more about it.

p.s. i found a cool trick to show your friends the inferiority of IE (i know, there are a lot). have an anchor send content to an iframe in the same page. depending on the version, it will vomit the content into a new window, or do nothing.