asamuzaK (Kazz)

In most cases (at least in my case), one latest zip file is enough. Old zip file will never be used. Currently, when building a new zip file you need...

> Out of curiosity: > * Why a max of 4 parts? > * Why no leading zeros? See: * [Manifest - Version - Google Chrome](https://developer.chrome.com/extensions/manifest/version "Manifest - Version -...

See also [1469764 - Can't send to device from a WebExtension panel (and potential other issues)](https://bugzilla.mozilla.org/show_bug.cgi?id=1469764)

See also [1578655 - Follow up 1280347 - Allow extensions to include native (tab) items when using overrideContext](https://bugzilla.mozilla.org/show_bug.cgi?id=1578655)

See also [1417183 - Provide a web extensions API-based way to send pages between devices](https://bugzilla.mozilla.org/show_bug.cgi?id=1417183)

Note that [1417183 - Provide a web extensions API-based way to send pages between devices](https://bugzilla.mozilla.org/show_bug.cgi?id=1417183#c17) is closed as WONTFIX.

Ref [Prototype-polluting function — CodeQL query help documentation](https://codeql.github.com/codeql-query-help/javascript/js-prototype-pollution-utility/)

Ref [Chrome Extensions Manifest V2 support timeline - Chrome Developers](https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/) Ref [Pausing Manifest V2 phase-out changes](https://groups.google.com/a/chromium.org/g/chromium-extensions/c/zQ77HkGmK9E)

For a note: [1811443 - Support type: "module" (event page, not background service worker)](https://bugzilla.mozilla.org/show_bug.cgi?id=1811443)

Ref [Manifest V2 support timeline | Extensions | Chrome for Developers](https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline)