|site falls to pieces in ie 5 mac|
I've just completed a beta version of a site for a uk based company. The code conforms to w3c html 4.01 standards and the css validates also, but I viewed the site on a mac (os 9.1, ie 5) this morning and it totally fell to pieces.
Anyone got any idea how to remedy this?
I did'nt get the oppotunity to view the site in any other mac browsers,
I'd be intrested to know what happens in
ie5.5 ie6 mozilla and safari.
[edited by: korkus2000 at 4:07 pm (utc) on Aug. 31, 2003]
[edit reason] No site reviews TOS #21 [/edit]
I'd delete that link very quickly if I were you. Personal links are not allowed in this forum, and I found out the hard way.
As for other Mac browsers... there is no IE 5.5 and IE 6.0 for MacOS. The latest version of MacIE is version 5.2, which is almost as standards compliant as Gecko and KHTML, but is hideously slow. I've never been able to test my site on a Mac, I just test it in WinIE 6.0, WinIE 5.0, WinIE 4.0, Netscape 7.1, Netscape 6.2, Netscape 6.0, Netscape 4.8, Netscape 4.0, Netscape 3.0, Opera 7.1, Opera 6.0, Opera 4.0 and Konqueror 3.1 and hope for the best.
Please can you be a bit more specific about "falls apart". You've done your layout with tables (rather than position:absolute), so I can't really imagine how it can fall appart, as your layout it actually quite basic. Is it just the case that it doesn't look quite so pretty in MacIE 5.0?
I apologize for posting the link, I was unaware of the rule.
Thanks for the reply hartlandcat,
not so much of "does'nt look so pretty" but more of becomes
unreadlable/unusable, tables get pushed out of synch with each other.
I'am unable to get access to a mac at the moment, so I can't go into a more detailed decription. But what a mean by the term "falls apart" is that users viewing the page on that platform would go elsewhere.
Its quite annoying that a site that validates to W3C standards in both html (version 4.1) and css. Is still able to become unusable in ie5 mac.
It is likely that other mac browsers (safari, mozilla) would
render the pages with such 'orrible' results?
Is the script, I could use to send ie mac viewers to an alternate page/s
Having just wrestled with some IE5/mac problems, I learned a few things:
1. IE5 on macintosh has much weaker error recovery than IE 5 on PC. However, you say the HTML validates, so that shouldn't be the issue.
2. Table layouts are lot more flexible than we tend to think. We put in a width declaration and assume that it will be rendered that width. But the W3C recommendations for user agents allow these attributes to be overruled at rendering time, because it's possible (even for validated HTML) to give impossible or mutually contradictory instructions. Maybe this is what's going on for you?
I had to use pencil and paper to layout the tables, including the width declarations, and then go through it logically. Eventually I discovered that the mac browser was collapsing one cell down to a narrower width than I had declared, because of activity elsewhere in the table. The PC browser was making a different decision. Using a spacer gif in that particular cell fixed the problem.
|It is likely that other mac browsers (safari, mozilla) would |
render the pages with such 'orrible' results?
I'd say that you need to test to find out - it's much more of a browser issue than a platform issue. There's no consistency from one browser to another just because they're on the same OS.
|Is the script, I could use to send ie mac viewers to an alternate page/s |
What PC browsers have you viewed the page on, besides IE? Is all OK on recent Mozilla or Netscape?
I've tested on mozilla 1.0 for pc and it looks better than
ie, (a few minor boarder issues in ie win) also the utility @ http://anybrowser.com/siteviewer.html and even looks 'ok' in html 4.0 Strict.
I've just been reading an article at [url=http://www.alistapart.com/stories/doctype/]ALA[/url] about doctypes and was wandering if that could have any thing to do with the problem. (more here at [url]http://macedition.com/cb/ie5macbugs/notbugs.html[/url]
I've just amended the pages in the site to from
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
apparently mac ie 5 is quite picky about this(?)
and so is netscape 6 which I have'nt yet tested in.
But I suspect the problem is more likely to do with your
suggestion about width and height declarations.
I havenít got access to a mac at the moment so can't experiment with finding a solution :(
I need to test in netscape 6 though
//edit works fine in netscape 6
thanks for your comments
Try to remove the doc type declaration completely, that does no good anyway and might be forcing some kind of rendering to happen, putting the browser into compliance mode, removing the doc type declaration will just get rid of some potential display problems, try testing without it altogether.
The odds are excellent that the page will display right on mozilla for mac, since it's the same gecko rendering engine in all cases as far as I know. I haven't seen any noticeable differences between any of the platforms mozilla runs on, except fonts in linux versions, but that problem is fixed now in latest linux distros from what I've seen.
Ie mac 5x is always a problem, I've almost given up supporting it, although I try to get the stuff to more or less work because I have clients that use it, but even they have gotten used to the familiar refrain: it's an ie mac 5x bug, sorry.
I had a problem in 5.0 which was that the browser would hang on the homepage bcz their was no favicon - it wouldn't load anything else til the favicon loaded... and the site didn't have one. 5.1 fixed it though.
It's tough to abandon IE5/mac support right now. I note that around 70% of all mac users on my client sites are using IE5. And that means a healthy 3% to 5% of all users, a much bigger number than the <1% using NN4 on both win and mac combined.
Because so many developers and designers do not check their work on a Macintosh, we hear less about support problems for IE5/mac than we do for NN4/pc. But it really is a more important browser at this point in time.
However, I know several businessmen who prefer Macintosh - and they all know that it takes more than one browser to get around the web on a Mac and not miss anything important. A sad but true fact of life in the Apple barrel.
The good news is, more and more Mac people are switching to OSX, and more and more of those are switching to Safari. (Those who cannot upgrade, however, I feel sorry for. The Netscapes all suck, Opera is decent but not great, and I don't even know where Mozilla is at.)
In my logs more than half of Mac users are using Safari. A few months ago most of my Mac users were on IE.
The comment about Mac users using many different browsers is correct. Some still don't and won't, but some are coming around. Safari may be good for most tasks, but some websites (especially banks, school registrations, and govt transactions) ONLY work for IE. (Because of their broken, non-compliant code.)
> ONLY work for IE. (Because of their broken, non-compliant code.)
Or even worse because they have a function that checks if you are using IE, if you don't it automatically blocks you - even though the browser works fine.
I hacked mozilla's user agent string to show that it was internet explorer and a site that said I needed IE to continue let me right in. ;)
I ended conveting the site to xhtml. It seems to work now
Mozilla on Mac:
That's my preferred browser - wouldn't use anything else:-)
As to the support for Mozilla on Mac, Mozilla.org skipped the offcial support for Mac OS 9.x somewhere between 1.2.1 and 1.3 focusing completely on Mac OS X which is very well supported.!However! somebody put together a Mac OS 9.x version of Mozilla 1.3.1 with additional bugfixes over and above the official 1.3.1 - see <http://wamcom.org/> he has more or less taken Mozilla 1.3.1 and branched it.
I'm coding to Mozilla and the standards. Subsequently I then use the IE only conditional comment to fix the css errors in IE5.x Win & IE6 by loading supplementary css files.