unreachable code after return statement

[L-a-n-g-o-l-i-e-r-s]

Hi there,

For whatever reason, on my Waterfox profile, when attempting to browse either by pasting a directory in or trying to locate one via pop open explorer, it will not navigate or open that dialogue at about:xpiler.

The console is giving this error when trying to click the button "unreachable code after return statement". It worked on a new profile, it was working on my Firefox profile, now it's not working after compiling and restarting Firefox, the history for compiled extensions also vanished.

Same behavior for my usual Waterfox profile

Perhaps you can offer some advice, I have tried toggling multiple extensions, not sure what's causing this.

Edit:

Sometimes it works when I'm swapping profiles, doesn't make much sense.

Thanks

[Noitidart]

Aw shoots, Firefox changed so much it is completely broken. I know that in Firefox 56 (one before the v57 update) the about:*** page navigation changed considerably. :(

[L-a-n-g-o-l-i-e-r-s]

I'm on FF 56.0.2 x64 not the anti-choice 57 XUL/XPCOM ender, it'd be so nice if they would make their mind up and break everything when they drop 57 rather than breaking things before 57, rather than lie about it.

I'm curious why the extension works every now and then, very strange indeed. You probably don't have the time nor the desire to maintain the extension because I'll be in the minority, scrambling to grasp any XPCOM/XUL support I can from anywhere and everywhere. I don't know, I'll tell you one thing, I'll create new profiles in waterfox -p -no-remote and install the extension drag and drop easy peasy no problem, I'm not going back to the rubbish way.

There are somethings that I absolutely cannot live without, for example, Location Bar Enhancer, browsing without it seems incredibly primitive and regressive.

Anyway, terribly sad, out of the few that do customize (Stats could be skewed due to people disabling basic telemetry.) that the extensions and developers are taking the heat of scorned users. Totally unacceptable, Mozilla needs to put a GIANT message on the front page of addons.mozilla.org and take entire responsibility and explain what is happening, with a clear message NOT to harass developers and bomb ratings.

That way, XPCOM / XUL extension developers, future or current porters are not discouraged by misplaced rage and rating bombing. I can't imagine "legacy" extensions will remain cataloged for historical purposes, I heard rumblings a bit ago that new "legacy" extensions couldn't be uploaded to addons.mozilla.org.

I'm sorry, I'm on a big rant, I just find it totally unacceptable that they continue to break things before they said they were going to break things. 💯 😠 They're not doing a good enough job, most users don't read blog posts, they go straight to the landing page.

May the ghost of XPCOM/XUL past visit Mozilla. 👻😠

By the way, does it also compile webextensions correctly?

[Noitidart]

Hahaha love your reply.

I really would so so love to support even a single user like you, as you are sooo motivational to me. I actually am so swamped with work right now that I didn't get time. I am also trying to add non-intrusive, "request card" so that people can support me. Definitely not ads, just a popup every 30 days (which can be disabled) asking for support. My hope is ideally that my works turn into cash flow so I can switch to working part time or even not at all and focus all my efforts here.

I think XPICompiler would compile webextensions too, all it does is zip it up and make an xpi out of it.