Open
Bug 1712338
Opened 4 years ago
Updated 3 years ago
The history results flicker while typing a keyword used for multiple searches on different websites
Categories
(Firefox :: Address Bar, enhancement, P3)
Tracking
()
NEW
People
(Reporter: cmuntean, Unassigned)
References
Details
(Keywords: perf:frontend, Whiteboard: [snt-scrubbed][search-performance])
Attachments
(1 file)
|
3.63 MB,
image/gif
|
Details |
[Affected versions]:
- Firefox Nightly 90.0a1;
- Firefox Beta 89.0b15;
- Firefox Release 88.0.1;
[Affected Platforms]:
- Windows 10 x64;
- macOS 10.15.7;
- Linux Mint 20 x64;
[Steps to reproduce]:
- Open the Firefox browser.
- Type "cars" in the address bar and press enter.
- Open a new tab, type "cars" in the address bar, select the "Amazon" one-off search and press Enter.
- Repeat Step 3 using the "Bing", "DuckDuckGo" and "Wikipedia" one-off searches.
- Close the opened tabs.
- Type "car" in the address bar and press the Space key multiple times.
- Observe the history displayed while performing Step 6.
[Expected result]:
- There is no flicker while typing the keyword.
[Actual result]:
- The history results flicker while typing the keyword.
[Notes]:
- Attached a screen recording of the issue.
Comment 1•4 years ago
|
||
This is due to how we update the view in chunks as new results are fetched. IMO there's definitely room for improvement with bugs like this, and it would be good for us to spend time on them. We have some similar recent flicker-related bugs on file and this might be a dupe, but AFAICT the flicker here isn't due to replacing a SERP because it dupes form history or something specific like that, it's just due to how the view update logic replaces results more generally.
I made a screen recording of the gif and I'll try to post screenshots later.
Updated•3 years ago
|
Severity: S4 → N/A
Type: defect → enhancement
Keywords: papercut → perf:frontend
Whiteboard: [snt-scrubbed][search-performance]
Updated•3 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SNT-428
You need to log in
before you can comment on or make changes to this bug.
Description
•