Cary, your post is unsubstantiated. Ever heard of the z-index? Absolutely positioned divs should be avoided? Take a look at this code..



Place that code above or below any element in a page and position it absolutely using the left and top values on the inner div and get pixel perfect precision in any browser. Tested, tried and true for about 10 years now. If abs divs have their place, where? You didn't say. You also didn't say where not to use them.

In regards to different font sizes, you can set the font size for a web page in a style sheet that's consistent in all browsers released in the past 5-7 years. Look up Eric Meyer's CSS reset.

I'm not sure how VSD and font size have anything to do with web page development. You're probably speaking about your system font size.

I'm not picking a fight here but it's posts like this that get my blood going.


G'kar,

I'd consider CSS strongly simply because you will spend double the amount of time styling a table than you would a div container. Think of it this way... if you feel you have more control over a layout using tables, try layering a table over another without using CSS. Cut out the middle-man (table) and go straight to the supplier (CSS).

Be well.

Actually, the web is full of substantiating evidence. The article, Absolute Positioning Pitfalls, tries to answer some of the questions you've raised about when to use absolute positioning.

http://www.tyssendesign.com.au/articles … -pitfalls/



Yep.



..."whenever possible."



Entire books and css courses are spent answering these questions, which you seem to believe I or anyone else can condense into a single forum post. Just look at the code you posted above. You make it sound like it can simply be dropped in a page, and the content won't budge, which we both know isn't true, since the relatively positioned outer divs will move and flow with the rest of the page elements.



Note that his reset, and his page designs, allow him to better control relative font sizes, but the base font size is controlled by the visitor. So, if someone with poor eyesight uses a larger base font size in the browser, the page doesn't fall apart and display overlapping text content.



Basically, VSD, which is used for web page development, requires 96dpi displays because its fonts sizes are defined as "points" rather than "ems", and point sizes don't mean anything apart from dpi. When you change your display's dpi, text content either shrinks or overlaps other page elements.

Sweet, an E-Rumble. Let me jump in here:

Hey Dave Thompson, your tables suck and are only used by noobs!

Anybody else want some?

Jo Ann, just hush a minute.

Spinny, get a haircut.

Scott, grow some hair.

J/K

It's all Dr Longo's fault. He started it with "My website is better than yours".

Thanks for all your opinions everyone. I seemed to of started a bit of a heated debate, that wasn't my intention I just wanted to know what you all thought of the way forward.
CSS it is then. I'll concentrate my efforts that way and leave those tables behind

There are some tech dichotomies that take on the heat of a religious war. Mac vs PC, vi versus emacs, tastes great versus less filling, and now tables versus CSS.

Now that's hyperbole.

What? Was it the beer reference?

Spinny you forgot iPhone vs BlackBerry et al, and then there is this: http://meiert.com/en/blog/20080419/rese … s-are-bad/

PS I like the graphics on your site, Spinny.
Makes me seriously think of dumping tables sooner than I intend.

Hey Tom no fighting please - but if you insist on a physical rumble, can I come and watch?