Closed
Bug 714340
Opened 14 years ago
Closed 2 years ago
hide the words "quick filter" from the quick filter bar when in icon mode
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: asa, Unassigned)
Details
Attachments
(1 file)
74.30 KB,
image/jpeg
|
bwinton
:
ui-review+
|
Details |
The quick filter bar moves to icon mode when there's not enough horizontal space but for the vertical view, it's not enough space. The search box gets cut off too much. To fix this, we should simply hide the "quick filter" label when in icon mode (or when in both modes, I don't think it's particularly useful.)
Comment 1•14 years ago
|
||
Comment on attachment 585019 [details]
a mock up of what it could look like. see, so much better.
Yeah, that makes way more sense. Removing some of the padding between the icons and the text box would be another good idea in this low-width environment.
Attachment #585019 -
Flags: ui-review+
Reporter | ||
Comment 2•14 years ago
|
||
We apparently can't remove that padding. It's the space where the message count appears when you do a search. I'd like that removed or moved but I don't know where else we could put that information.
Comment 3•14 years ago
|
||
Dupe of bug 592248?
Comment 4•14 years ago
|
||
What do you all think about collapsing the message count area when there is no message count (and possibly also when the text box is focused)?
Reporter | ||
Comment 5•14 years ago
|
||
(In reply to Blake Winton [On vacation until Jan 9th] (:bwinton - Thunderbird UX) from comment #4)
> What do you all think about collapsing the message count area when there is
> no message count (and possibly also when the text box is focused)?
I'd just get rid of it. Why is it there? What's the use case it's solving? Or put in the status bar or something. I can see from the size of the scrollbar thumb whether it's a huge list or a small list. I don't need a precise count for anything, ever, honestly.
Comment 6•14 years ago
|
||
You'ld have to ask Bryan (cc-ed, cause surely he doesn't have anything better to do than review three-year-old UI decisions ;). I suspect it's there for ux-feedback and, uh, something I'll call ux-locality (which is related to ux-visual-hierarchy, but different in that it's not about important controls).
Putting it in the status bar isn't a bad idea… (Well, until we get rid of the status bar. Just kidding! Don't shoot me! ;)
I could see changing the status bar from:
Unread: 0 Total: 7
to:
Unread: 0 Shown: 4 Total: 7
or some such.
And it seems to me, based on the complaints I hear when we remove things, that many of Thunderbird's users relish the amount of precise data we give them, so you (and I, since I totally agree with you) might not be representative of the people who will be affected by this.
Thanks,
Blake.
Reporter | ||
Comment 7•14 years ago
|
||
Here's my thinking. I love the count for things like "find in page" where I can't see the whole page and it's nice to know there are [some small number] of offscreen hits. But with a message list, it's either some small number I can see (fits on the screen) or some large number I can't see with many offscreen. I can take a look at the scrollbar thumb and get an idea if it's a 100 or 10000. If they all fit on screen, whether it's 20 or 40 doesn't seem to help me any. If they spill offscreen, knowing if it's "just a few offscreen" or "pages and pages of messages" is sort of useful in helping me decide if I want to try to narrow the search some. Still, I don't think that case is worth the extra UI.
I run with the statusbar hidden and so I'm cool with that bit too. There's rarely any info I need there. It shows me the "unread" count which is redundant with the server/folder pane telling me the same thing and it tells me the total message count which is some thousands or tens of thousands that really doesn't help me solve any problem.
Comment 8•14 years ago
|
||
I disagree "quick filter:" isn't useful. I don't think it's clear what it is otherwise.
Comment 9•14 years ago
|
||
(In reply to Blake Winton [On vacation until Jan 9th] (:bwinton - Thunderbird UX) from comment #6)
> You'ld have to ask Bryan (cc-ed, cause surely he doesn't have anything
> better to do than review three-year-old UI decisions ;). I suspect it's
> there for ux-feedback and, uh, something I'll call ux-locality (which is
> related to ux-visual-hierarchy, but different in that it's not about
> important controls).
For the quick filter text I'd agree that in icon only mode it's likely excessive and a responsive design would hide it. Perhaps for the count you could just trim it down to the number only and lose the text "messages" to save some space. The indicator has some value even if it could be better designed that's often not the reason you want to use to throw it all out.
Comment 10•14 years ago
|
||
(In reply to Asa Dotzler [:asa] from comment #5)
> (In reply to Blake Winton [On vacation until Jan 9th] (:bwinton -
> Thunderbird UX) from comment #4)
> > What do you all think about collapsing the message count area when there is
> > no message count (and possibly also when the text box is focused)?
>
> I'd just get rid of it. Why is it there? What's the use case it's solving?
It tells me how much emails I have in my selection (ie filtered) which helps me when I'm reading bugmail for instance.
Comment 11•14 years ago
|
||
(In reply to Asa Dotzler [:asa] from comment #7)
> But with a message list, it's either some small number I can see (fits on the screen) or
> some large number I can't see with many offscreen. I can take a look at the scrollbar
> thumb and get an idea if it's a 100 or 10000.
Unfortunately, this isn't true if there are collapsed threads in the results. That said, I *think* threads get expanded when the quick filter is active, but I'm not totally sure.
Updated•13 years ago
|
Severity: normal → minor
Updated•3 years ago
|
Severity: minor → S4
Comment 12•2 years ago
|
||
no longer relevant in version 115, in fact WFM
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•