Add-ons • Re: Working on a Greasemonkey fork for Pale Moon

So, I'm currently working on:

• deleting 'framescript'/'messageManager' round-trip that is doing nothing on a single-process browser, replacing it with direct chrome-side injection (Unless if someone just decides to approach me and be like "Why did you delete that, I was making a fork of Pale Moon, but was about to introduce e10s into it and now your extension is unusuable in my browser").

• 'GM_util.getService()'-style indirection that exists only because Mozilla once threatened to take JSMs away - collapsing them to direct calls.

• XBL bindings that aren't load-bearing — convert to anonymous content + JS

And some Multi-process /e10s idioms surviving in places where they no longer matter.

I tried to avoid doing that, but the more I develop the extension, the more my code goes through friction with dirty code. It's inevitable for me to do something about it, and it'll definitely take a lot of time and effort in order to fix such thing.

I'm glad that the latest 3.6.1 is already stable and nobody reported any instability issues with it - this gives me so much room for me to stay off-grid and do nothing but streamlining my code and hopefully I get to fix some long-standing bugs that cannot be fixed by any other way except streamlining it.

So, the per-script option redesign update will be delayed for a bit, until I streamline the extension.