After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 660900 - search bar displays wrong search term when switching folders
search bar displays wrong search term when switching folders
Status: RESOLVED DUPLICATE of bug 564820
Product: evolution
Classification: Applications
Component: Mailer
3.0.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-10-04 17:24 UTC by rmeador
Modified: 2011-10-21 13:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rmeador 2011-10-04 17:24:52 UTC
Evolution 3.0.3 on Fedora 15 x86_64.  I'm connecting to an Exchange 2010 mail server with evolution-mapi 3.0.3-2, but I don't think that's relevant.

Assumption: you have a subfolder under your inbox that contains some mail.

1) search the inbox for an arbitrary term (this works correctly)
2) switch the view to the subfolder

Observe that the search bar returns to the "Subject or Addresses contain" message, indicating a cleared state, yet the term you searched for in the inbox is still in effect.  I doubt this is the intended behavior, since the contents shown for the subfolder are filtered based on the original term, but the search bar doesn't give any indication this is happening, nor does it permit you to clear the search term (you have to go back to the inbox and clear it there to get rid of it).

3) search the subfolder for a different arbitrary term

Observe that this does what you expect, filtering the subfolder by that term

4) go back to the inbox

Observe that the inbox is now filtered by your term from step 3, but the search bar indicates it is filtering by the one from step 1.  This is clearly wrong.
Comment 1 Milan Crha 2011-10-21 13:53:59 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 564820 ***