Luca Greco

@fregante yeah, when I added support for Chrome I evaluate a bunch of options, using what the management API provides to non privileged extension was a reasonable way to get...

> I don’t think a browser restart is necessary, I usually just have to click reload in the Extensions page. I think runtime.reload() from the extension itself does the same....

The "notification" I had in mind would be meant specifically to make the developer aware that the extension manifest has been update but chrome will not be see the update...

We have discussed about this in our triage meeting today and we are willing to review and merge changes that may make this use case possible and easier. To make...

For reasons unrelated to this issue I've been using windows for a bit and I took that opportunity to look for reasonable implementation strategies for the issues we already know...

> > In Firefox, we have decided to support Event Pages in MV3, and our developer preview will not include Service Workers (we’re continuing to work on supporting these for...

@darkred thanks for reporting this to us, the additional details looks pretty useful to look into it. @Rob--W would you mind to take a look into this? it looks something...

@icl7126 Let me ask some additional questions to get a better picture of the issue and how to reproduce it: - is the extension installed from AMO the same one...

Thanks @icl7126 the additional details were very helpful. Based on some additional logs collected by executing web-ext run with the addition of -p "extensions.logging.enabled=true", it seems that the extension installed...

I suspected that the config was being overridden by the CLI parameters, and running web-ext in verbose mode does confirm that: ``` ... [program.js][info] Applying config file: ./web-ext-config.js [config.js][debug] Loading...