From c62f230cfc1041c8ec62dfeb98e2e18132fae442 Mon Sep 17 00:00:00 2001 From: Richard Bloor Date: Fri, 22 May 2026 11:39:24 +1200 Subject: [PATCH] Remove statement that `proxy` isn't available on Chrome name space --- files/en-us/mozilla/add-ons/webextensions/api/proxy/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/mozilla/add-ons/webextensions/api/proxy/index.md b/files/en-us/mozilla/add-ons/webextensions/api/proxy/index.md index 6f34d1aaba6b22d..51dd827e71f6bbc 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/proxy/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/proxy/index.md @@ -13,7 +13,7 @@ The advantage of the {{WebExtAPIRef("proxy.onRequest")}} approach is that the co Apart from this API, extensions can also use the [`browserSettings.proxyConfig`](/en-US/docs/Mozilla/Add-ons/WebExtensions/API/proxy/settings) property to configure global proxy settings. > [!NOTE] -> Chrome, Edge, and Opera have [an extension API also called "proxy"](https://developer.chrome.com/docs/extensions/reference/api/proxy) which is functionally similar to this API, in that extensions can use it to implement a proxying policy. However, the design of the Chrome API is completely different to this API. Because this API is incompatible with the Chrome `proxy` API, this API is only available through the `browser` namespace. +> Chrome, Edge, and Opera have [an extension API also called "proxy"](https://developer.chrome.com/docs/extensions/reference/api/proxy) which is functionally similar to this API, in that extensions can use it to implement a proxying policy. However, the design of the Chrome API is completely different to this API. To use this API you need to have the "proxy" [permission](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions). Also, where you want to intercept requests, you also need [host permission](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions#host_permissions) for the URLs of intercepted requests.