Bug 1283639 (webextensions-proxy-api)

[tracking] Proxy API support for WebExtensions

NEW
Unassigned

Status

defect
P3
normal
3 years ago
7 days ago

People

(Reporter: johannh, Unassigned)

Tracking

(Depends on 4 bugs, {dev-doc-needed, meta})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [proxy][design-decision-approved] triaged)

Reporter

Description

3 years ago
https://developer.chrome.com/extensions/proxy

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

Events
* onProxyError

Updated

3 years ago
Whiteboard: [proxy]
Assignee: nobody → mwein
Depends on: 1285342
Depends on: 1285343
No longer depends on: 1285343
Depends on: 1285349
No longer depends on: 1285349
Depends on: 1285351
Depends on: 1285352
Assignee: mwein → nobody
Whiteboard: [proxy] → [proxy][design-decision-needed]

Updated

3 years ago
Whiteboard: [proxy][design-decision-needed] → [proxy][design-decision-needed] triaged
Summary: Implement chrome.proxy → Proxy API support for WebExtensions
Depends on: 1290600
Depends on: 1293751
Depends on: 1294228
Summary: Proxy API support for WebExtensions → [tracking] Proxy API support for WebExtensions
Depends on: 1294246
No longer depends on: 1294228
Depends on: 1295807
Depends on: 1296081
Component: WebExtensions → WebExtensions: Request Handling
No longer depends on: 1296081
No longer depends on: 1290600
No longer depends on: 1294246
No longer depends on: 1293751
No longer depends on: 1285352
No longer depends on: 1285342, 1285351
Depends on: 1319630
Depends on: 1319631
Depends on: 1319634
Depends on: 1319641
Depends on: 1319642

Comment 1

3 years ago
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

Updated

3 years ago
webextensions: --- → +

Updated

3 years ago
Priority: -- → P1
Depends on: 1337001

Updated

2 years ago
webextensions: + → ---

Updated

2 years ago
No longer blocks: webext-port-hola
Depends on: 1353510
Depends on: 1355198
Depends on: 1359417
Depends on: 1359543
Depends on: 1362798
Depends on: 1368559

Comment 2

2 years ago
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?
Depends on: 1381290
Depends on: 1380313
Depends on: 1381070
Depends on: 1360404
Depends on: 1357635

Updated

2 years ago
Depends on: 1378205
Depends on: 1383426
Depends on: 1382684
Depends on: 1377325

Updated

2 years ago
Depends on: 1388619

Updated

2 years ago
Depends on: 1389718

Updated

2 years ago
Depends on: 1388289

Updated

2 years ago
Assignee: nobody → mixedpuppy
Keywords: meta
Priority: P1 → P3
Depends on: 1215880
Depends on: 1396485

Updated

2 years ago
Depends on: 1397991

Updated

2 years ago
Depends on: 1405975
Depends on: 1409878
Alias: webextensions-proxy-api
Depends on: 1410257
Depends on: 1373640
Depends on: 1443259
Given our proxy api is completely different from chrome, I think these two blockers are not valid.
Depends on: 1457213
No longer depends on: webextensions-startup
Depends on: 1458698

Updated

Last year
Product: Toolkit → WebExtensions
Assignee: mixedpuppy → nobody

Comment 4

8 days ago

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.

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

You need to log in before you can comment on or make changes to this bug.