1283639 - (webextensions-proxy-api) [tracking] Proxy API support for WebExtensions

Status: NEW

(WebExtensions :: Request Handling, defect, P3)

Description

[Johann Hofmann [:johannh]]

https://developer.chrome.com/extensions/proxy

Properties
* settings (which is a ChromeSetting object https://developer.chrome.com/extensions/types#ChromeSetting)

Events
* onProxyError

Comment 1

[Andy McKay]

Moving to approved because Matt is working on this API, so it's happened.

Comment 2

[Stealthy Team]

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?

Comment 3

[Shane Caraveo (:mixedpuppy)]

Given our proxy api is completely different from chrome, I think these two blockers are not valid.

Comment 4

[netroby]

Hello, Any update for this issue?
firefox proxy switch ugly.
Like chrome proxy switch, many extension can do that.
But for firefox, fewer addons can do it rightly.
Most of addons was not working anymore.
very bad user experience.

Comment 5

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

This is a meta bug for various issues regarding proxy support, of which most issues have been resolved. If you have more specific suggestions on how the Firefox proxy API can be improved, please post at https://mail.mozilla.org/listinfo/dev-addons

Comment 6

[netroby]

I am not plugin author. but i found most proxy manage addons of firefox not working at all (both them do not support quick switch on/off pac.js)
It just because firefox change the abi.
I have no idea how to improve the addon developer experience.
but firefox you should really care about it .
now, i have to use chrome as primary browser.
It help me turn on/off proxy easier.(many addons works like a boss)