Proxy configuration not used in metro

RESOLVED INCOMPLETE

Status

defect
RESOLVED INCOMPLETE
6 years ago
2 years ago

People

(Reporter: motiosnv22, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [defect] p=0)

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release)
Build ID: 20130921004001

Steps to reproduce:

Under the desktop mode, went to options, advanced, network tab, connection, settings, and set my manual proxy


Actual results:

the proxy worked under the desktop; under the metro version, proxy was not used


Expected results:

proxy should have been used for both desktop and metro
Summary: proxy configuration not used in metro → Defect - proxy configuration not used in metro
Whiteboard: [triage] feature=defect c=tbd u=tbd p=0
Tested on 2013-09-30 on latest nightly. It looks like these preferences are not shared between the desktop and metro browser and this might be intended. Requesting information from Asa to confirm.
Flags: needinfo?(asa)
We didn't specify proxy config as a Metro feature. If we share a profile with Desktop, this might just work. If not, it's not implemented and probably won't be for v1.
Flags: needinfo?(asa)
Blocks: metrobacklog
No longer blocks: metrov1backlog
Whiteboard: [triage] feature=defect c=tbd u=tbd p=0 → feature=defect c=tbd u=tbd p=0
candidates for the prefs mirroring module.
Whiteboard: feature=defect c=tbd u=tbd p=0 → [triage] feature=defect c=tbd u=tbd p=0

Comment 4

6 years ago
A quick test with this patch seems to be pulling the proxy settings from Desktop to the Modern UI.
Summary: Defect - proxy configuration not used in metro → Proxy configuration not used in metro
Whiteboard: [triage] feature=defect c=tbd u=tbd p=0 → [defect] p=0
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.