Forum Moderators: open
try and find out the stats on who still uses what, set your prefs in dw and then like that you will be able to anticipate any problems and make adjustments
i think accomodating for mac is more important than say NS4 ...
i think accomodating for mac is more important than say NS4 ...
A statement I've made several times around here. If you've never considered Mac support, you will most likely feel quite embarrased when you see your website on a mac.
One saving grace, most Mac users I know maintain 3 or 4 browser just out of self defense against the PC-heavy web. They are usually a browser-savvy bunch compared to the average PC user.
I had a client with the same problem - i made them install the bug fix and at the same time made a favorites icon.
This certainly would be very interesting if it were to do with differences in IIS versions between the dev and production server. Although, I'm more inclined to think it a coding compatability issue.
Have you seen instances of support issues on browsers between IIS versions?
Can't say that I have although I know of one IIS flag that defaults to on in IIS 5.1 and off in IIS 6. It would be natural to assume that there are probably others.
FWIW, Netscape 7.1 and Safari 1.2 render the pages correctly. IE 5.1 under OS9 and IE 5.2 under OSX both exhibit the same problem.
I just did a page that validates to XHTML 1.0 Strict, looks fine in IE6, Firefox, Opera 7 and... quite askew in Safari. I haven't been able to see it in IE for Mac so it doesn't exactly adress you question.
Depending on your audience, it can be very important to support Mac.
If you're dealing with academia at all, expect a lot of Macs. I don't mean schools, I mean hard-core science labs. I know of research labs with 20 Macs, three PCs and a *nix server or two.
Tom