Closed
Bug 701029
Opened 14 years ago
Closed 6 months ago
Error: uncaught exception: Error: Permission denied for <> to get property Proxy.InstallTrigger
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: wowkise, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0 AC/4.0
Build ID: 20111104165243
Steps to reproduce:
nothing special just visited my normal day to day websites you can visit them
http://www.facebook.com
http://www.twitter.com
http://www.huffingtonpost.com
http://www.engadget.com
Actual results:
Error: uncaught exception: Error: Permission denied for <https://www.facebook.com> to get property Proxy.InstallTrigger
Error: uncaught exception: Error: Permission denied for <https://www.twitter.com> to get property Proxy.InstallTrigger
Expected results:
no error should have been triggered since the said websites worked fine in 7.0.1
I have disabled all the addons & themes short of deleting my profile and i keep getting the same error and its not just those 2 websites its seems all websites who linked to a social platform even my private website suffer from the same problem
Comment 1•14 years ago
|
||
I can confirm this issue apparently triggered by the Twitter Intent and Facebook Like buttons with UA Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
A comment on a Twitter Help Center article confirms the issue also on Windows 7 64-bit. (https://support.twitter.com/groups/32-something-s-not-working/topics/133-top-issues/articles/266189-blank-screen-on-login -- by user @xbsaint)
Can confirm this issue on other Web sites, including those I develop.
I can also reproduce with FF8, on all sites I visit with the FB Like button.
Comment 3•14 years ago
|
||
We at Facebook have no idea what's causing this, but would love to fix it if it's something on our end. Let me know if I can help.
Comment 4•14 years ago
|
||
I can reproduce it on Mac OSX Lion with Firefox 8
(In reply to Marshall Roch from comment #3)
> We at Facebook have no idea what's causing this, but would love to fix it if
> it's something on our end. Let me know if I can help.
im not really sure im neither developer or anything like that but i guess its something to with the new Origin tag added in 8.0
Comment 6•14 years ago
|
||
more details on the Origin tag? I went through the 8.0 release notes and bug list but I'm not sure what you're referring to.
i (In reply to Marshall Roch from comment #6)
> more details on the Origin tag? I went through the 8.0 release notes and bug
> list but I'm not sure what you're referring to.
i was refering to this
https://developer.mozilla.org/en/HTML/Element/img#attr-crossorigin
i'm getting this error in firebug:
uncaught exception: Error: <http://www.facebook.com> wurde die Erlaubnis für das Lesen der Eigenschaft Proxy.InstallTrigger verweigert.
Comment 9•14 years ago
|
||
Just FYI, this is apparently a Firebug issue, not a Firefox issue: http://code.google.com/p/fbug/issues/detail?id=4991
Comment 10•14 years ago
|
||
I confirmed in the Firebug ticket that this issue was fixed in Firebug 1.9b2. It is not a Firefox bug.
Comment 11•14 years ago
|
||
This error is raised without Firebug installed. Perhaps Firebug is now masking the error, but this still looks like a Firefox problem to me.
Comment 12•14 years ago
|
||
I can also get this in FF 8.0.1 with Firebug 1.9.0b2 and also with all add-ons disabled. So it looks as though there's something more that just Firebug involved (see comments on http://code.google.com/p/fbug/issues/detail?id=4991)
An example page is : http://www.justshowof.com/demo/socialButton
where I get Facebook related errors on the fisrt load and Facebook AND Twitter related errors on a refresh.
Comment 13•14 years ago
|
||
You are correct, Adam. Firefox's error console does show the exception being thrown. Hadn't looked at this before (so used to using Firebug for everything; not a core Gecko dev.).
This is probably a FF bug as you said.
Comment 14•14 years ago
|
||
This error can be simply triggered by setting document.domain to any valid value in any webpage using javascript. For example, assuming the follow page can be visited by http://foo.com/bar.html.
------------------------------------
<!DOCTYPE html>
<script>
document.domain = 'foo.com';
</script>
------------------------------------
Then the error message "uncaught exception: Error: Permission denied for <http://foo.com> to get property Proxy.InstallTrigger" shows in the error console.
Comment 15•14 years ago
|
||
so, now what? the errors are still happening - from Facebook scripts; and it seems like it is affecting other JavaScript scripts.
Comment 16•14 years ago
|
||
¿Me podeis ayudar con este error? Ya no se que hacer
Error: uncaught exception: Error: Permiso denegado para <http://static.ak.facebook.com/> para cargar la propiedad Proxy.InstallTrigger
Comment 17•14 years ago
|
||
FireFox 9.01
FireBug 1.8.4
I have recently added a Facebook Status Link to our website: http://smutsniffer.com
Code below is a copy/paste from Facebook:
<script>
(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) {return;}
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_US/all.js#xfbml=1";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));
</script>
FireBug Error: uncaught exception: Error: Permission denied for <http://www.facebook.com> to get property Proxy.InstallTrigger
It appears the javascript is trying to connect using http instead of https. For some reason it is not "forcing" a https (secure) connection.
Here is the all.js Facebook function that should be utilized, but is not.
FaceBook all.js from: http://connect.facebook.net/en_US/all.js#xfbml
if(FB.initSitevars.forceSecureXdProxy)b=true;var g=FB.getDomain((b?'https_':'')+'cdn')+FB.XD._xdProxyUrl+'#';
Hope this helps...
Sniffer
Comment 18•14 years ago
|
||
(In reply to Kz from comment #14)
> This error can be simply triggered by setting document.domain to any valid
> value in any webpage using javascript. For example, assuming the follow page
> can be visited by http://foo.com/bar.html.
>
> ------------------------------------
> <!DOCTYPE html>
> <script>
> document.domain = 'foo.com';
> </script>
> ------------------------------------
>
> Then the error message "uncaught exception: Error: Permission denied for
> <http://foo.com> to get property Proxy.InstallTrigger" shows in the error
> console.
+1 reproduced
And I am afraid this bug sometimes affect other scripts !
Comment 19•14 years ago
|
||
I am seeing this error in my error console at gmane.org with Firefox 11 (Aurora) without having Firebug installed.
Comment 20•14 years ago
|
||
I am having problems viewing and creating email on my hotmail account at mail.live.com ... and noticed tons of several errors that say:
Error: uncaught exception: Error: Permission denied for <https://snt109.mail.live.com> to get property Proxy.InstallTrigger
Error: uncaught exception: Error: Permission denied for <https://secure.shared.live.com> to get property Proxy.InstallTrigger
Could these errors be affecting my ability to view/create email?
Has the source of these errors been found?
Comment 21•14 years ago
|
||
I forgot to mention more details: Windows 7 x64, Firefox 9.0.1, addons disabled, cache cleared, cookies deleted, restarted firefox... and still got those errors.
Also, I constantly get a message within my hotmail tab that says:
We've updated Hotmail, so please refresh your browser or close it and sign in again. If you are composing a message, make sure you save it as a draft.
... even if I've deleted the cache/cookies and restarted!
I'm wondering if it might be related to the uncaught exceptions... There are also several dozen css warnings that the page spews out.
Comment 22•14 years ago
|
||
I see it also with Aurora daily build, Windows 7, pretty mpuch no plugin installed, fresh machine, never logged in to facebook
Comment 23•14 years ago
|
||
(In reply to Kz from comment #14)
> This error can be simply triggered by setting document.domain...
Yes, but not so simply. If I write document.domain AND window.open() I get the Proxy.InstallTrigger exception. Either by itself is harmless.
Further spookiness, the exception happens at window.open() time but cannot be caught.
Example (visibone.com/pderror.html):
------------------------------------
<script>
// Full error message on the error console (Tools | Web Developer | Error Console, or Ctrl-Shift-J):
// Error: uncaught exception: Error: Permission denied for <http://visibone.com> to get property Proxy.InstallTrigger
try {
document.domain = document.domain; // If I do this...
alert('Before "uncaught exception"');
window.open("http://mozilla.org/favicon.ico"); // ...and this, then I get "uncaught exception" on the error console
alert('After "uncaught exception"');
} catch(e) {
document.write(e.message);
}
</script>
------------------------------------
Firefox 10.0, Win2K, no FireBug
Comment 24•14 years ago
|
||
I also noticed this error on FF 10.0.1 when I code with an Iframe and javascript, even with the same domain or hostanme for the iframe link.
this exception was not visible on FF 6 and earlier
Comment 25•13 years ago
|
||
I can reproduce with Firefox 11 on Windows XP.
Updated•3 years ago
|
Severity: normal → S3
Comment 26•3 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 23 votes.
:mossop, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(dtownsend)
Comment 27•3 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Flags: needinfo?(dtownsend)
Comment 28•6 months ago
|
||
This issue was very likely fixed long time ago, but I didn't try to bisect what fixed it given that InstallTrigger has been disabled on all channels (by Bug 1772901 in Firefox 103), and we will remove its implementation as part of Bug 1776426.
Status: UNCONFIRMED → RESOLVED
Closed: 6 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•