Bug #36363
Javascript uncaught exception
| Status: | Accepted | Start date: | 2012-04-20 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| Votes: | 0 |
Description
If I have installed the extension and added the static ts template, I get a javascript error on every page (even if the plug-in is not placed on the page):
uncaught exception: Error: <http://static.ak.facebook.com> wurde die Erlaubnis für das Lesen der Eigenschaft Proxy.InstallTrigger verweigert.
(in english:
uncaught exception: Error: <http://static.ak.facebook.com> has permission to read the property Proxy.InstallTrigger denied.)
And also the extension adds the following on every page (plug-in not placed on page):
<div id="fb-root"></div>
<script src="typo3temp/javascript_db4b080e49.js" type="text/javascript"></script>
Why do I need this on every page? And why do I need <div id="fb-root"></div>?
Thank you!
History
Updated by Refresj internetbureau about 1 year ago
- Status changed from New to Accepted
Thanks for submitting!
The error is a bug in Firebug:
http://stackoverflow.com/questions/8251540/uncaught-exception-permission-denied-to-proxy-installtrigger
On the Facebook developer page i found this:
The fb-root element must not be hidden using display: none or visibility: hidden, or some parts of the SDK will not work properly in Internet Explorer.
The SDK inserts elements into fb-root which expect to be positioned relative to the body or relative to an element close to the top of the page. It is best if the fb-root element is not inside of an element with position: absolute or position: relative. If you must place the fb-root element inside of a positioned element, then you should also give it a position close to the top of the body or some parts of the SDK may not work properly.
I will take a look at the problem with the inclusion on all pages.
Updated by Bernhard Eckl about 1 year ago
I have seen this page on stackoverflow you posted, but then I started Firefox using a brand new profile (without any addon, without Firebug…) and the error still occured. So this means, that the error still occurs even if Firebug is not installed at all. And this can be very annoying, even if the plug-in is not placed at the page at all but will still output the code.
Thanks for checking this out!
Updated by Bernhard Eckl 6 months ago
Push!
I do not understand why it should be included on every page output even if there is no plug-in on the current page.