Table vs Div vs Layer - design layout

Hi,

Designing pages/sites.

I currently use Divs to layout, which Nutscrape doesn't like... at all (floating problems I think it was). Tables gave a better layout initially, but restricted the scrolling in ie (as in the table cell always expanded even when I styled it in css). Nutscrape gave up and either didn't display the page at all or lost the colours/styles but got the text up in some vague way.

Anyway, I'd like some views from professional and amateur web page/site developers as to what they find is the best way to lay out the page. Has to use CSS, for styling.


Vince

I've only recently begun using CSS to develop my sites, so up to this point I've used tables. So from a development time and ease aspect, I'd say tables are good.... and from what I'm seeing CSS can be tricky for layouts when you're trying to make every browser happy. If IE would just do everything it is supposed to, we could all get along better.

IE has also made me a bad web designer. I used to have the idea that "Netscape sucks because it won't display my code correctly"... however I've come to learn that IE just lets you get away with so much more crap. So while I make sure everything works in IE because people are sheep, I always code it to work in Opera/Firefox first since they follow the standards. This has led me to CSS layouts, even tho I chose tables above.

Been using <TABLE>s all through, without a problem. With CSS styles, that's obvious.

I use tables/css combination because I feel I have a better control over what I'm displaying.

All projects I've done were with <TABLE>s and <CHAIR>s. :)

But then, its your own personal preference. Some people aren't comfy with them, so they prefer DIVs or LAYERs.

*Cue CornedBee with a post on how TABLEs are no good and how DIVs are better...* :p

Right on cue then ;)
I'm only doing pure CSS, and it's very simple for me as I don't give a damn about IE on most what I'm doing.

If you want it to work in IE you have to try a little harder, but it's still possible.

I can also recommend hybrid layouts: a single table to roughly divide into areas, then CSS inside.

Quote:

---

Originally posted by CornedBee

I can also recommend hybrid layouts: a single table to roughly divide into areas, then CSS inside.

---

Yeah, that's definately the best solution I've found so far ...