CSS and IE

[janetb99]

As a newbie to CSS, I'm trying to set up a page, experimenting with replacing tables. I have a test page at:

http://www.mtn.ncahec.org/web/test.asp

Can anybody give me a fix and brief explanation on why it works fine in FireFox and not IE? Something to do with floats in the parent divs inheriting?

(Also, if you see anything else that looks kludgy, I'm open to suggestions.)

Thanks
Janet

 

[Vragabond]

You have constructed divs and gave them properties to display as table? Let me give you a suggestion. Use <table>. I gather IE has trouble rendering divs when they're forced to behave as tables -- since IE has problems supporting more elaborate CSS. Anyway, why do you have <div>s that act like a table and not have a table? Table is not a forbidden element in CSS layouts.

 

[janetb99]

Vragabond,
Well, thanks, I guess. But that wasn't my question? I'm investigating, remember?

There are some who feel that tables cause delays in page loading because the page has to be completely parsed twice before display. If you have a large dataset, have limited resources for buying mega-servers, this might be a bit of a concern. I'm investigating the concept of how a pure css page would respond.

Might not work out, but I'm trying to understand.
Janet

 

[Vragabond]

First of all, you said you're a newbie in CSS and experimenting in replacing tables. That usually means that you shifted from a designing layout with tables to designing layout with CSS. I apologize for jumping to conclusion and accept now that you're trying to use divs as tables.

That aside, you're not doing anything. If you say you don't like long sleeved shirt and that is why you will buy a short sleeved shirt and some fabric which you will sew to the short sleeved shirt to make long sleeves you end up with long sleeves (and everything you hated about them) just with much more work. In your case, what is on your page is a table. It doesn't really make a difference if tags are called <div> or <table> <tr> and <td> or <thingamajig> for that matter. As long as behaviour of a table is loaded onto them, they are tables. So, you end up with all bad stuff you heard about the tables, you just make the browsers redo them from scratch rather than relying on what browser knows what table is.

Even more aside, I gave you the most probable answer why IE burps at your efforts. Most likely the support for it is too shaky.