Manifest v3

[samhh]

It looks like this will stop working in Chromium-based browsers in January 2023 as v2 support is dropped.

[paulie-g]

Any chance you could fix this? I haven't looked at the v3 changes in detail in terms of how hard it would be, but the APIs that they're intending to break permanently ought not affect Bukubrow, surely? All Bukubrow does is grab the page url and title, that should still be available in some form. Or are they killing the native host interface?

[samhh]

The background page might need some attention as the APIs look to have changed a bit there.

I haven't used the extension for a while and I've got a lot of offline stuff going on so I'm not sure I'll get around to looking at this by then. PRs are welcome.

[samhh]

v2 phase out delayed: https://groups.google.com/a/chromium.org/g/chromium-extensions/c/zQ77HkGmK9E

[LeXofLeviafan]

It appears that Firefox added support for V3 recently.

The background page might need some attention as the APIs look to have changed a bit there.

The background pages/scripts are getting replaced with non-persistent service workers… Problem is, service_worker is apparently not supported by Firefox (according to dev blog they're using "event pages" instead, with intention of adding service worker support eventually… I wonder if it will be possible to use the same script/manifest in both Chrome & Firefox 🤔)

[LeXofLeviafan]

I wonder if it will be possible to use the same script/manifest in both Chrome & Firefox

…Alright, no, it's not possible: Chrome rejects V3 extensions with background.scripts or background.persistent in their manifest (the latter isn't allowed by Firefox either, along with background.service_worker). You'll need separate manifest files for Chrome and Firefox.

Other changes to take note of:

• browser_action in manifest & browserAction in the code need to be renamed to action
• similarly, applications in manifest need to be renamed to browser_specific_settings
• tabs.executeScript gets replaced by a much more restricted scripting.executeScript (so much so that it's likely going to limit bookmarklets support severely)