https://developer.chrome.com/extensions/proxy Properties * settings (which is a ChromeSetting object https://developer.chrome.com/extensions/types#ChromeSetting) Events * onProxyError
Assignee: mwein → nobody
Whiteboard: [proxy] → [proxy][design-decision-needed]
Whiteboard: [proxy][design-decision-needed] → [proxy][design-decision-needed] triaged
Summary: Implement chrome.proxy → Proxy API support for WebExtensions
Summary: Proxy API support for WebExtensions → [tracking] Proxy API support for WebExtensions
Component: WebExtensions → WebExtensions: Request Handling
Moving to approved because Matt is working on this API, so it's happened.
Whiteboard: [proxy][design-decision-needed] triaged → [proxy][design-decision-approved] triaged
Any chances to change this: "this API only supports the PAC file approach. Because this API is incompatible with the Chrome proxy API"? What is so terrible about define explicit proxying rules that is worth to break the Chrome compatibility?
Given our proxy api is completely different from chrome, I think these two blockers are not valid.
You need to log in before you can comment on or make changes to this bug.