[Tickets #7196] Re: Hitting escape in the search field doesn't clear it

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7196
------------------------------------------------------------------------------
  Ticket             | 7196
  Updated By         | Chuck Hagenbuch <chuck at horde.org>
  Summary            | Hitting escape in the search field doesn't clear it
  Queue              | IMP
  Version            | HEAD
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Chuck Hagenbuch, Michael Slusarz
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2009-01-15 20:56) wrote:

> Is Apple Mail doing search as you type?  If so, and it is hitting the
> IMAP server for every search (as opposed to its local cache)

I'm 99% certain it's using the local Spotlight cache.

> totally inefficient.  The whole point of allowing a user to set
> search parameters before typing in DIMP is to eliminate this
> inefficiency.  There is absolutely no reason to send an IMAP search
> request for 'c', 'ch', 'chu', 'chuc', and/or 'chuck' in the From
> header if you are searching for that information in the Subject
> header.

Agreed.

>> - hitting escape while in the search field clears the search and
>> hides the search bar
>
> That is non-intuitive for me.  I never use ESC in this manner.
> Although this is less intrusive than any of the other suggestions in
> this ticket, and wouldn't break anything that is already implemented
> so this is a reasonable request.

I've seen this in a lot of places more recently; ESC as a kind of  
cancel-out. I'd like to see this.

>> - since it's impossible to do an empty search, empty searches don't
>> result in empty mailboxes. I think if we end up with nothing in the
>> search filter box, we should either not run a search, or we should
>> match everything - matching nothing, especially when what I've done
>> is tab in and out of the search box, is really disruptive.
>>
>> Clicking the search box and then outside of it does leave the search
>> bar open, but it doesn't seem to run an empty search - not sure why
>> the difference from tabbing in and out.
>
> This is a feature: after all, why run an empty search?  When I click
> on the search box, I don't want the mailbox listing to go blank.  I
> haven't searched for anything yet.  An empty search string is NO
> search, not an empty search.

Right. The bug here is that if I tab into the search box and out, the  
mailbox listing *does* go blank. If I just click, it doesn't. I think  
that tabbing into the search box should behave the same as clicking it.