This is likely a bug with ASP.Net instead of the store itself. Please note that you'll need to include some extra code in your ScriptManager. I added the following line:
Code:
<asp:ScriptReference Path="~/jscripts/SafariChromeAJAXFix.js" />
The file contains:
Code:
// Safari 3 AJAX "issue". It no longer needs JavaScript hacks that are still implemented
// http://forums.asp.net/p/1252014/2392110.aspx
Sys.Browser.WebKit = {}; //Safari 3 is considered WebKit
if (navigator.userAgent.indexOf('WebKit/') > -1) {
Sys.Browser.agent = Sys.Browser.WebKit;
Sys.Browser.version = parseFloat(
navigator.userAgent.match(/WebKit\/(\d+(\.\d+)?)/)[1]);
Sys.Browser.name = 'WebKit';
}