Closed
Bug 1534652
Opened 5 years ago
Closed 5 years ago
Google search engine gets removed after deleting the foo.js default preferences file
Categories
(Firefox :: Search, defect)
Firefox
Search
Tracking
()
VERIFIED
FIXED
Firefox 68
People
(Reporter: atrif, Assigned: mkaply)
Details
Attachments
(3 files)
Affected versions
- Firefox 66.0 (20190311211048)
- Firefox 67.0a1 (20190312095443)
Affected platforms
- macOS 10.13.6
- Windows 10 x64
- Ubuntu 18.04 x64
Prerequisites
- Place the attached foo.js file inside the firefox/defaults/pref folder .
Steps to reproduce
- Open Firefox with a clean profile.
- Perform a random search in URL bar.
- Close Firefox.
- Go to “firefox/defaults/pref” and delete “foo.js”.
- Open Firefox with same profile used at step 1.
- Inspect search engines.
Expected result
- Google search engine is available.
Actual result
- Google search engine is no longer displayed/available.
Regression range
- I will get back with a regression range ASAP.
Additional Notes
- On 66.0 the issue is intermittent.
- Attached a screen recording with the issue.
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Updated•5 years ago
|
Has Regression Range: --- → no
Has STR: --- → yes
Assignee | ||
Comment 2•5 years ago
|
||
Pushed by mozilla@kaply.com: https://hg.mozilla.org/integration/autoland/rev/46fbb035f335 Add try catch whenever querying mozparams. r=adw
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 68
Updated•5 years ago
|
Assignee: nobody → mozilla
Comment 5•5 years ago
|
||
Mike, is that something that would be safe and valuable to uplift or can we let it ride the 68 train? Thanks
Flags: needinfo?(mozilla)
Assignee | ||
Comment 6•5 years ago
|
||
The shield study that was going to use this is using a different mechanism, so this can ride the trains.
The scenario that happened was test only.
Flags: needinfo?(mozilla)
Updated•5 years ago
|
Reporter | ||
Comment 7•5 years ago
|
||
Since the code no longer exists on latest versions, I've tested this using Nightly 68.0a1 (20190410100020) and it no longer reproduces. We can safely close this issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•