Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js RSS

• • Reply
  

  zeroup_vn

  Member

  2 Points

  1 Post

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Sep 09, 2009 07:38 AM|LINK

  It seems to me that the issue still occurs in the .NET Framework 3.5 SP1. Does any of you have an idea on if Microsoft will put that fix into the MS AJAX library? I would like to post a support case to Microsoft Support (http://support.microsoft.com) to request for an official feedback from them on the issue. When submitting the case, it required to key in the Access ID and Contract ID. Does any of you know where to get those 2 IDs? My company is already a Microsoft Certified Partner. Are those 2 IDs obtained from the Microsoft Partner Program Portal?

  Thanks.
  

• • Reply
  

  celoftis

  Member

  56 Points

  355 Posts

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Oct 08, 2009 01:04 PM|LINK

  danludwig

  I've experimented with this bug a lot, and the best temporary solution is the one proposed by kshakir (second post in this thread). Simply create a single JS file with his code and reference it in your site. To work properly, this script should be loaded before any AJAX control scripts. For my applications, I simply reference it as the first script in the ScriptManager, like so:

  <asp:ScriptManager ID="ScriptManager1" runat="server">
      <Scripts>
          <asp:ScriptReference Path="~/Scripts/Safari3AjaxHack.js" />
      </Scripts>
  </asp:ScriptManager>

  The file can exist in any folder in your site, but as kshakir says, it should contain this code:

  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';
  }
  

  Microsoft and the AjaxControlToolkit project managers tell me they want to fix this bug in the toolkit, so eventually this hack will (hopefully) no longer be necessary. But in the meantime, this solution solves the problem with AjaxControlToolkit scripts not being loaded properly during partial updates.

  
  

  Thanks very much - this worked for me!

  WebKit browsers UpdatePanel Literal

• • Reply
  

  BBuzzi

  Member

  159 Points

  110 Posts

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Nov 03, 2009 06:49 PM|LINK

  Hi everybody,

   

  Using the code behind command Page.ClientScript.RegisterClientScriptBlock(...) doesn't work in Chrome.

  Could somebody tell me if it has something to do with this thread?!

  Anyway, I'll try this solution to check this out.

   

  What looks a little strange for me is that I did not add this solution to my project yet, but it is working ok with tabs and partial updates.

   

  Thanks,

   

   

  Thanks!
  
  Bruno Buzzi
  brunobuzzi@gmail.com
• • Reply
  

  twilsontomet...

  Member

  16 Points

  3 Posts

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Nov 13, 2009 04:46 PM|LINK

  Thank you! Works great!

• • Reply
  

  StrouMfios

  Member

  27 Points

  31 Posts

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Dec 18, 2009 02:05 PM|LINK

  Works great for me.

  Thank you very much.

• • Reply
  

  Ranmonster

  Member

  5 Points

  5 Posts

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Jan 20, 2010 09:19 AM|LINK

  Works in Chrome !!! Thank you :) 

• • Reply
  

  Rojzik

  Member

  2 Points

  1 Post

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Feb 11, 2010 06:52 PM|LINK

  This worked for me.  I can't believe it's still a problem over 1 YEAR later.  Thanks!

  thankyou

  • Edited by Rojzik on Feb 11, 2010 06:52 PM
• • Reply
  

  ncsuwolf

  Member

  10 Points

  7 Posts

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Feb 17, 2010 07:05 PM|LINK

  I am using Google Chrome, version 4.  It keeps the site from throwing an error, but it still prevents the control from actually doing what I want it to.  I have a control to help extend the session for our users, as they are away from the screen for periods long enough for the session to expire.  Well, after the session has been "extended" for a set number of times, I redirect to the logout page and log the user out.  This all works fine in IE6, IE7 and IE8 and the latest Firefox, but not in Google Chrome and probably not in Safari.  Is there anything else that needs to be done besides adding the javascript workaround?  I put the following in a separate .js file:

  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';
  }

  I then referenced the script on the masterpage where the control is located:

  <script type="text/javascript" language="javascript" src="/Workarea/java/webkit.js"></script>

  So, I am confused.  The update panel is working as far as updating the current page, but when trying to redirect to another page - it does nothing. No error, nothing, the session just expires.  I am a little stumped.

  The code is written in ASP.NET 3.5 SP1 with the latest version of the AJAX Control Toolkit.

  Thanks.

  • Edited by ncsuwolf on Feb 17, 2010 07:12 PM
• • Reply
  

  danludwig

  Contributor

  3020 Points

  601 Posts

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Feb 17, 2010 07:16 PM|LINK

  How exactly is the redirect done? From the server control via Response.Redirect? Or from javascript by setting location.href?

  My Signature: Mark a post as answered if it helped you, or don't, it makes no difference to me. Just PLEASE try not to use the word "random" when describing your problem.
• • Reply
  

  ncsuwolf

  Member

  10 Points

  7 Posts

  Re: Compatibility patch for WebKit (Safari 3) 3.5.21022.8 MicrosoftAjax.debug.en-US.js

  Feb 17, 2010 09:22 PM|LINK

  It is redirecting from the server control.  Here is a code sample:

  Context.Response.Redirect(VirtualPathUtility.ToAbsolute(redirectPage));

  Kind of an odd issue.  I added an update panel to the master page's footer to show session variable count, session id, refresh time, etc.. to debug that the session was indeed staying alive.  These show and are updated everytime the session is refreshed.  When the session times out and the page doesn't redirect, the data is updated to tell me that my session variables are gone, a new session id has been created, etc... in Goolge Chrome that is.  In Firefox and IE, a redirect occurs to the Logout.aspx page and the user is logged out gracefully and they know when they come back to the site that they were idle for x number of minutes (almost 2 hours) and they need to log back in.

  I haven't dealt with Google Chrome/Safari or the web kit browsers before now, so any help would be greatly appreciated.

  Thanks.

  • Edited by ncsuwolf on Feb 17, 2010 09:26 PM