Bug 403984 - [Accessibility]Shotcut is missing on XML Source tab in designer
Summary: [Accessibility]Shotcut is missing on XML Source tab in designer
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2013-03-21 03:55 EDT by fengfu liu CLA
Modified: 2019-11-27 07:12 EST (History)
4 users (show)

See Also:


Attachments
Detail (271.86 KB, image/png)
2013-03-21 03:55 EDT, fengfu liu CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description fengfu liu CLA 2013-03-21 03:55:08 EDT
Created attachment 228814 [details]
Detail

OS Birt

Steps to reproduce

1,Launch Birt.
2,Swtich to "XML Source" tab and hit "context menu" keys in keyboard.
3,Press W and check the shotcut for sub menu

Actual Result:Shotcut for properties is missing.See attached.
Comment 1 Zhiqiang Qian CLA 2013-05-22 13:31:05 EDT
This action was contributed by org.eclipse.ui.views.
Comment 2 Paul Webster CLA 2013-05-22 13:39:46 EDT
This has always been this way (it's the second view that starts with a P).

We could consider a smarter algorithm to pick the mnemonics

PW
Comment 3 Lisa Lasher CLA 2013-05-28 14:01:51 EDT
During the IES 4.2.1 testing, Carolyn MacLeod said that it is not required for every action to have a short cut mnemonic defined, because you can also use the keyboard to navigate up/down through the context menu and select the action.   If that is the case here, then this would not be a must-fix
Comment 4 Lars Vogel CLA 2019-11-27 07:12:10 EST
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.