Latest recent search is added with a little delay on the Recent Searches list
Categories
(Firefox :: Address Bar, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox123 | --- | unaffected |
firefox124 | --- | affected |
firefox125 | --- | affected |
People
(Reporter: phorea, Assigned: daleharvey)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sng])
Attachments
(1 file)
1.07 MB,
image/gif
|
Details |
Notes
- Please see the attached gif for more details.
Found in
- Firefox 124.0b3;
Affected versions
- Firefox 124.0b3; Nightly 125.0a1
Tested platforms
- Windows 11;
- macOS 12;
Affected platforms
- Windows 11;
- macOS 12;
Unaffected platforms
- N/A;
Preconditions
- browser.urlbar.suggest.recentsearches = true
- browser.urlbar.suggest.trending =true
- browser.urlbar.trending.featureGate = true
- browser.urlbar.recentsearches.featureGate = true
- browser.urlbar.trending.requireSearchMode = false
- VPN connected to US/CA.
- Google set as default search engine
Steps to reproduce
- Launch Firefox with the profile from preconditions.
- Perform a few searches using the default search engine.
- Open a new tab after each search and check that the most recent search is added to the
Recent Searches
list
Expected result
- The latest search item is added instantly to the
Recent Searches
list
Actual result
- There is a noticeable (short) delay when opening the address bar after new searches were made.
Regression range
- Will look for one ASAP.
Reporter | ||
Updated•1 year ago
|
Reporter | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Hey Marco, I was wondering what your opinion on this is, from my understanding of the code there isnt anything we can do quicker, we are pretty much passing Formhistory.search
results straight back to the ProvidersManager, I can see that trending have the same flash as the first set is cached then gets repopulated. The FormHistory.search queries arent taking a long time here, usually 1 or 2 ms, I have 14 at the longest which will miss the first batch.
I think this is working as expected, but I would like to hear since you are way more familiar with the urlbar and query performance relating things.
Comment 3•1 year ago
|
||
There may be some space for reducing flicker (that likely consists in further delays), but the roundtrip to disk and back is not easily bypassable without hacks, like some sort of memory cache, that I don't think it's worth the benefit. The use-case of making a search and having an instant need to remake it seems not particularly common. Imo it's a wontfix for the cost/benefit ratio.
Surely it'd be nice to have a smoother rendering of results, but we don't have a clear solution there yet.
Assignee | ||
Comment 4•1 year ago
|
||
Yeh that is what I was thinking cheers, closing as wontfix
Description
•