Luca Greco

@SeburoSUMO I'm currently unable to reproduce this using the snap package installed on Ubuntu 20.04.2 (web-ext was installed globally just fine and the core-js message was printed on the console....

@SeburoSUMO I've been able to reproduce it on a vanilla Xubuntu 21.04 system installed in a VM. The issue seems to be due to snap confinement (even if technically this...

@danhumphrey when running a web-ext command by requiring it as a nodejs module, it may be useful to include the `noInput` option explicitly set to `true`, e.g. ```js webext.cmd.run({ noInput:...

@pdehaan I briefly looked into this and the --ignore-files cli option should be excluding the "files that match the list of ignore patterns" from the addons-linter validation results, I'm wondering...

@pdehaan ah, thanks for the additional details, I see now what it is actually happening! (and now I'm wondering how I missed it when I looked at the linting output...

> I think it's ready for review(!) > > Two of the tests I added I just couldn't get working - I marked them `.skip` -ideas welcome! Also now CI...

I took a look to the windows CI job failure, as I mentioned yesterday I was pretty sure to have seen that and fixed it not long ago, and confirmed...

@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...

@wbamberg the options page are running in a different process from the about:addons page and so they can't be reached from the devtools toolbox opened on the about:addons tab, but...

> From your response this seems quite likely to be a Firefox bug, so I'll cross-file it in Bugzilla. yeah, it looks like a Firefox bug, do you mind to...