Closed Bug 1459177 Opened 7 years ago Closed 7 years ago

Mouse cursor should only add highlighted line on autocompletion dropdown after being moved (like Chrome)

Categories

(Firefox :: Address Bar, defect)

61 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1357533
Tracking Status
firefox61 --- affected

People

(Reporter: nachtigall, Unassigned)

Details

Attachments

(1 file)

Attached image awesomebar-line-focus-ff-vs-chrome.gif (deleted) —
STR: 1. Have the mouse somewhere below the awesomebar but still where the autocompletion popup will end up 2. Type in something that will open suggestions (e.g. from browsing history 3. Now use arrow down/up to navigate through suggestions AR: There are two focus highlights: One for the first item, one for where the mouse is. The first is more prominent, but still I very often end up looking at the one where the mouse is. I guess because it is usually more in the middle and hence more eye catching. So very often I use down/up arrows and think I am at the line where the mouse points to, but instead I am at the first highlighted line. ER: One solution would be to do it the same way that chrome does here. You're "silten" not-yet-move mouse does not cause a trigger unless you really move it. See attached screened GIF comparing the Firefox vs. Chrome behaviour here. This is currently my number one UX annoyance using Firefox, that is, I regularly hit wrong pages because I move the first focussed line when I think I am on the mouse-focused line. And then I go to the wrong sites accidentically. Not sure this is caused by a recent change (I am on Nightly 61) because this has become a real annoyance in recent weeks. (or I have just become more sensitive to the autocompletion ;)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: