If the search service fails to initialise properly, allow the Firefox to be used in a limited mode
Categories
(Firefox :: Search, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: standard8, Assigned: mcheang)
References
Details
Attachments
(4 files)
If the search service fails to initialise, we should still allow Firefox to be used.
At the moment, if it breaks, then the address bar can't be used. The new tab page also doesn't finish starting properly.
Although this should be an extremely rare scenario, that's hopefully only limited to test builds, I think it is worth making sure that at least some of the browser is usable, so that users can still try and find information without needing to resort to switching browsers.
This will probably need some investigation as to what exactly breaks, could we return a dummy engine or something.
It might also be interesting to add telemetry to see if this is happening in the wild at all.
Reporter | ||
Comment 1•4 years ago
|
||
Note to self: Also need to think about other parts of the browser that may be broken, e.g. the context menu.
Assignee | ||
Comment 2•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Comment 5•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4716950128c5
https://hg.mozilla.org/mozilla-central/rev/034192694257
Assignee | ||
Comment 6•1 year ago
|
||
Before my patch:
When the search service failed to init on start-up the address bar cannot use search engines. The address bar is in a state where the user cannot search their history and bookmarks. No result panel will be shown.
See the "before-fix" video.
After my patch:
When search service init fails address still use search engines. But the result panel will show when the user types, the user will see their history and bookmarks results in the result panel. See the "after-fix" video.
Assignee | ||
Comment 7•1 year ago
|
||
Assignee | ||
Comment 8•1 year ago
|
||
Comment 9•1 year ago
|
||
The issue is verified as fixed using the provided trybuilds from treehearder on Windows 10, macOS and Ubuntu. Address bar is no longer stuck and searching in bookmars works correctly when search init fails (like in the provided video).
Assignee | ||
Updated•1 year ago
|
Description
•