325817 - (MailClearButton) After search for subject or sender, the Clear button is grayed out and inoperable.

Status: RESOLVED DUPLICATE of bug 286367

(SeaMonkey :: MailNews: Message Display, defect)

Description

[eftc]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

After I use the "Subject or Sender contains" box to get a subset of a mailbox's messages, the Clear button is grayed out and nonfunctional. The only way to clear is to delete the search term. I remember that for a brief time this was a bug in earlier versions of the Mozilla suite. Please fix this otherwise fabulous feature.

Reproducible: Always

Steps to Reproduce:
1. Type a text string in the "Subject or Sender contains" box 
2. Hit "Enter"
3. Click on the grayed-out Clear button.

Actual Results:  
Nothing happens when I click on the button.

Expected Results:  
It should have restored the full set of messages in the main window.

Comment 1

[zug_treno]

WFM with SeaMonkey 1.0 and SeaMonkey 1.5a/20060202, related to/duplicate of bug 278352 and bug 286367?

Comment 2

[OstGote!]

Seems that this is broken only on the 1.8/1.8.0 branch. Confirming with SeaMonkey 1.8 branch build 2002020401 on WinXP. WFM with SeaMonkey trunk build 2006020310 and Mozilla 1.7.12, although I get this in the JS console for SM trunk: 

Warning: reference to undefined property gSearchInput.showingSearchCriteria
Source File: chrome://messenger/content/searchBar.js
Line: 189
Warning: reference to undefined property gSearchInput.showingSearchCriteria
Source File: chrome://messenger/content/searchBar.js
Line: 529

Comment 3

[Mike Cowperthwaite]

Ostgote, did you intend to confirm this bug?

I can't reproduce with the SM 1.0 release (0130) under Win2K.

The 'searchCriteriaShowing' is a member of the search field that's shared between Firefox and Thunderbird -- that error message indicates some code 
leaked over from TB's development that shouldn't have, unless the trunk has 
also upgraded to use that field.  ("Search criteria showing" means the field 
is displaying, as in TB, a greyed-out "Sender" or "Subject" or "To or CC", 
etc.)

Comment 4

[OstGote!]

(In reply to comment #3)
> Ostgote, did you intend to confirm this bug?

I'm not sure if this is a new bug or not.

I see this with SM 1.8 branch build as noted in comment 2. With this build I get additional to the other JS warnings these two errors, directly after entering something to search.

Error: gSearchBundle has no properties
Source File: chrome://messenger/content/searchBar.js
Line: 106
Error: gSearchBundle has no properties
Source File: chrome://messenger/content/searchBar.js
Line: 63

I checked it with SeaMonkey 1.0 too, and you are right, it WFM with SM 1.0. But as I stated, I see this with the 1.1a build.

Comment 5

[Rolf Sponsel]

I experienced this issue too initially, immediately after upgrading from the Mozilla Application Suite 1.7.12 to SeaMonkey 1.0, on Windows/NT 4.0 sp6a, using an existing Mozilla Profile (classic theme).

Now, after having removed the XUL.mfl file, found in C:/Winnt/Mozilla/Profiles/<ProfileName>/, and re-booted Windows the issue seems to have gone away.

But, as I wrote, this was on NT - not XP, which might behave differently.

Comment 6

[Rolf Sponsel]

I can confirm that this happens once in a while, on Windows NT 4.0 sp6. So it seems to be - at least - a Windows issue. Not just an XP issue.

It might be that it occurs after having performed an s.k. "quick" quick search, as described in bug 286367 - although I am unaware of it. I haven't managed to trigger that mal-behavior explicitly though. During normal use, all of the sudden it appears, and a restart of SeaMonkey 1.0 remedies it - which of course is annoying, considering that my browser usually runs for days w/o being restarted.

There is no need to remove any XUL.mfl and/or chrome.rdf files before restarting SeaMonkey.

The theme I use is classic.

Comment 7

[Jerry Kliot]

moving the cursor from the inbox to another folder (i.e. the draft folder) and back also clears the search text and restores the full set of messages.

Comment 8

[Winfried Schöch]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

I can confirm this bug on Windows XP (fresh install!). JavaScript Console shows 

Error: gSearchBundle has no properties
Source File: chrome://messenger/content/searchBar.js
Line: 106

Error: gSearchBundle has no properties
Source File: chrome://messenger/content/searchBar.js
Line: 65

as described in bug 286367. So, is this a duplicate?

Comment 9

[Mike Cowperthwaite]

(In reply to comment #8)
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130
> SeaMonkey/1.0
> 
> I can confirm this bug on Windows XP (fresh install!). 

With an old build, apparently.

> as described in bug 286367. So, is this a duplicate?

Seems likely.  286367 is marked fixed due to a recent patch checked in for 
bug 179050; can you reproduce with a current suite build?

Comment 10

[general]

I can confirm this bug on all versions of SeaMonkey I've used (started w/ version 1) on Win XP SP 2. I'm now on 1.0.5.

It is reproducible. On any SeaMonkey clean start (i.e. after a proper SeaMonkey shutdown), if you enter a search term in the Mail components "Subject or Sender contains" quick search, and hit Enter right away (i.e. don't just type the words and let the filter go), the Clear button (and the Alt + C clear shortcut) won't work. The Clear button just stays grayed out.

This only occurs on the very first use of the quick search for that session. If you don't hit Enter, i.e. just type the search term and let the filter go, then you can hit Enter after every other search term, and the Clear button works as expected for the rest of the browser session (i.e. until the next clean start).

I've started poking around the files implicated in the JavaScript Console (already noted here in Comment #2), but am not very familiar with XUL, so nothing leaps out at me. I'll keep trying...

Comment 11

[Bruno 'Aqualon' Escherl]

This could depend on bug 364060 and/or bug 286367. The patch in bug 286367 fixed it for me in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2pre) Gecko/20061221 SeaMonkey/1.1

Comment 12

[Serge Gautherie (:sgautherie)]

Theses warning + error are the same as I reported in bug 262893 comment 10 and now 18.

Marking as "Blocks" for now.