Are there any concrete plans to start interoperating or incorporating web-ext with Google Chrome, Opera, and other platforms?

[tommai78101]

trafficstars

I understand the primary focus for web-ext is to improve and build upon its features for Mozilla Firefox.

As noted here:

By creating a new tool that focuses on the [emerging] web extension standard, we have a better chance of interoperating with other platforms, such as Google Chrome or Opera. It would be hard to do that while preserving compatibility in jpm.

I would like to know if there are any concrete plans to start interoperating with other platforms? Or it still needs to take a while before the main focus can be shifted towards this?

Thanks.

[rpl]

@tommai78101 yes, we have plan to add support for Chrome and Opera to web-ext run.

Part of the refactoring have been already landed, with some additional tweaks that are going to be part of the support for Firefox for Android (#868), which uses the same underlying abstraction that we are going to be used to add the additional chrome/opera "extension runners".

[tommai78101]

Thank you. Reason I'm asking is because the quoted part isn't clear if there are plans to add Chrome and Opera support, and it's more like "this tool has potential to do XYZ." Is it possible to edit a little bit to confirm that, yes, we do have future plans for this?

Or maybe I can do a tiny bit of PR for the Readme section ...?

[tgvdinesh]

Has this tool started supporting chrome?

[Pomax]

I guess I have the same question still =)

Is there a --target=[chrome|edge|firefox] on the near horizon that will not try to solve unsolvable differences, but automatically does browser. => chrome. substitutions, manifest changes, etc., or even a --target=all that simply builds a "universal" web extension (with shims that figure out the namespace, a manifest that matches both formats, etc)?

[kumar303]

Is there a --target=[chrome|edge|firefox] on the near horizon

You can track https://github.com/mozilla/web-ext/issues/809 for Chrome support in web-ext

...automatically does browser. => chrome. substitutions...

This is probably out of scope for web-ext. I'd suggest using https://github.com/mozilla/webextension-polyfill which is well supported.

...automatically does ...manifest changes...

That one is a bit tricky. I'd suggest using something like webpack (example) and configuring multiple targets for your output. Maybe there is a better strategy.

[matanox]

Seems to work with latest chrome releases ... at least for me.