Bug 293533 - [KeyBindings] incorrect navigation instruction read when switching between tab
Summary: [KeyBindings] incorrect navigation instruction read when switching between tab
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL: ORACLE_OEPE
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-28 03:22 EDT by Raj Alagumalai CLA
Modified: 2019-09-06 16:19 EDT (History)
1 user (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 Raj Alagumalai CLA 2009-10-28 03:22:55 EDT 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.14) Gecko/2009082707 Firefox/3.0.14 GTB5 (.NET CLR 3.5.30729)
Build Identifier:  Build id: 20090920-1017

incorrect navigation instruction read when switching between tab

Reproducible: Always

Steps to Reproduce:
create a dynamic web project
open web.xml
create index.html
tab until you switch to the design view
notice that the reader read Ctrl up/down to switch between tabs. this should be Ctrl Page up/Page down
Comment 1 Paul Webster CLA 2009-11-12 15:09:10 EST 
What are you reading, exactly?  Do you mean the keybindings (CTRL+PAGE_UP and CTRL+PAGE_DOWN) which do switch between editor tabs?

PW
Comment 2 Carolyn MacLeod CLA 2009-11-15 14:21:56 EST 
When a TabItem or CTabItem gets focus, JAWS says: "To switch pages press control tab".

But in SWT (and Eclipse) you need to type control pageup or control pagedown to switch pages.

I am not sure if this is what Raj meant, though.
Comment 3 Raj Alagumalai CLA 2009-11-15 14:48:04 EST 
Thanks Carolyn. That's exactly the issue I reported. The JAWS version I used in my test is JAWS 10.0

thanks
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:19:00 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.