Closed Bug 959574 Opened 6 years ago Closed 6 years ago
Create design spec for Search Prompt in awesomebar results
UX must decide on placement and heuristics around when to show a row in awesomebar results that makes explicit how to search the default search provider.
Status: NEW → ASSIGNED
Whiteboard: [search] [ux] p=5 → [search] [ux] p=2 s=it-30c-29a-28b.3
Whiteboard: [search] [ux] p=2 s=it-30c-29a-28b.3 → [search] [ux] p=2 s=it-30c-29a-28b.3 [qa-]
WIP prototype: http://phlsa.github.io/ff-search-prompt
The prototype is now finished: http://phlsa.github.io/ff-search-prompt Here's a few things to notice: - The list entry that prompts to search uses a different layout (one line). That helps to set it apart from the rest of the list. - That entry is automatically selected once you start typing into the URL bar. - Once the text in the URL bar has URL formatting, the autoselected entry changes as well. - We definitely need better heuristics for when a string is a URL and when its a search term. »localhost« for example should be treated as a URL while »node.js« ideally shouldn't. Feel free to ping me if anything is unclear!
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
No longer blocks: fxdesktopbacklog
You need to log in before you can comment on or make changes to this bug.