Safari

it'll get big, I want to be prepared

[Purple Martin]

Safari (based on Konqueror) is going to get big enought to care about because it's the default browser on Mac OS X, so I want to be prepared for it.

Can anyone tell us about any major issues that we need to be aware of when building cross-browser sites?

[txbakers]

I guess the best thing would be to get yourself a new Mac with osX and Safari and test.

The best way to make sure you have valid cross browser code is to write to the validator. Just make sure everything on the page validates.

I already know that some osX users have complained to me about some javascript function not working. (THEY didn't know it was javascript and thankfully they called me.) I fixed it but I expect more errors to come.

[Purple Martin]

I've just quit my job and I can't afford to replace my holey socks, so I can't afford a new Mac ;-)

Writing valid code is certainly sound advice, but we all know that each browser has a few valid things that it can't render, and we learn to avoid those few things where possible. Because Safari is the newest I hope that it is the best at rendering valid code correctly, but no browser is ever perfect and Safari won't be an exception. So if anyone discovers a rendering issue in Safari, please post it here!

[hartlandcat]

If you can't afford a Mac, get Linux and test on Konqueror. It'll make pages look the same. So, it doesn't support quite so much CSS2 as Mozilla, Netscape and other Gecko browsers, but it definately supports more than IE.