Update UrlbarView's selection model to support selection within "tip" results
Categories
(Firefox :: Address Bar, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: bugzilla, Assigned: bugzilla)
References
Details
Attachments
(2 files)
The user needs to be able to navigate to both the main button and and help link. UrlbarView.selectBy
is one major method that will need updating.
Assignee | ||
Comment 1•6 years ago
|
||
Verdi, should the intervention button and help icon have different states for hover vs. selected? Right now we highlight autocomplete rows grey if they're hovered and blue if they're selected. Currently the UX spec for Interventions only specifies the state for selected.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
(In reply to Harry Twyford [:harry] from comment #1)
Verdi, should the intervention button and help icon have different states for hover vs. selected? Right now we highlight autocomplete rows grey if they're hovered and blue if they're selected. Currently the UX spec for Interventions only specifies the state for selected.
The row itself shouldn't have a hover state. The button should use the "Primary" button hover state and the help icon should use the "Ghost" button hove state.
Assignee | ||
Comment 4•6 years ago
|
||
Afaik, we previously discussed the buttons taking on the primary hover state when they were selected with the keyboard. Should they have a different appearance when selected with the keyboard?
Updated•6 years ago
|
Comment 5•6 years ago
|
||
(In reply to Harry Twyford [:harry] from comment #4)
Afaik, we previously discussed the buttons taking on the primary hover state when they were selected with the keyboard. Should they have a different appearance when selected with the keyboard?
Sorry I wasn't more clear. I updated Invision and attached a mock of how this button should work.
Comment 7•6 years ago
|
||
bugherder |
Description
•