1825764 - Google Trending Predictions are not displayed in PBM upon first interaction with urlbar

Status: RESOLVED DUPLICATE of bug 1830474

(Firefox :: Address Bar, defect)

Description

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

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

1. Launch FF.
2. Open a PBM window.
3. Click on the urlbar. (or select the Google shortcut)

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

[Dale Harvey (:daleharvey)]

First issue is that trending shouldnt show in pbm unless browser.search.suggest.enabled.private is set to true, is that required for this bug?

With that set to true I am seeing trending suggestions reliably, is this down to the same issue as the other 2 with us hitting intermittent timeouts?

Comment 2

[Petruta Horea [:phorea]]

(In reply to Dale Harvey (:daleharvey) from comment #1)

First issue is that trending shouldnt show in pbm unless browser.search.suggest.enabled.private is set to true, is that required for this bug?
Yes, we enable suggestions in PBM for this scenario, this step is missing from comment#0.

With that set to true I am seeing trending suggestions reliably, is this down to the same issue as the other 2 with us hitting intermittent timeouts?
This issue only happens the first time we open a Private Window, so we suspect it's related with the intermittent timeout issue.