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 446041 - cycling forward through search results in message view does not work
cycling forward through search results in message view does not work
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-10 14:35 UTC by Øystein Gisnås
Modified: 2012-10-15 14:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Øystein Gisnås 2007-06-10 14:35:09 UTC
Please describe the problem:
When viewing a message either inline in the main view or in a separate
window, it is possible to find the first result of a search in the
message, and it is possible to see the total number of matches, and the
previous button lets you cycle through the matches backwards, but the
next button doesn't cycle forward through search results. Instead it has
no effect.

Steps to reproduce:
1. View a message where a word in the message body is repeated multiple times
2. Press Ctrl-Shift-F and search for the repeated word
3. Press the "Next" and "Previous" button multiple times to step through the matches


Actual results:
Backward stepping works, forward stepping stops at the first match.

Expected results:
Forward stepping should step through all matches

Does this happen every time?
Yes

Other information:
This bug was originally reported by Trevor Caira at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428146
Comment 1 Akhil Laddha 2009-07-31 13:42:46 UTC
It seems to work fine in 2.27.5. May be as Matthew did many changes there.
Comment 2 Matthew Barnes 2009-07-31 13:47:20 UTC
Not really composer related -- removing tag.

But yeah, should be working better (but not perfect) in 2.27.
Comment 3 André Klapper 2012-06-16 17:22:29 UTC
Øystein: Is this still a problem in 3.4 or 3.2?
Latest comments indicate that it should not be...
Comment 4 André Klapper 2012-08-06 15:21:46 UTC
Øystein: Is this still a problem in 3.4 or 3.2?
Latest comments indicate that it should not be...
Comment 5 André Klapper 2012-10-15 14:34:45 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!