Package Chrome Extension As Well

[Justin-CB]

Because you use the WebExtensions API, which is more or less standardized across browsers, it makes sense to also package this as a chrome extension. This might require some work, as chrome provides a chrome object, rather than a browser object, but the chrome object supports almost all of the same WebExtension API's.

[rugk]

Sure, any PRs are always appreciated!
See rugk/offline-qr-code#59 for reasoning and information on polyfills etc.

[mrl24730]

Is Chrome supported???

[rugk]

Not yet, but PR's are very welcome though if one wants to try to make it work.

Also see another add-on in development currently, that also tries to support Chome/ium browsers.

[rugk]

Note that Chrome/ium support may be tricky, given not all APIs are supported by Chrome/ium browsers.

[rugk]

...especially as v2.0 uses a new browser setting/API that only Firefox has, for now. So porting the add-on in the current state seems quite impossible.
Only the old mechanic from v1.3 could possibly be ported, but would have to be maintained separately or so, which I'd like to avoid.