Bug 76381 - [Browser] Help contents does not start with keyboard focus
Summary: [Browser] Help contents does not start with keyboard focus
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux-GTK
: P2 normal (vote)
Target Milestone: 3.4   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2004-10-15 14:24 EDT by Douglas Pollock CLA
Modified: 2008-04-09 15:47 EDT (History)
5 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 Douglas Pollock CLA 2004-10-15 14:24:35 EDT 
I200410130800, GTK+ 2.4.9, KDE 3.3.0, Linux 2.6.8.1 
 
When the help contents window first opens, it does not have keyboard focus.  
This makes it impossible to navigate with just a keyboard.
Comment 1 Konrad Kolosowski CLA 2005-06-01 22:23:05 EDT 
Seems to only appear in embedded help browser on Linux.
Comment 2 Konrad Kolosowski CLA 2005-06-02 14:11:40 EDT 
Also affects browser in help view and intro.  I can place the focus inside the 
embedded browser using mouse, but once it leaves it it cannot reenter, it 
jumps to the next control.
In case of the help browser in a separate window, there is no other controls 
so focus is not visible at all.
Comment 3 Steve Northover CLA 2005-06-10 16:08:35 EDT 
GG to check to see whether this is a regression.  Not getting the initial 
focus is bad, but the jumping Konrad describes seems worse.
Comment 4 Grant Gayed CLA 2005-06-10 16:52:18 EDT 
The Help Contents issue happens in 3.0.2 too.

The problem that Konrad describes seems to have appeared sometime between M5 
and M7.
Comment 5 Steve Northover CLA 2005-06-10 17:36:16 EDT 
Can you enter a new bug report and track it down a bit please for possible 
inclusion in RC3?  Thanks.
Comment 6 Grant Gayed CLA 2005-06-13 09:45:53 EDT 
I've logged bug 99636 to track the second problem.
Comment 7 Steve Northover CLA 2006-06-28 14:16:35 EDT 
We need to look into this for accessibility.
Comment 8 Karice McIntyre CLA 2006-12-04 09:55:54 EST 
Grant, what is the status/target of this bug?
Comment 9 Grant Gayed CLA 2008-04-09 15:47:04 EDT 
This is fixed in the 3.4 stream.