Bug 170835 - [Progress] Can't fully navigate ProgressMonitorDialog using keyboard
Summary: [Progress] Can't fully navigate ProgressMonitorDialog using keyboard
Status: RESOLVED DUPLICATE of bug 131851
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2007-01-17 16:16 EST by Brian Lillie CLA
Modified: 2007-07-16 11:06 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Lillie CLA 2007-01-17 16:16:35 EST
Eclipse 3.2.2
Build ID: M20061220-1400

Steps To Reproduce:
Perform an operation that causes the ProgressMonitorDialog to display.  (An example is to check out a number of projects from CVS)

Now click on the Details button.  As expected the Details display on the screen.  Now press the tab key.  Notice that focus goes to the Cancel button.  Press tab again and notice that you can no longer navigate through the buttons on the dialog.  The focus continues to stay on the Cancel button.  Note, there are buttons in the details area of the dialog that cannot be navigated to either.  They are the small red squares to the right of the detail information and they allow you to cancel the operation.

More information:
Comment 1 Mike Wilson CLA 2007-03-21 15:10:11 EDT
WORKSFORME on 3.3 M6 on Mac.

That is, after following the steps in the bug, I can still tab between the buttons. However, there is a slight oddity in that, after I tab through all three buttons, I have to hit the tab key twice to get back to the first one. Presumably, focus has gone elsewhere in the dialog, but there is no focus ring. This may be due to changes in the focus ring behavior made recently by SWT (see bug 28842)
Comment 2 Mike Wilson CLA 2007-03-21 15:22:10 EDT
Tod can you test this on the other platforms?
Comment 3 Philipe Mulet CLA 2007-03-21 17:50:20 EDT
If/When addressed:
Please make sure to attach the 3.3 patch, and risk assesment for a 3.2.2
backport.
Comment 4 Tod Creasey CLA 2007-03-22 13:58:11 EDT
This is a duplicate of Bug 131851 which was fixed in 3.3 M1



*** This bug has been marked as a duplicate of bug 131851 ***