Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356886 - The highlighted values with navigation (press F3 key) is not correct for the 1st time
Summary: The highlighted values with navigation (press F3 key) is not correct for the ...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Xiao Bin Chen CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-07 02:38 EDT by fahua jin CLA
Modified: 2017-02-23 14:16 EST (History)
3 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 fahua jin CLA 2011-09-07 02:38:56 EDT 
Build Identifier: 0.7.0.v201109061723

1) Start EDT with an empty workspace
2) Create a client project with 'Web Client Project'
3) Create an RUI handler, and EDT will open the handler with VE.
4) Right click the created RUI handler, open with 'EGL Editor'
5) Put the cursor to GridLayout, and press F3. EDT will navigate the code to GridLayout, but the selected code is not correct (THIS IS THE PROBLEM).
6) Use the alt + left key to go back the handler, and press F3 again, the selected code is correct.

Reproducible: Always
Comment 1 Xiao Bin Chen CLA 2011-09-27 02:22:14 EDT 
This defect can't be reproduced in my machine, set it to minor.
Comment 2 Brian Svihovec CLA 2011-10-26 14:31:54 EDT 
I cannot recreate this issue as well.  If the issue has somehow been resolved indirectly, let's close it and let someone else report it in the future if it happens again.
Comment 3 fahua jin CLA 2011-10-30 21:55:33 EDT 
(In reply to comment #2)
> I cannot recreate this issue as well.  If the issue has somehow been resolved
> indirectly, let's close it and let someone else report it in the future if it
> happens again.

It seems that this problem only happens with IBM JVM, I suggest to triage this defect to future.
Comment 4 Brian Svihovec CLA 2011-10-30 22:24:14 EDT 
Do we have any idea why this is only happening in the IBM JVM?  There is one other issue that we know about right now regarding a difference between VM's, and we are not working on it right now because it should be an edge case.  This does not seem like an edge case, and at the very least we should understand why the difference is happening before we decide to defer a fix.