Thanks so much! The problem is resolved. It was caused by a plugin making an ajax call via mootools-core.js from http to https.
On Wednesday, November 7, 2012 2:32:54 AM UTC+2, hazlema wrote: > > II loaded up the page in FF and IE9. The console didn't generate any > errors but 'LOG: FB.getLoginStatus() called before calling FB.init(). '. > All three sliders appeared to work in IE9. > > Other errors I logged with Firebug: > > 1. FB.getLoginStatus() called before calling FB.init(). > 2. all.js#xfbml=1 (line 52) > 3. Exposing chrome JS objects to content without __exposedProps__ is > insecure and deprecated. See > https://developer.mozilla.org/en/XPConnect_wrappers for more > information. > 4. [Break On This Error] > 5. > > ...conds();wa=na.getUTCMilliseconds();}na=(pa<=0||pa>=10000?(pa<0?"-":"+")+o(6,pa<0... > > 6. xd_arb...sion=14 (line 13) > 7. Exposing chrome JS objects to content without __exposedProps__ is > insecure and deprecated. See > https://developer.mozilla.org/en/XPConnect_wrappers for more > information. > 8. GET http://static.ak.fbcdn.net/rsrc.php/v2/y4/r/pkOztHQw5vM.js > 9. 200 OK 130ms > 10. like.p...t=false (line 249) > 11. Exposing chrome JS objects to content without __exposedProps__ is > insecure and deprecated. See > https://developer.mozilla.org/en/XPConnect_wrappers for more > information. > 12. Exposing chrome JS objects to content without __exposedProps__ is > insecure and deprecated. See > https://developer.mozilla.org/en/XPConnect_wrappers for more > information. > 13. Exposing chrome JS objects to content without __exposedProps__ is > insecure and deprecated. See > https://developer.mozilla.org/en/XPConnect_wrappers for more > information. > 14. Exposing chrome JS objects to content without __exposedProps__ is > insecure and deprecated. See > https://developer.mozilla.org/en/XPConnect_wrappers for more > information. > 15. The character encoding of a framed document was not declared. The > document may appear different if viewed without the document framing it. > 16. Error: Permission denied to access property 'toString' > 17. Exposing chrome JS objects to content without __exposedProps__ is > insecure and deprecated. See > https://developer.mozilla.org/en/XPConnect_wrappers for more > information. > > The page however seems to function ok. Can you be more precise on how to > reproduce this error? > > On 11/6/2012 4:38 PM, Chesky wrote: > > I have three "content" slideshows on my joomla site (freeslider sp1) the > javascript is powered by mootools. In all browsers they work fine except > for IE. In IE9 I get the following error: > > SCRIPT5: Access is denied. mootools-core.js, line 483 character 2. > > I have tried disabling jQuery, updating mootools-core.js. I would like to > fix this problem without rewriting mootools-core.js which is out of my > capacity. The url is http://www.secureamericanow.org/ > > This issue has been driving me crazy! > > Thanks, > > >
