views:

821

answers:

3

I am writing a custom .pac script for use with Firefox. Following numerous examples I've seen, I intersperse alert()s in order to debug it, but no alerts popup, even though the script is clearly being invoked. (I am clicking "Reload" in the "Connection settings" after each change to my script. I have even tried restarting Firefox.)

Are alerts supposed to work from PAC scripts? Maybe this is an IE-only feature?

A: 

You might need to disable "EnableAutoproxyResultCache" in the Windows registry . . .

Noah
According to http://support.microsoft.com/kb/271361, that's an IE feature. That key does not appear anywhere in my registry, and I doubt that it would affect Firefox.
Chris Noe
A: 

Ah Ha! The alert messages are getting logged to the console. I actually prefer that to alert popups anyway.

Chris Noe
+2  A: 

http://mxr.mozilla.org/mozilla-central/source/netwerk/base/src/nsProxyAutoConfig.js

The alert function is added to the sandbox:

80         // add predefined functions to pac
81         this._sandBox.importFunction(myIpAddress);
82         this._sandBox.importFunction(dnsResolve);
83         this._sandBox.importFunction(proxyAlert, "alert");

And the mapped function calls dump, which goes to the Error Console:

108 function proxyAlert(msg) {
109     msg = XPCSafeJSObjectWrapper(msg);
110     try {
111         // It would appear that the console service is threadsafe.
112         var cns = Components.classes["@mozilla.org/consoleservice;1"]
113                             .getService(Components.interfaces.nsIConsoleService);
114         cns.logStringMessage("PAC-alert: "+msg);
115     } catch (e) {
116         dump("PAC: proxyAlert ERROR: "+e+"\n");
117     }
benc
Interesting. I wonder why they unilaterally convert alerts to log dumps. I suppose popping alerts during such a low-level operation is considered unacceptable.
Chris Noe
Yeah. Its not in the spec, it's not in any PAC bug I ever found (I tested Proxy and PAC for Netscape/AOL/Mozilla). We could go digging in the changelog...
benc
It occurs to me that alert() probably requires a Window object, and being a network-level operation, there certainly is no Window object yet. There's not even a TCP connection yet, since the PAC script is helping decide how we're going to connect...
Chris Noe
Chris, you are probably right. The low-level implementation of PAC involves running javascript in a sandbox, worrying about how it relates to blocking activity like DNS lookups. Putting up alerts in a dialog box was probably just too much work. I would imagine IE has similar concerns.
benc