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 323917 - Advanced Search UI inconsistent
Advanced Search UI inconsistent
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 327508 327510 336362
 
 
Reported: 2005-12-12 19:40 UTC by Karsten Bräckelmann
Modified: 2021-05-19 12:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Karsten Bräckelmann 2005-12-12 19:40:28 UTC
When applying Advanced Searches or Saved Searches, the UI does not reflect this
state consistently.

Steps to reproduce:
* Apply an Advanced or Saved Search
  * the text input field is grayed-out
* Switch Folders
* Switch back to the folder with the search applied
  * the text-input field is not grayed out any more and sensitive

Expected results:
* consistent UI
* grayed out text input field

Additional Notes:
* Entering a search text and hitting the Find Now button results in *really*
  weird behavior from a users point of view.
Comment 1 Karsten Bräckelmann 2005-12-12 19:44:08 UTC
Forgot to mention: The text input field is not grayed out after re-starting Evo
as well, although the search still applies. :)
Comment 2 André Klapper 2005-12-12 19:45:32 UTC
confirming
Comment 3 Srinivasa Ragavan 2006-01-17 16:53:06 UTC
guenther, Doesn't visual cue for search helps to solve it? Just checking...
Comment 4 Karsten Bräckelmann 2006-01-18 00:23:34 UTC
What visual cue? Are you talking about CVS HEAD?

Don't have a recent devel version handy, but I will check if it fixes this issue. Remember, the bug is filed against Evo 2.4.x...
Comment 5 Karsten Bräckelmann 2006-01-23 20:21:41 UTC
Andre just told me: "still valid in 2.5.5"

So "no", the visual cue does not solve this issue. Please read the original report and try to reproduce it. Should be pretty easy.
Comment 6 André Klapper 2006-07-11 15:45:12 UTC
switching from one folder to another is obsolete in 2.7.4 as the search view remains for all folders, even if i search only in the "current folder" (hmm...).

problem: running an advanced search turns the quick search ui text input field blue. so far, so good.
running a saved search turns the quick search ui text input field in a bright grey. bad, bad, and not easy to recognize at all.

wrini, jony, comments?
Comment 7 André Klapper 2006-07-11 21:47:49 UTC
switching from one folder to another is obsolete in 2.7.4 as the search view
remains for all folders, even if i search only in the "current folder"
(hmm...).

problem: running an advanced search turns the quick search ui text input field
blue. so far, so good.
running a saved search turns the quick search ui text input field in a bright
grey. bad, bad, and not easy to recognize at all.

wrini, jony, comments?
Comment 8 Srinivasa Ragavan 2006-07-12 03:37:30 UTC
jony: ?
Comment 9 Johnny Jacob 2006-07-12 03:54:41 UTC
when running a saved search, the quick search text ui should be blue(theme) and the clear button should be visible. 'saved search' ui behaviour should be same as 'advanced search'.
Comment 10 Matthew Barnes 2008-03-11 00:27:33 UTC
Bumping version to a stable release.
Comment 11 André Klapper 2012-06-27 12:34:55 UTC
(In reply to comment #0)
> When applying Advanced Searches or Saved Searches, the UI does not reflect this
> state consistently.
> 
> Steps to reproduce:
> * Apply an Advanced or Saved Search
>   * the text input field is grayed-out

It's not in 3.2.3.
Comment 12 André Klapper 2021-05-19 12:12:12 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.