Apple, however, is going to need to make the sell to people who don't know what they're doing if they want Safari to make it in Windows.
And a glitch like this is something that they should probably handle in their own code.
1) Most people with such mice won't want to screw around in SetPoint and set up custom conditions.
2) Taking any of Firefox's marketshare is going to require some work on Apple's part.
3) The look and feel of Safari (no back/forward mouse buttons, anemic scroll rate compared to rest of system) is something that's currently inconsistent with how the iTunes Store works in iTunes - which DOES have working back/forward buttons and system scroll rate.
So despite this quick fix, this is something that really needs to be resolved by Safari itself.
