Forum Moderators: not2easy
Let's also try to stay clear of our reasons; they've been discussed enough already that I think it's safe to say we'll all automatically understand the reasons behind the votes!
So, short and sweet, what do people use, and when? Remember, no reasons, just simple statements of what method we use! :)
I'll lead off:
As of very recently, I use CSS Positioning as much as possible, but still haven't totally eliminated the use of tables.
I have tried to make some new sites with Div Basic Page Layout and for most things it works in most browsers most of the time, but I found table structures to be more cross browser compatible and much less time wasted troubleshooting and applying css fixes.
As said above look at Google(login page for adwords), nested tables within nested tables.
"CSS is just a new way to present bad stuff faster" said BaseVinyl. That is a statement I can't argue with. However, CSS is also a new way to present good stuff faster if you have it.
I find myself cracking up when I try to get CSS to work in early browsers. (and IE5.5!)
Thing is, I can Ski, and every time I go to learn to snowboard I end up with ski's on again. It fun and quick and I can do it pretty well, but I REALLY do want to learn to board!
Time spent learning is the biggest factor for me. Jobs are to varied at the mo' to concentrate on just CSS.
Then what do you do with:
a) the massive growth occuring in smartphones. Those such as Pocket IE (ipaq), Symbian (Europe) Opera are not necc compat with css2 positioning.
Are you just abandoning that percentage of users?
Lastly, would those of you that are dumping those users, allow me to run a script off your site to take that traffic elsewhere?
Lastly, would those of you that are dumping those users, allow me to run a script off your site to take that traffic elsewhere?
Brett sideswipes the thread with a jolt of realization, what about those users?
Are there some tools to simulate what the smartphones, pda's, Ipaq would see?
<edit>speeling</edit>
But since we've opened this box, I would like to add that the benefits of CSS-P may very well result in more visitors being attracted than are lost.
Are there some tools to simulate what the smartphones, pda's, Ipaq would see?
Yes, Opera 7 has an emulator for its small screen display mode, shift F11. But Opera's small screen rendering technology is quite different than for example's MS IE handheld version, which I believe actually tries to sort of render the whole page.
However, if you use Opera to view your page you will immediately find a few things:
If you are relying on absolute positioning to place items in the display, but that placement is actually not in accord with the linear flow of the html, you will have big problems. Right float should really be used with great caution because of this problem as well. Opera removes most, but not all, javascript, and css and replaces it with default css from what I can tell.
Using Lynx to view your pages is useful to check the logic of your data, but will not show you anything you can't see from just looking at your html. One thing either of these tools will show you that questions of accessibility and simple table layouts are myths.
CSS positioning is fun, but I use tables on money sites.
With a table you get pretty reliable rendering of your site for 99.75 to 99.9% of the site visitors. When you are creating the html for a megasite, you can't afford to have the page break for 1-2% of the site's visitors, that's thousands of people a day. It's this reason that google for example keeps its page in a table, not because they somehow can't change it but would if they could.
When I'm eating, I use a table since I can't figure out how to use CSS to position my plate. However, when it comes to Web pages, CSS all the way!Heh heh
the massive growth occuring in smartphones. Those such as Pocket IE (ipaq), Symbian (Europe) Opera are not necc compat with css2 positioning.Perfect! They don't see the fancy layout, and since I've carefully arranged the source of my page to render coherently without a stylesheet, they get a page optimized for linear reading. Frankly, I don't want to scroll around three columns on a tiny screen.
Oh yeah, the poll. CSS for everything it's designed for. Tables for tabular data. Simple, sweet... and it looks good too ;)
If you think there is only one answer, then you're wrong! I'm generally a CSS fan, but above all I use the right tools for the job.
Tables are used for tabular data, such as lists, that are to complicated to do with CSS.
CSS all the way, but it still has it's limits.
Tabular data means something like product id, product name, product price, etc. And you shouldn't try to use CSS for this beacuse CSS is about presentation, whereas "tabular data" refers to content.
CSS is limited in what it can do with content in HTML tables, so you should avoid putting data into these (even if it's logically correct) unless you actually want to present the content in a tabular format.
Reasons:
1. The web was originally meant to use stylesheets in conjunction with html (used for stucture) from the start.
2. Clients are more interested in being part of the future, not the past.
3. I will not cut off mobile phone, pda and disabled users.
4. Who wants to:
A. Generate a lot of crappy code and slow everything down
B. Make life difficult for mobile phone users.
C. Make things exceptionally difficult for those with disabilites.
I just prefer to do what the web was originally meant to do, it's not Tim's fault that stylesheets got put back a few years.
My final answer is: CSS-P
"CSS-P all the way, and I'm even getting it to work in Netscape4 - not as pretty but very functional!"
You just need to use the little comments trick to make Netscape 4.x exclude certain parts from any stylesheet.
....I think we're getting sidetracked away from the "poll"....- MatthewHSE
This "poll" is like shooting fish in a barrel. Did you expect different results, (responses running about 15:1 in favor of CSS)... THIS IS A CSS FORUM. You'll get less biased results in a more general forum.
My vote: I'll stick with tables for positioning and layout purposes until CSS matures or something better comes along.