Bug 384162 - Internal web browser does not catch Tab keystrokes
Summary: Internal web browser does not catch Tab keystrokes
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 4.2.2+   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks: 376011
  Show dependency tree
 
Reported: 2012-07-03 09:56 EDT by Kaloyan Raev CLA
Modified: 2013-03-25 15:29 EDT (History)
6 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 Kaloyan Raev CLA 2012-07-03 09:56:46 EDT 
Steps to reproduce:
1. Download the Eclipse IDE for Java EE Developers (Juno, based on 4.2)
2. Extract it and start it. 
3. Open the internal web browser: Ctrl+3 and type "Open Web Browser"
4. Request "google.com" in the browser. 
5. The keyboard focus is now in the search text field. 
6. Hit the Tab key. 

Expected: the keyboard focus should traverse to the next button inside the web page. 

Actual: the keyboard focus leaves the web browser editor and moves to the Outline view. 

This works as expected in Indigo SR2, but regresses in Juno. It looks like the root cause is in a new feature in Juno that enables users to traverse through the views in the perspective using the Tab key. 

This issue is quite annoying for people who are used to web development in Eclipse.
Comment 1 Carolyn MacLeod CLA 2013-02-12 09:02:43 EST 
I see this failure in base Eclipse also, following almost the same steps (for step 3, it's just "Open Browser").
This is related to bug 376011.
Moving back to Platform UI.
Comment 2 Eric Moffatt CLA 2013-02-12 10:02:21 EST 
After talking with the SWT team they would like to take another look at this to see if it's an implementation issue with the Browser control itself...reassigning.
Comment 3 Eric Moffatt CLA 2013-02-12 10:05:34 EST 
Oops, helps if it's in the correct component...;-)
Comment 4 Grant Gayed CLA 2013-02-13 12:34:37 EST 
Fixed in the 4.3 stream > 20130213, patch: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=a037998b353b05ee82e13bf075b6bbaa98c571fb .
Comment 5 Carolyn MacLeod CLA 2013-02-26 14:40:44 EST 
Fix needs to be backported to 4.2.2+. Reopening as a reminder to do this.
Comment 8 Lisa Lasher CLA 2013-03-25 15:29:03 EDT 
added Accessibility keyword so this defect will show up in queries