You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
After you type something and erase it, the search suggestions don’t disappear.
Expected behavior
Suggestions should disappear along with the characters you’ve entered.
Actual behavior
Suggestions do not disappear, and are still there above the other suggestions/history/etc
Device information
Android device: Pixel 3, android 10
Fenix version: Nightly
What is the user problem or growth opportunity you want to see solved?
People expects the address bar to be fluid and responsive. This means that suggestions (search keywords, history, bookmarks, etc.) should be fetched as quickly as possible. And whenever any changes happen (e.g. add new letters, remove all letters.), suggestions should respond as quickly as possible.
data-sync-user
changed the title
FNX3-13523 ⁃ [Bug] Remove search suggestions after erasing
FNX-13655 ⁃ [Bug] Remove search suggestions after erasing
Aug 11, 2020
data-sync-user
changed the title
FNX-13655 ⁃ [Bug] Remove search suggestions after erasing
FNX2-15331 ⁃ [Bug] Remove search suggestions after erasing
Aug 11, 2020
Steps to reproduce
Expected behavior
Suggestions should disappear along with the characters you’ve entered.
Actual behavior
Suggestions do not disappear, and are still there above the other suggestions/history/etc
Device information
What is the user problem or growth opportunity you want to see solved?
People expects the address bar to be fluid and responsive. This means that suggestions (search keywords, history, bookmarks, etc.) should be fetched as quickly as possible. And whenever any changes happen (e.g. add new letters, remove all letters.), suggestions should respond as quickly as possible.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: