Proxy clients appear broken in new release

User Help for Seamonkey and Mozilla Suite
Post Reply
tyukok
Posts: 18
Joined: November 8th, 2021, 4:49 pm

Proxy clients appear broken in new release

Post by tyukok »

Up until now I've been using FoxyProxy Standard as my proxy client of choice. But now SeaMonkey 2.53.10 came out, and, unfortunately, now it doesn't work.
I tried to use other clients from SeaMonkey add-on page, but they all appear broken too (they are either missing certaing parts of their UI, or even all of it, but the worst part is that none of them seem to work).
What do I even do now? I really need a functional HTTPS proxy client.
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: Proxy clients appear broken in new release

Post by frg »

It use the obsolete try / catch syntax and needs an aupdate. Should be quite easy to fix it yourself.

Zeitstempel: 17.11.2021, 12:05:02
Fehler: SyntaxError: missing ) after catch
Quelldatei: resource://foxyproxy/authPromptProvider.jsm
Zeile: 296, Spalte: 17
Quelltext:
} catch (e if e.name === "NS_NOINTERFACE") {


Same for the version parameter but this one is just ignored.

Zeitstempel: 17.11.2021, 12:05:02
Fehler: Versioned JavaScripts are no longer supported. Please remove the version parameter.
Quelldatei: chrome://foxyproxy/content/firefoxOverlay.xul
Zeile: 19
tyukok
Posts: 18
Joined: November 8th, 2021, 4:49 pm

Re: Proxy clients appear broken in new release

Post by tyukok »

frg wrote:It use the obsolete try / catch syntax and needs an aupdate. Should be quite easy to fix it yourself.
Ah, I see. But what would be the correct syntax in this case? I have no knowledge of JavaScript.
For now I just removed the whole "if e.name === "NS_NOINTERFACE" bit, that seems to have done it, it works now.
The code used to be like this:

Code: Select all

      } catch (e if e.name === "NS_NOINTERFACE") {
        throw CR.NS_ERROR_NO_INTERFACE;
      } catch (e) {}
Now it's just

Code: Select all

      } catch (e) {}
frg
Posts: 1361
Joined: December 15th, 2015, 1:20 pm

Re: Proxy clients appear broken in new release

Post by frg »

In this case:
} catch (e) {
if (e.name === "NS_NOINTERFACE")
throw CR.NS_ERROR_NO_INTERFACE;
}
tyukok
Posts: 18
Joined: November 8th, 2021, 4:49 pm

Re: Proxy clients appear broken in new release

Post by tyukok »

frg wrote:In this case:
} catch (e) {
if (e.name === "NS_NOINTERFACE")
throw CR.NS_ERROR_NO_INTERFACE;
}
Ok, that worked. Thank you!
Post Reply