Closed
Bug 1825761
Opened 3 years ago
Closed 3 years ago
Google Trending Predictions are not displayed after a browser restart
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1830474
| Tracking | Status | |
|---|---|---|
| firefox113 | --- | affected |
People
(Reporter: vlucaci, Unassigned)
References
(Blocks 2 open bugs)
Details
Found in
- 113.0a1(20230330214245)
Affected versions
- 113.0a1(20230330214245)
Tested platforms
- Affected platforms: macOS 13, Ubuntu 22, Windows 10
Preconditions
- Have VPN connected to US.
- Google as default search engine.
- browser.search.region set to US
- browser.urlbar.trending.featureGate set to true
- browser.urlbar.trending.requireSearchMode
- browser.urlbar.update2.emptySearchBehavior set to 1 or 2 (default being 0)
Steps to reproduce
- Launch FF.
- Open a new tab.
- Restart the browser. (either from about:profiles or with command+Shift+J -> option+command+r)
Expected result
- Google Trending Predictions entries are displayed without any issues.
Actual result
- Google Trending Predictions entries are not displayed.
Other notes
- The workaround is to dismiss the urlbar (click anywhere outside it) then re-selecting it.
- The following error is displayed inside the browser console :
SearchSuggestionController found an unexpected string value: HTTP request timeout SearchSuggestionController.sys.mjs:634:17 - Screencast of the issue
Comment 1•3 years ago
|
||
Both this and the linked issues seem to be that trending suggestions will intermittently fail due to timing out, the timeout for urlbar interactions is quite short and trending suggestions have been seen to be slower than the main suggestions api, I put browser.search.suggest.timeout = 5000
in my machrc at some point to avoid the issue but it is something we should check in again with google about.
Can we check that these are timeouts and close the linked bug as a dupe. I cant see any way restarts or pbm would specifically cause intermittent issues like this
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•