function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Marc BaizmanMarc Baizman 

FF3 and sforceclient.js - they don't play nice

So we know that FF3 doesn't play nice with the old sforceclient.js - which, to be fair, was always "in beta" (AJAX Toolkit) - but is used in things which are probably on the AppExchange (i.e Case Timeline).  See beow:
 
 
 
Does anyone know the extent of how many S-controls have been built using the toolkit?  It seems that we would need to rewrite all code that used the beta AJAX Toolkit to use the "official" connection.js, which appears to be a non-trivial task.
 
Thoughts?


Message Edited by Marc Baizman on 06-22-2008 10:55 AM
Ron HessRon Hess
We've noticed this, and several of those apps are worth revisiting and re-writing now with Visualforce.  This is more productive than porting to Ajax since it will result in better performance and the code will be easier to maintain, extend and reuse.
No schedule is set for this effort currently.

Note: FF3 is not in the Salesforce supported browser list at this time, we do plan to add this after we complete our testing.
You can expect this to take up to 90 days.