Rob Wu

The warning in Chrome is not fatal, there is a feature request at https://issues.chromium.org/issues/40196501 to stop emitting errors for known keys.

Could you explain the relation between your comment and the task I described here?

One of the differences between web-ext 8.2.0 and 8.3.0 is the removal of the node-fetch dependency in https://github.com/mozilla/web-ext/pull/3217 When I reproduce the issue locally, I can see that the submitted...

> At first glance, the problem is that our "remove cookies" DNR rule for `mail.google.com`, despite being scoped to `domainType: 'thirdParty'`, is applied to `mail.google.com` requests in a new, `mail.google.com`...

Could you share the verbose logs of `web-ext` ? (add `-v` to the command line). And what proxy application and OS are you using?

Thanks for looking into this @fregante . I'm closing this PR because rather than updating the dependency, we decided to drop the dependency altogether in https://github.com/mozilla/addons-linter/pull/5520, because the feature that...

We have a stub for MDN documentation, which we should link that from the dedicated message: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/optional_permissions#optional-only_permissions

The current warning is `Invalid permissions "${permName}"`, associated with the `permissions` manifest key. This message is confusing. It would be nice if the message is more specific, e.g. `Permission "${permName}"...

> Maybe @Rob--W could help. I know that's the Firefox team but I know Rob has looked into the timing of Chromium feature freezes and browser version releases a lot...