-
December 27th, 2006, 02:43 PM
#1
It is impossible to prepare a workaround for this issue. So we have introduced in the Web Client a feature that will detect when the issue arises and then disconnects the client and prompts with an alert. This will allow users using "broken" browsers to reload the page in order to return to correct functionality (or better advise them to upgrade the browser )
The feature has been introduced since version 4.1 build 1254 (check the changelog in the distribution)
The prompted message is the following:
It has been detected that the JavaScript engine of this browser is not respecting the timeouts in setTimeout method calls. The Client has been disconnected from the Server in order to avoid reconnection loops. To try again, just refresh the page.
Similar Threads
-
By cara713 in forum Client SDKs
Replies: 1
Last Post: January 13th, 2012, 08:54 AM
-
By emiliob in forum Client SDKs
Replies: 7
Last Post: June 21st, 2010, 02:59 PM
-
By chuan_ckc in forum Client SDKs
Replies: 7
Last Post: December 17th, 2009, 10:15 AM
-
By markgoldin in forum Client SDKs
Replies: 5
Last Post: September 26th, 2008, 11:28 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 08:27 AM.
Bookmarks