Firefox address bar pop-out has a noticeable delay in Firefox 117
Categories
(Firefox :: Address Bar, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox118 | --- | wontfix |
firefox119 | --- | wontfix |
firefox120 | --- | wontfix |
firefox121 | --- | fixed |
People
(Reporter: omeremin29, Assigned: daleharvey)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [sng-scrubbed][search-performance])
Attachments
(2 files, 1 obsolete file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0
Steps to reproduce:
- Open Firefox 117.
- Type quickly in the adress bar.
Actual results:
The address bar pop-out (auto-suggestions or dropdown) is delayed, lagging behind the typing speed. This bug is specific to Firefox 117 and does not occur in older versions of Firefox.
Expected results:
The address bar pop-out should keep up with the typing speed of the user.
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•1 year ago
|
||
I think this may just be a consequence of us giving heuristic results a bit more time to reply. It should not have an effect on the final outcome if you press Enter, it's basically just a visual thing.
Apart from the visual delay do you notice misbejaviors, like visiting truncated search strings or such?
Updated•1 year ago
|
Updated•1 year ago
|
(In reply to Marco Bonardo [:mak] from comment #2)
I think this may just be a consequence of us giving heuristic results a bit more time to reply. It should not have an effect on the final outcome if you press Enter, it's basically just a visual thing.
Apart from the visual delay do you notice misbejaviors, like visiting truncated search strings or such?
It seems to be just a visual delay.
Comment 4•1 year ago
|
||
I see some possibilities here:
- we add a new notification to the controller that will update the view heuristic on input. This would probably save some resources, though the view must be able to update in-place the various heuristic result types
- maybe we just move the heuristic waiting to the event bufferer and revert to the 16ms timer, that moves us back to the previous update system, the view may flicker a bit more while results arrive, I don't know if that may have other consequences.
While I'm not actively working on this, I can attach a WIP patch with an idea to implement the latter, as inspiration. It requires a lot more testing though.
Comment 5•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Set release status flags based on info from the regressing bug 1816572
Updated•1 year ago
|
Comment 7•1 year ago
|
||
:daleharvey we are in the final week of beta for F119. Do we expect anything for this for Fx119?
Assignee | ||
Comment 8•1 year ago
|
||
Hi, I am working on a patch at the moment but I cant say that it will be done for this week, its also not a particularly simple patch so it may not be one we want to rush in
Updated•1 year ago
|
Comment 9•11 months ago
|
||
Set release status flags based on info from the regressing bug 1816572
Assignee | ||
Comment 10•11 months ago
|
||
Updated•11 months ago
|
Updated•11 months ago
|
Updated•11 months ago
|
Comment 11•11 months ago
|
||
Comment 12•11 months ago
|
||
bugherder |
Description
•