View Full Version : mac compatible
04-09-2003, 07:44 PM
I would search for this, but I haven't the slightest what to search for...
I'm looking to find out what is mac compliant. How do things change once they are viewed on a mac in comparison to a PC os. Is CSS fine for it? What works in 'normal' html?
Any help is appreciated, thanks.
04-09-2003, 07:55 PM
I havnt the computer to test it, ive never even used a mac.
but im guessing CSS is CSS and HTML is HTML. :confused:
as long as the vendors support the standards i thought i wouldnt matter.
04-09-2003, 07:59 PM
It's like anything - mostly it's the same, but every browser has unique quirks and bugs. In a very loose, hand-waving sense, mac browser are more standards compliant than PC browsers, basically because the 3 major mac browsers are ie5, safari and the browser formerly known as chimera, all of which are pretty compliant; compare this with the dominant windows browsers - ie5 and ie6 - which are comparatively buggy and non-compliant, and you end up with a pretty safe principle - code to the standards and you'll probably be okay.
04-09-2003, 08:15 PM
Makes good sense, thanks a lot.
04-09-2003, 09:24 PM
Actually, it's more complicated. A perfectly standards-compliant page which looks good and works well on a PC across multiple browsers may be unsightly and unusable on a Mac.
The key seems to be more one of simplicity: Don't try anything too fancy, and you should be reasonably safe.
04-09-2003, 09:55 PM
Well it's certainly true that something which works in win/moz and O7 is more likely to work in mac/ie5, than something which only works in win/ie5. But mac/ie5 has some savage bugs hidden away in the deeper crevices of its rendering engine ...
I guess there's no real substitute for having a mac yourself; although browsercam do a pretty good job.
04-09-2003, 10:16 PM
For an example, I just found out that my site crashes IE5.2 on OSX (Jaguar). That is because it uses vertical-align and background-color in combination. It works with either one left out, but not with both.
I really hope Tantek & Co. are working on a new, better version of Tasman that has less crashing bugs and is more stable.
04-09-2003, 10:52 PM
Originally posted by liorean
I just found out that my site crashes IE5.2 on OSX (Jaguar).
So it does ... never seen that before.
04-09-2003, 10:58 PM
No, it's not that usual. Often what happens is that something doesn't work as it should (links in fixed positioned elements that doesn't react on clicks, for instance), or it makes something not render at all (overflow: auto; on html and body elements, for instance). I'll change my site to use relative positioning instead of vertical-align when I update it next. Don't hold your breath, though - I'm lazy.
04-10-2003, 03:21 PM
I recall recently someone posted a link to a resource where you can send a page and they'll check it under a wide range of browsers so you'll be able to see how your page displays. I know it's in a forum message here somewhere but none of the searches I tried located it. Anyone else remember that thread?
04-10-2003, 04:55 PM
Originally posted by Roy Sinclair
I recall recently someone posted a link to a resource where you can send a page and they'll check it under a wide range of browsers ...
it's BrowserCam www.browsercam.com. There's a free trial, and you can post your results publicly with comments to show the differences. Here's an example that Vincent Flanders' put up (of http://www.webpagesthatsuck.com/dailysucker/) that I think speaks to the specific point here: http://www.browsercam.com/public.aspx?proj_id=1695
But having looked at thousands of screen captures at this point, there are signficant implementation differences between even the most current versions. Many of the differences trace back to some basic stuff like operating system level font rendering (kerning, spacing, etc.) For many designs the differences are small. But a little extra space somewhere could mean the difference between your "Sale Starts Today" text being above the fold or below the fold. A little extra space between letters can cause orphans on one browser and not on others.
It's a judgement call on whether your particular design/client can tollerate stuff like that. Other stuff like the one cited above can cause more serious problems.