Bug 464766 - "Next" doesn't cycle through finds in 'Current Message' search
Summary: "Next" doesn't cycle through finds in 'Current Message' search
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: evolution
Version: 5.3
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-30 12:05 UTC by Jay Turner
Modified: 2015-01-08 00:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-01 15:05:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jay Turner 2008-09-30 12:05:04 UTC
Description of problem:
When performing a "Current Message" search in Evo, the bar comes up at the bottom of the message pane indicating how many Matches were found as well as "Previous" and "Next" buttons.  The "Next" button doesn't cycle through the matches.  The "Previous" button does still function as expected.

Version-Release number of selected component (if applicable):
2.12.3-12.el5

How reproducible:
Always

Steps to Reproduce:
1. Pull up a message then execute a "Current Message" search for a term in the message (something which will result in multiple matches)
2. Press the "Next" button and the first match will be highlighted.  Continue to press "Next" and nothing will happen.
3. Press the "Previous" button and you will correctly cycle through the matches in reverse order

Comment 1 RHEL Program Management 2008-09-30 12:29:07 UTC
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

Comment 10 RHEL Program Management 2008-12-01 15:05:09 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.


Note You need to log in before you can comment on or make changes to this bug.