Your code starts with this:


It throws IE into quirks mode which is not good. Delete that line and make sure the doctype is the very first line of code, no blank lines above it.

IE 6 is still about 20% of potential visitors/customers who would then look elsewhere.
http://www.netmarketshare.com/browser-m … px?qprid=2

Depends which report you read and where your visitors come from, anything from 4%-20% and its going to drop pretty rapidly from here in.

I think Scott mentioned elsewhere that Google won't be supporting IE from July this year so that will really push the cart for code compliant browsers and if you don't have a code compliant browser you may increasingly find it difficult to view websites.

There needs to be a point where you draw the line in the sand and Google's move might just be it...lets hope so anyway.

That aside you need to look at what your market is and weigh up whether your customers are likely to still have IE6 or not versus the bother of coding for an archaic system. If your customers are likely to be up with the more modern technology then I'd say it was worth the risk not to code for that browser, but if they are from a demographic that would be sticking with older browsers then you may feel its worth the effort.

It depends. If you're coding you're own sites, fine. But if you are coding for paying customers, it just doesn't take any real additional effort to make pages work in IE 6. Basically, you make your pages for other browsers, and just make sure they are usable in IE 6, even if not as nice looking.

Now, web applications and specialized services such as those of Google are another matter.

You will find lower percentages of IE 6 users on web development sites such as w3schools, but it's visitors aren't typical of the rest of the world.

Yep very true Cary...if you are coding for a paying customer you need to do the best job

Just out of interest I just had a look at the stats on 7 of my own sites covering a wide range of themes and the IE6 usage was between 3.7 and 10.6%.

If you have access to stats on your sites its worth having a look at them over several months and see what the trend is for your own site or the site you are working with.

But as mentioned, better to code for all for now.

This is the sort of topic we could discuss ad infinitum Heck just read my disclaimer below

I wonder if the OP has gone to sleep yet?...

My line in the sand is I refuse to avoid using transparent PNGs in my designs. The site is certainly still usable for IE6-ers but they're just going to have to live with downgraded appearance.

Here here! I resemble that remark! LOL I too feel that way, as much as I'd love to make my site as nice and easy for everyone, it's hard enough for me to get it right for one system without having to code for super old ones lol. Upgrade I say!

hmmmmm?

My css menu works fine in the preview but not when i upload. I only get an unordered list. Im sure i am doing something fundamentally wrong.http://www.ultrasoundpaedia.com/USP%20obstetric%20tool%20arnold%20chiari%20winner.html
I have tried putting the menu (obstettoolpathologymenu.mnu) in both the css folder and just directly in the public folder.
Id be grateful for any assistance,
Thanks,
Brian

Hiya Brian, did you upload "all" the files for it? There are a few files including the css file that it needs for the styling and arrangement. Sounds like there's some things missing.

Looks like the menu-menu.css file isn't uploaded or isn't in the right place. According to your code it should be in the css folder. Find that file and upload it to there or move it to there if it's already uploaded and you should be all set.

css/menu-menu.css

Also you NEED to remove the spaces in your file names, that's an extreme No No to website design. If you need to separate words in your site pages and file names, use underscores _ or dashes - which are both acceptable ways to separate words.