Handle proxy.settings properly in private browsing

NEW
Unassigned

Status

enhancement
P2
normal
5 months ago
3 months ago

People

(Reporter: mixedpuppy, Unassigned)

Tracking

(Depends on 1 bug, Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

5 months ago

If a user has a proxy extension running that uses proxy.settings upgrades to a version with incognito preffed on, what do we do with the setting? We can remove it, leave it, or give the extension pbm permission.

Reporter

Updated

5 months ago
Priority: -- → P1
Reporter

Updated

4 months ago
Flags: needinfo?(mconca)

The bug becomes moot if we allow extensions that are already installed to be granted PBM permission during the upgrade.

Flags: needinfo?(mconca)
Reporter

Comment 2

4 months ago

(In reply to Mike Conca [:mconca] from comment #1)

The bug becomes moot if we allow extensions that are already installed to be granted PBM permission during the upgrade.

Only for those extensions, not for new profiles, new installs, etc.

For now, the extension will require private permission to use this setting. Filing a bug on netwerk to see about getting support here.

Priority: P1 → P3
Reporter

Updated

4 months ago
Depends on: 1527749

Changing the title a bit. The use case is to make an extension that uses proxy.settings work separately in normal and private windows (similar to what was done for proxy.register and proxy.onRequest).

Summary: Handle PAC settings on upgrade to incognito → Handle proxy.settings properly in private browsing

Upping this to P1 to try and get the user experience unbroken when a user needs to set an extension to run in private browsing just to get it working at all (this is currently invisible to the user). Updating bug 1527749 to try and increase that priority as well.

Priority: P3 → P1
Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.