Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322805 - [compare] Eclipse Text compare: Previous Change button is highlighting the whole line rather than just the previous change as in word.
Summary: [compare] Eclipse Text compare: Previous Change button is highlighting the wh...
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows Server 2003
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-16 11:22 EDT by Rahul Yadav CLA
Modified: 2010-08-17 04:52 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rahul Yadav CLA 2010-08-16 11:22:35 EDT 
Build Identifier: Version: 3.6.0.v20100525-7b7mFKtFEx2XmfZ4_B7NUJA, Build id: I20100608-0911

Steps to Reproduce:

1.Compare two different files in text editor.
2.Select any file from Structure Compare view.
3.Click on Previous / Next change buttons from CE toolbar.

Expected Results:
The next or the previous change words should get highlighted.

Actual Result:
In case of Next change, the next changed word is highlighted however in case of Previous change, the previous line which contains the change is highlighted instead of actually a changed word.


Reproducible: Always

Steps to Reproduce:
1.Compare two different files in text editor.
2.Select any file from Structure Compare view.
3.Click on Previous / Next change buttons from CE toolbar.
Comment 1 Dani Megert CLA 2010-08-17 04:52:44 EDT 
The text compare does not show structure, so I assume you refer to Java compare.

This works fine for me using R3.6 and 3.7 M1 from here:
http://download.eclipse.org/eclipse/downloads/

If you can reproduce with one of those builds then please provide a step by step test case starting from a fresh workspace and reopen this bug.