Well, that was another 45 minutes lost time. How about NoScript light, finally? Else, if QuickJava should introduce per-site settings, NoScript will be deleted.
So I now found out, it has nothing to do with ABE.
I get the following error code when trying in my locally javascript-application (file:///...) to load another webpage-html (http://example1.com) with XMLHttpRequest:
Fehler: uncaught exception: [Exception... "Component returned failure code: 0x805e000a [nsIXMLHttpRequest.open]" nsresult: "0x805e000a (<unknown>)" location: "JS frame :: file:///C:/Dokumente%20und%20Einstellungen/Joe/Eigene%20Dateien/Eigene%20html-Seiten/SOMEWHERE.DE%20-%20Something/javascript_n_templates/XMLHttpRequest.js :: anonymous :: line 24" data: no]
What I found out:
If I tell NoScript, that example1.com is allowed to execute Javascript, then there will be no error, but if example1.com is not allowed to execute Javascript, then the error will show up and stop my application.
The error will of course not show up, if I disable NoScript at all.
It's NoScript Version 2.0.8.1
Btw: I will not register to post here. If some forum-section allows me to post without registering, I might do. Else I won't.
An after browsing through the NoScript-prefs with all the exceptions for websites, which I can't remember to have find as settings in the User-Interface, I'm quite sure you are not really trustworthy anymore.
Feel free to delete. It's your forum after all and your Extension.
But it's my computer here.
Bug-Reprot. So it has nothing to do with ABE
Bug-Reprot. So it has nothing to do with ABE
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2) Gecko/20100115 Firefox/3.6
Re: Bug-Reprot. So it has nothing to do with ABE
You see, I'm quite lucky I had a chance to find out that allowing Javascript for example1.com changes anything:
I only switched to a new Firefox version recently, before still using 1.5.0.6 for some reasons. And it happened that I allowed example1.com before I used my application the first time. Usually I don'T allow example1.com to execute javascript.
Would it have been the other way round, i.e. I would have tried first to run the application without allowing example1.com to execute Javascript: the application would have never worked at all and I would have seen that error and would have been to think it has something to do with the browser, because in 1.5.0.6 it worked perfectly. (I don'T know if example1.com is allowed to execute javascript in the Noscript-settings in the 1.5.0.6 browser. But I will look it up.)
I only switched to a new Firefox version recently, before still using 1.5.0.6 for some reasons. And it happened that I allowed example1.com before I used my application the first time. Usually I don'T allow example1.com to execute javascript.
Would it have been the other way round, i.e. I would have tried first to run the application without allowing example1.com to execute Javascript: the application would have never worked at all and I would have seen that error and would have been to think it has something to do with the browser, because in 1.5.0.6 it worked perfectly. (I don'T know if example1.com is allowed to execute javascript in the Noscript-settings in the 1.5.0.6 browser. But I will look it up.)
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2) Gecko/20100115 Firefox/3.6
Re: Bug-Reprot. So it has nothing to do with ABE
So it's NoScript 1.1.7 and now Firefox 1.5.0.12 (Installing Firefox 3.6 and using it a couple of time turned automatic updates on in my old browser somehow. I have seen the confirmation dialog in my 1.5... version if I want to update, so it's nothing I imagine. Obviously some minor quiet updates were done too from .6 to .12. You see the same problem as here: Explicitly Not Wished Actions by a Program.)
So in that old Firefox my application runs fine, though NoScript isn'T set to allow example1.com to execute Javascript.
No errors there.
(I always got the getInterface-missing error there like some thousand times when downloading big files when using:
until I finally changed
channel.notificationCallbacks = myOwnObjectImplementingGetInterface;
I only found out that error was fired by some NoScript-function when I started using FF 3.6, as FF 1.5 didn't show a link to the code where the error occured. You have some routine in your NoScript that seems to hook in in every download and firing your function at every progress-event which is quite a lot.
So in that old Firefox my application runs fine, though NoScript isn'T set to allow example1.com to execute Javascript.
No errors there.
(I always got the getInterface-missing error there like some thousand times when downloading big files when using:
Code: Select all
var obj_URI = Components.classes["@mozilla.org/network/io-service;1"].getService(Components.interfaces.nsIIOService)
.newURI(MyThis.theURL, null, null);
const CI = Components.interfaces;
// Now go download the remote file, and store it somewhere local.
var ioService = Components.classes["@mozilla.org/network/io-service;1"].getService(CI.nsIIOService);
var channel = ioService.newChannelFromURI(obj_URI);
channel.loadFlags |= Components.interfaces.nsIRequest.LOAD_BYPASS_CACHE;
channel.notificationCallbacks = none;
channel.notificationCallbacks = myOwnObjectImplementingGetInterface;
I only found out that error was fired by some NoScript-function when I started using FF 3.6, as FF 1.5 didn't show a link to the code where the error occured. You have some routine in your NoScript that seems to hook in in every download and firing your function at every progress-event which is quite a lot.
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2) Gecko/20100115 Firefox/3.6
Re: Bug-Reprot. So it has nothing to do with ABE
Clarification for the getInterface-error:
With: "I only found out that error was fired by some NoScript-function" I mean, your function tried to access something that wasn'T there (as I still used channel.notificationCallbacks = none;) and Firefox then showed the error in the javascript-logs.
With: "I only found out that error was fired by some NoScript-function" I mean, your function tried to access something that wasn'T there (as I still used channel.notificationCallbacks = none;) and Firefox then showed the error in the javascript-logs.
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2) Gecko/20100115 Firefox/3.6
- Giorgio Maone
- Site Admin
- Posts: 9524
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Bug-Reprot. So it has nothing to do with ABE
Very unlikely, until NoScript exists. And script blocking without the rest is really weak.still really pissed of wrote:Well, that was another 45 minutes lost time. How about NoScript light, finally? Else, if QuickJava should introduce per-site settings, NoScript will be deleted.
still really pissed of wrote: So I now found out, it has nothing to do with ABE.
Very likely this:still really pissed of wrote: So why are you posting in the ABE forum, exactly?
I get the following error code when trying in my locally javascript-application (file:///...) to load another webpage-html (http://example1.com) with XMLHttpRequest:
Fehler: uncaught exception: [Exception... "Component returned failure code: 0x805e000a [nsIXMLHttpRequest.open]" nsresult: "0x805e000a (<unknown>)" location: "JS frame :: file:///C:/Dokumente%20und%20Einstellungen/Joe/Eigene%20Dateien/Eigene%20html-Seiten/SOMEWHERE.DE%20-%20Something/javascript_n_templates/XMLHttpRequest.js :: anonymous :: line 24" data: no]
What I found out:
If I tell NoScript, that example1.com is allowed to execute Javascript, then there will be no error, but if example1.com is not allowed to execute Javascript, then the error will show up and stop my application.
NoScript Changelog wrote: v 1.4.9.4
==========================================================================
+ Added client-side policy control for new Firefox 3 cross-site XHR,
configurable via noscript.forbidXHR about:config preference:
0 - Allow any XHR
1 - Allow cross-site XHR across trusted sites only (default)
2 - Allow same-site XHR only (like Firefox 2)
3 - Forbid all XHR
The "NoScript Support" forum is there exactly for this. How did you miss it?still really pissed of wrote: Btw: I will not register to post here. If some forum-section allows me to post without registering, I might do. Else I won't.
I'm moving this topic there where it belongs.
BTW, if you registered you'll have an easier life at following your own topics (you know, mail notifications and this gay stuff)...
And I'm quite sure you should give up drinking in the morning. Would you care to list the exception you found and the malicious intent behind each of them?still really pissed of wrote: An after browsing through the NoScript-prefs with all the exceptions for websites, which I can't remember to have find as settings in the User-Interface, I'm quite sure you are not really trustworthy anymore.
OMG, how will I pursue my world domination evil plan now, that I cannot violate your precious PC?still really pissed of wrote: Feel free to delete. It's your forum after all and your Extension.
But it's my computer here.
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13