Forum Moderators: not2easy

Message Too Old, No Replies

CSS and Safari

anything odd there?

         

txbakers

5:39 pm on Aug 31, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I just tested some sites in Safari on OSX 3, and noticed that a lot of the CSS wasn't working correctly. Some was and some wasn't.

Is there a guide to working around some of this with Safari? Even Mozilla and Netscape showed the screen correctly, but not Safari.

Thanks.

dcrombie

9:42 am on Sep 1, 2004 (gmt 0)



Safari pretty much follows the standards so I'd be surprised if that was the problem. Can you post the relevant HTML/CSS?

txbakers

12:04 pm on Sep 1, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Thanks d,

I can't really post the URL here, and the site is really a web based application with passwords to get inside.

I remember that Netscape et al were case sensitive, maybe that's the issue with Safari as well.

Safari also doesn't handle the javascript exactly the same was as IE - more fixing for my fringe users.

dcrombie

12:39 pm on Sep 1, 2004 (gmt 0)



Even IE doesn't perform the same as IE across platforms ;)

I'd look here for problems relating to the DOM:
[quirksmode.org...]

In static pages Safari CSS generally matches the Gecko browsers, with a few extensions:
[diveintomark.org...]

isitreal

2:31 am on Sep 2, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Safari is pretty weak, it's ok, but has many bugs, especially for complex stuff. Wish Apple had gone with gecko for their rendering engine, but too late now, have to live with yet another just ok browser with just ok support of various things.

I never understand what it is people mean when they say a browser is 'standards compliant', all the browsers have css bugs, different ones for different browsers and browser versions, the closest thing I can find to an actually standards compliant browser is mozilla, it's all down hill after that. 'Is feature x or y implemented correctly by the browser programmers?' is a more useful statement than 'browser x claims to be standards compliant'.

From what I've seen on the last websites I've done, Safari will have roughly the weaknesses that Opera 7x will have, give or take, plus of course it will have its very own bugs.

whoisgregg

6:46 pm on Sep 3, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



diveintomark.org link:
This page refers to Safari 1.0 (build 85), released 23 June 2003

Current release version of Safari is 1.2.3 (v125.9) and it has corrected nearly every CSS problem from the original release. Safari is an Apple app, so software update keeps it current and most Safari users (according to my site's logs) are running something far better than 1.0. What version were you testing in?

txbakers

7:22 pm on Sep 3, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I was using 1.2.2 from 2004 Surely there can't be that much change between that and 1.2.3

I just bought a new iBook to test with Safari. I have a significant number of mac customers so I should solve it.

isitreal

10:09 pm on Sep 3, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The thing you really want to test on your new ibook is IE 5x mac, that has huge CSS holes and bugs, not to mention only partial dom support, so it's always a crapshoot if CSS pages will display correctly, Safari is more predictable in its failures.

txbakers

10:19 pm on Sep 3, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Oh Yeah - I remember how bad the 5.x was for the Mac.

I tell my clients to only use Safari on Mac because IE is so haphazard.