Bug 1809235 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

We'll need to add the new permission, named `"webRequestFilterResponse"`:
- for MV3 extension: the new permission is required to be allowed to successfully call `webRequest.filterResponseData` (if the permission is not granted the method is going to throw an explicit error for the missing permission)
- for MV2 extensions: the new permission is not required (but in Firefox versions where the attached patches will be landed, it would still be recognized as a valid permission if requested by an MV2 extensions)

We should update the following MDN pages:
- https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions
- https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/filterResponseData

and the following MDN's browser-compat-data json files:
- https://github.com/mdn/browser-compat-data/blob/main/webextensions/manifest/permissions.json
- https://github.com/mdn/browser-compat-data/blob/main/webextensions/manifest/optional_permissions.json

-----

Given that we are going to add `"webRequestFilterResponse"` permission to cover the dev-docs-needed keyword on this bug, we should also add `"webRequestFilterResponse.serviceWorkerScript"`, which was introduced in Bug 1636629 and it does also apply to MV2 extensions:

- `"webRequestFilterResponse.serviceWorkerScript"` is a permission required to allow an extension (both MV2 or MV3) to use `webRequest.filterResponseData` API method on intercepted requests originated for service worker scripts (e.g. the main service worker script or scripts imported from the service workers using `importScripts`)
- once this bug will be landed, an MV3 extension that wants to use `webRequest.filterResponseData` will have to request both `"webRequestFilterResponse"`  and `"webRequestFilterResponse.serviceWorkerScript"`

The MDN pages and MDN's browser-compat-data JSON files to be updated are the same listed above in this comment.
We'll need to add the new permission, named `"webRequestFilterResponse"`:
- for MV3 extension: the new permission is required to be allowed to successfully call `webRequest.filterResponseData` (if the permission is not granted the method is going to throw an explicit error for the missing permission)
- for MV2 extensions: the new permission is not required (but in Firefox versions where the attached patches will be landed, it would still be recognized as a valid permission if requested by an MV2 extensions)

We should update the following MDN pages:
- https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions
- https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/filterResponseData

and the following MDN's browser-compat-data json files:
- https://github.com/mdn/browser-compat-data/blob/main/webextensions/manifest/permissions.json
- https://github.com/mdn/browser-compat-data/blob/main/webextensions/manifest/optional_permissions.json

-----

Given that we are going to add `"webRequestFilterResponse"` permission to cover the dev-docs-needed keyword on this bug, we should also add `"webRequestFilterResponse.serviceWorkerScript"`, which was introduced in Bug 1636629 and it does also apply to MV2 extensions:

- `"webRequestFilterResponse.serviceWorkerScript"` is a permission required to allow an extension (both MV2 or MV3) to use `webRequest.filterResponseData` API method on intercepted requests originated for service worker scripts (e.g. the main service worker script or scripts imported from the service workers using `importScripts`)
- once this bug will be landed, an MV3 extension that wants to use `webRequest.filterResponseData` on intercepted requests originated for service worker scripts will have to request both `"webRequestFilterResponse"`  and `"webRequestFilterResponse.serviceWorkerScript"`

The MDN pages and MDN's browser-compat-data JSON files to be updated are the same listed above in this comment.

Back to Bug 1809235 Comment 3