Home › Forums › Bugs

As of Fx4.0b9pre-2011-01-08 FoxyProxy Std 2.22.4 stopped working

Sat, 01/08/2011 - 20:14 — yamaban

Hello altogether,
I'm sorry to report that in Firefox 4.0b9pre from 2011-01-08
(from ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2011-01-08-03-mozilla-central-l10n/) the Addon stopped working.
The toolbar icon and the context-menu entry are still there, but nothing happens if you click on them. Also it's proxy-selection function no longer works, Firefox falls back to the config->network options.

I get the following error message in the console:
Error loading component match.js: SyntaxError: property name pattern appears more than once in object literal
("match.js")@{path-to-profile}/extensions/foxyproxy@eric.h.jung/components/foxyproxy.js:43
@{path-to-profile}/extensions/foxyproxy@eric.h.jung/components/foxyproxy.js -> {path-to-profile}/extensions/foxyproxy@eric.h.jung/components/proxy.js:64

I hope this give a little info for solving this. Thanks for this excellent addon.

‹ Automatic Proxy config changes to Direct Connection when script load fails FF Beta 9 kills FP again. ›
Sat, 01/08/2011 - 23:55 — KWierso

I'd be interested in what

I'd be interested in what the solution is for this, as one of my addons has a similar error appearing in the nightly.

Sun, 01/09/2011 - 01:26 — KWierso

I'm suspecting it's

I'm suspecting it's https://bugzilla.mozilla.org/show_bug.cgi?id=622321 but I need to wait for some builds to be made that come from that change and from the one right before it to find out.

Sun, 01/09/2011 - 05:17 — KWierso

Okay, it is

Okay, it is https://bugzilla.mozilla.org/show_bug.cgi?id=622321 that's causing this. You can no longer use any of the following in your JS code:

({ x: 1, get x() { } })
({ x: 1, set x(v) { } })
({ get x() { }, x: 2 })
({ set x(v) { }, x: 2 })
({ get x() { }, get x() { } })
({ set x() { }, set x() { } })

(Where 'x' is some function or object.)

Sun, 01/09/2011 - 08:35 — yamaban

Wow, that's fast!

Thanks @KWierso!
Now comes the hard part: Implementing the needed change.
I admit freely that I don't have enough knowledge of JS to produce a patch.

Thanks non the less, this makes it easier for all addon-developers to hunt down errors in their implementation. I know at least just why I've made a wide way around such code, and implement such things discrete.

Wed, 01/12/2011 - 15:07 — idrugoy

Please, fix this ASAP

Hello,

Please, could you fix the extension to make it work under latest Fx nightlies as soon as possible?
Fx nightlies are quite stable for a long period by now, so there are quite many users (and I am one of them), that use nightly version of Fx as a main browser. I am really looking forward to get your add-on fixed, since I got used to it pretty fast, and now, when it's not working - this problem really bothers me much.
If anyone could quickly post a fixed version - I'll be very grateful for that.
Thanks in advance.

Regards,
Paul.

Thu, 01/20/2011 - 23:56 — yamaban

FPstd has fix, please update

Eric Jung has released Foxproxy Standard 2.22.5 which fixes this Bug.
for Foxproxy Basic there is also an update. This matter is closed.