Closed
Bug 1129554
Opened 10 years ago
Closed 10 years ago
Wrong default engine set under profile creation with device using outside US VPN
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: aaronmt, Unassigned)
References
Details
As anticipated, currently with a device using an outside VPN (Britain), the wrong default engine is set on profile creation. Yahoo.
Install VPN Master
Set VPN to London (UK) and connect
Launch Firefox
See Yahoo as default, expected to see Google
Comment 1•10 years ago
|
||
Sounds weird. You say that Fennec works fine (CA/CA and shows Google?) when using a non-VPN approach?
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Mark Finkle (:mfinkle) from comment #1)
> Sounds weird. You say that Fennec works fine (CA/CA and shows Google?) when
> using a non-VPN approach?
Yes. What does Kar get on a new Nightly profile?
Comment 3•10 years ago
|
||
by a new nightly profile, I presume you mean I uninstall nightly and re-download & install it.
If that's the case (done), my default is google.
Comment 4•10 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #2)
> (In reply to Mark Finkle (:mfinkle) from comment #1)
> > Sounds weird. You say that Fennec works fine (CA/CA and shows Google?) when
> > using a non-VPN approach?
>
> Yes. What does Kar get on a new Nightly profile?
(In reply to Karen Rudnitski [:kar] from comment #3)
> by a new nightly profile, I presume you mean I uninstall nightly and
> re-download & install it.
>
> If that's the case (done), my default is google.
Based on this information, I think this bug is working. I don't know why the VPN approach is causing issues, but it's not our priority at the moment. It would be nice to have that working, for the sake of testing though.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•