Webextension API merge strategy

[Happy-Ferret]

As an interested developer, I'd like to know if there's any merge strategy in place for dealing with the newer Webextension APIs introduced with FF57+.

Some of the changes can be easily cherry-picked or applied with git am (browser.privacy.websites.trackingProtectionMode, for one), others require somewhat more work in order to not run into merge conflicts or even touch files outside of toolkit/components/extensions.

Any solid merge strategy to deal with this, @MrAlex94?

I wouldn't mind helping on that front, btw.

[grahamperrin]

See also: #267 (comment)

[Peacock365]

@Happy-Ferret

I think it would be an amazing idea to merge newer WebExtension APIs in. After all, some add-ons have already ended support for ver.56 as they rely on newer APIs.

Furthermore, I am sure @MrAlex94 wouldn't mind if somebody could assist him with these issues by creating related commits:

#538

I hope you are still interested, I have only found his ticket recently.

[grahamperrin]

Handy points of reference, thanks to @jbeich

• 57 https://developer.mozilla.org/Firefox/Releases/57#New_APIs
• 58 https://developer.mozilla.org/Firefox/Releases/58#New_APIs
• 59 https://developer.mozilla.org/Firefox/Releases/59#New_APIs
• 60 https://developer.mozilla.org/Firefox/Releases/60#New_APIs

[grahamperrin]

if there's any merge strategy

Whilst I'm not aware of an explicit strategy …

… defocusing from APIs, we do have plenty of recent work that goes towards the stated aim of maintaining (security and bug fixes for) Waterfox Classic. 56.2.14...2019.10-classic-1, various PRs, and so on.

@Happy-Ferret all things considered – with Waterfox Current developing nicely in parallel with maintenance of Waterfox Classic – would you like to close this issue?

Thanks