Port to firefox / manifest@v3

[ixrock]

TODO

• [ ] manifest@v3 content_scripts not injected automatically (only after opening translator's window via toolbar icon), maybe extra chrome.scripting-api required. Otherwise it works automatically only when user allows it manually per domain/site: Right click at XTranslate icon and Select Extension can access site data: Always
• [ ] manifest@v3 doesn't support background.service_worker
• [ ] chrome.runtime.sendMessage and related methods doesn't support Promise<Response>
• [x] chrome.tts doesn't work, could be handled by #58

PREREQUISITES

• Go to about:config system page
• Set extensions.manifestV3.enabled to true
• Set xpinstall.signatures.required to false
• You can now install MV3 extensions from about:debugging system browser page

Availability in firefox extensions store: (manifest@v2) https://addons.mozilla.org/en-GB/firefox/addon/xtranslate-chrome/

[ixrock]

Status: won't be ported while it's not become good browser :)

Problems:

• Shadow-dom api not supported (only with enabled flag in about:config)
• Lacks of chrome extensions api:

1. chrome.storage.sync - not supported (though chrome.storage.local can be used as fallback)
2. chrome.runtime.onConnect(port => ...) - where port.sender.id is id of window(?), instead of extension, but it has anyway (not-documented?) port.sender.extensionId
3. not possible to create custom-scrollbar styles with css-only

and some more minor problems...

[ixrock]

Reopened to investigate new changes since then..

[SergeyTverye]

Reopened to investigate new changes since then..

Installed your extension in Firefox Developer today and everything seems to be working fine. It seems to me that you could upload the extension to the Firefox store. =)

[labi-le]

Is it relevant?

[ixrock]

What is relevant? Yes it's still in long non-priority todo-list if you want know ;) If firefox-extensions store is fully compatible with chome-store apis (like edge-store), then (re)solution for the issue would be quite fast & trivial.