268797 - Search field mode not visible when quicksearch active

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, enhancement)

Description

[Rathmann, Zoltan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: version 0.9 (20041103)

This is a suggestion to inptov the quick serch function 

Reproducible: Always
Steps to Reproduce:
1.Select a search field i.g. "Sender" or "Suject" in the quich search field
2. I select another folder or click on new mail
3. The serch field name "sender" orr "subject" etc. appears in the search field.
4. I write the serch string in the field and hit enter

Actual Results:  
1. I can't see the name of the serch field, what I have selected.
4. After hitting enter, there is no visible sign what is happening

Expected Results:  
1. The name of the serch field ("sender" "subject" ect.) should be allways
visible, not only when I change sreens. 

I also miss a toolbar button for detailed search dialog with the function of
CTRL+ SHIFT+F

The most frequently used serch fields i.g.: subject, sender, date, should be
present in the serch messages dialog box so that I don't have to push the button
"more" every time I do a usual search.
The best solution would be to create a checkbox beside the "Fewer" button with
the text: "Use this search fields as default". If I check this box, my search
fileds are saved and defoulted for every other use. If I change anything (i.g.
push the more or fewer buttons, this checkbox should be unchecked by the program
giving me the possibility to save the changed fields as default.

Comment 1

[Mike Cowperthwaite]

(In reply to comment #0)
> 1. The name of the serch field ("sender" "subject" ect.) should be allways
> visible, not only when I change sreens. 

This is unlikely to be implemented, but I'll restate the summary for this point.

One possibility would be to display the mode in a tooltip.


> I also miss a toolbar button for detailed search dialog with the function of
> CTRL+ SHIFT+F
> 
> The most frequently used serch fields i.g.: subject, sender, date, should be
> present in the serch messages dialog box so that I don't have to push the
> button "more" every time I do a usual search.
> The best solution would be to create a checkbox beside the "Fewer" button with
> the text: "Use this search fields as default". If I check this box, my search
> fileds are saved and defoulted for every other use. If I change anything
> (i.g. push the more or fewer buttons, this checkbox should be unchecked by
> the program giving me the possibility to save the changed fields as default.

Those two ideas are both fine suggestions, but the b.m.o policy is one item per 
bug; please open two new bugs (severity:enhancement) for those items.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.