Open
Bug 716058
Opened 13 years ago
Updated 2 years ago
[Faceted search] Refining search terms *with autocomplete* from global search box above faceted search results should not open a new tab (re-use same / existing tab, as for typed modifications)
Categories
(Thunderbird :: Search, defect)
Thunderbird
Search
Tracking
(Not tracked)
NEW
People
(Reporter: thomas8, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: ux-consistency, ux-control, ux-minimalism)
STR
1) Search all messages (global search) for "Blake"
2) From the global search box at the top of faceted search results,
2a) refine search terms with typing, e.g. add " Winton" to search "Blake Winton"
2b) refine search terms with autocomplete, e.g. delete "n" of Winton to trigger autocomplete, then choose "Blake Winton blake@mailserver.xxx" from dropdown list
Actual result
2a) results for search terms refined *with typing* will be shown in *same* tab
2b) results for search terms refined *with autocomplete* will be shown in *new tab*
Expected result
2b) This bug: regardless of the method used for refining search terms (typing vs. autocomplete), search results should always show in the same tab.
- ux-consistency: no plausible reason for this inconsistent behaviour
- ux-minimalism: we should not complicate the UX by opening new tabs sometimes, and sometimes not
- ux-control: unexpected, unexplainable behaviour makes user feel not in control of the software
New bug needed: Holding Ctrl for global search should render search results in a new tab.
Reporter | ||
Updated•13 years ago
|
Reporter | ||
Comment 1•13 years ago
|
||
With tabs on top scheduled to land with tb11, we will be unable to refine existing searches from faceted search results or even start a new one unless bug 717261, or bug 719008, or both, get fixed. For the purpose of refining, 719008 is the more appropriate UI (and there could be some other interesting buttons on that toolbar), which imo does not preclude the need for or appropriateness of bug 717261.
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Thomas D. from comment #1)
> With tabs on top scheduled to land with tb11, we will be unable to refine
Tabs on top, that's bug 644169.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•