Bug 297834 - [key binding][content assist] Multiple editor views: "Home" and "End" key working wrong after unfinished autocomplete in another editor view
Summary: [key binding][content assist] Multiple editor views: "Home" and "End" key wor...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: 3.6 M5   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-15 08:09 EST by Hendrik Eeckhaut CLA
Modified: 2009-12-15 12:26 EST (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 Hendrik Eeckhaut CLA 2009-12-15 08:09:29 EST 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009061118 Fedora/3.0.11-1.fc9 Firefox/3.0.11
Build Identifier: M20090917-0800

If you use multiple editor views, start autocomplete and click another editor: "home" (AbstractTextEditor.LineStartAction) and "end" (AbstractTextEditor.LineEndAction) are not working as expected.

Reproducible: Always

Steps to Reproduce:
1. open two editor views side by side
2. place cursor into RIGHT view
3. hit CTR+SPACE
4. place cursor into LEFT view (by mouse click)
5. hit "home"-key or "end"-key
In some situations nothing happens. In other situations (when there is a horizontal scroll bar in the RIGHT editor) the RIGHT editors scrolls.
Comment 1 Oleg Besedin CLA 2009-12-15 10:01:33 EST 
I can duplicate with Eclipse 3.6 on WinXP.
Comment 2 Paul Webster CLA 2009-12-15 10:29:20 EST 
I suspect the content assist is still capturing the home/end key strokes.  I can arrow up and down in the second editor, but home and end still don't work until I activate something else.

PW
Comment 3 Dani Megert CLA 2009-12-15 12:16:43 EST 
Introduced in R3.4. Only a problem when editor is side-by-side.
Comment 4 Dani Megert CLA 2009-12-15 12:26:37 EST 
Happens because focusLost comes to the deactivated editor after focusGained on the new one and hence some actions are wrongly retargeted.

Fixed in HEAD.
Available in builds >= N20091215-2000.