url for which browsers support what in css?

[joolsm]

I've lost the url for the website which had charts showing how the various browsers rendered or supported the various css elements/tags.

Please can someone refresh my braincell?

Thanks, Jools

[DanA]

Maybe this one?
[webdevout.net...]
or this one
[corecss.unk.edu...]

[joolsm]

DanA - thanks very much - exactly what I was looking for.

Now to have a good study and try & find out why my websites are breaking in Firefox!

[Wlauzon]

Probably only 3, maybe 4 browsers worth worrying about though. FF, IE6+, and Opera probably have 98% of the market.

[DrDoc]

Sorry to tell you, though, but those charts are incorrect. For example, there are several CSS properties listed as fully supported by IE 6, but which are in reality buggy at best.

[Robin_reala]

Well edit them DrDoc - click on a property and it'll put you into editing mode where you can submit your update.

[DrDoc]

Only one of them ... which happens to be the most correct one :)

[doodlebee]

>>try & find out why my websites are breaking in Firefox! <<

Probably because you're coding for IE, and then checking in Firefox. You've got it backwards.

You should *always* code for Firefox first. It'll save you a ton of headaches.

[Robin_reala]

Actually, no. You should always code to standards first, then bug fix in every browser. I realise that coding to standards is hard, but coding by implementations is what got us into this mess in the first place. Firefox is a lot better than IE (I've used it for 3-4 years now as my only browser) but it's still got rendering bugs that could lock out other browsers like Opera or Safari if you thought they were the right way to do things. Not to mention causing yourself more trouble when they are finally fixed in Fx.

[doodlebee]

>>Firefox is a lot better than IE (I've used it for 3-4 years now as my only browser) but it's still got rendering bugs that could lock out other browsers like Opera or Safari if you thought they were the right way to do things.<<

Okay, maybe I didn't put that in proper English, then.

What I meant was, you should code for Firefox *before* you code for IE. The biggest mistake I see developers make is coding for IE before coding for other browsers.

My point was to code for standards. I've been doing web design for years, and have discovered that coding for Mozilla first will generally rule out the issues you have in other browsers. Usually, when I code for Mozilla, the *only* browser I have to "fix" is IE. All others render the sutes to standards compliance.

But if you prefer to code for Opera, fine. Just don't code for IE first.