Bug 574918 - Navigation from "Problems" view does not consistently work with "Backward History"
Summary: Navigation from "Problems" view does not consistently work with "Backward His...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.20   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-19 14:18 EDT by Andy Lee CLA
Modified: 2021-07-19 14:20 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Lee CLA 2021-07-19 14:18:21 EDT
Sometimes, after navigating to a file using the "Problems" view (ie, by double-clicking a problem), that file does not get properly inserted into the history used for the "backward / forward history" commands. It seems like the issue only occurs in cases where the navigation to the problem caused a new file to be opened.

To reproduce:
 - Setup: A workspace with at least one problem (e.g. a compile error)
 - Close all files
 - Open the Problems view
 - Open a file other than the one that has a compilation error (File A)
 - Use the Problems view to navigate to the compilation error via double click (File B)
 - After the file opens, navigate somewhere else, e.g. by using F3 to jump to another class (File C)
 - Click the backward history button

Result: The back button jumps you from File C back to File A, skipping over File B.

NOTE: The bug only seems to occur if you double click on a problem while the problems view does not already have keyboard focus. So it won't happen, for example, if you click once to select the problem, pause, then double click to navigate. It also will not occur if you first click the "Problems" tab to open it, since that grants focus to the tab.
Comment 1 Andy Lee CLA 2021-07-19 14:20:12 EDT
Disregard the part about the issue only happening when a new file is opened; further testing revealed that it was focus-related, and can occur regardless of whether a new file is opened or not.