GrinningCat
10-16-2007, 05:31 PM
Note: Safari 3 is going to cause problems with our site because it is still in a beta phase.
I can certainly understand not officially supporting a browser that's in beta. However, I hope this isn't a sign that Safari 3 will be ignored indefinitely -- it's leaving beta status in less than two weeks as part of the Mac OS X 10.5 "Leopard" release. (Also, as compatibility and underlying implementation go, the version of MobileSafari already released with the iPhone and iPod touch is much closer to Safari 3 than to Safari 2.)
There seem to be a few bugs using Mint on Safari 3 that aren't present with Safari 2: most notably, the Transactions page fails to update properly when clicking the account tabs on the left or using the search field, and the paging buttons at the bottom (for when the list shows more than 100 transactions) don't work at all.
Also, a friendly reminder from Apple (http://developer.apple.com/internet/safari/faq.html): If you need to detect the version of the browser accessing your site, use the AppleWebKit/XX portion of the user-agent string. A given build version of WebKit, the rendering and JavaScript engine embedded in Safari, provides consistent site compatibility in Safari or any third party application embedding WebKit to render page content.
I can certainly understand not officially supporting a browser that's in beta. However, I hope this isn't a sign that Safari 3 will be ignored indefinitely -- it's leaving beta status in less than two weeks as part of the Mac OS X 10.5 "Leopard" release. (Also, as compatibility and underlying implementation go, the version of MobileSafari already released with the iPhone and iPod touch is much closer to Safari 3 than to Safari 2.)
There seem to be a few bugs using Mint on Safari 3 that aren't present with Safari 2: most notably, the Transactions page fails to update properly when clicking the account tabs on the left or using the search field, and the paging buttons at the bottom (for when the list shows more than 100 transactions) don't work at all.
Also, a friendly reminder from Apple (http://developer.apple.com/internet/safari/faq.html): If you need to detect the version of the browser accessing your site, use the AppleWebKit/XX portion of the user-agent string. A given build version of WebKit, the rendering and JavaScript engine embedded in Safari, provides consistent site compatibility in Safari or any third party application embedding WebKit to render page content.