Community
Participate
Working Groups
build I20040210-0800 Many of the toolbar buttons in the console are not accessible (e.g. display selected console, pin, scroll lock). They should also appear on a menu. Recommend using the view menu for actions that apply to the view or the current page, and the context menu for things that apply to the selection.
I think this is more a problem with Bug 53882 as you cannot get to the toolbar from the keyboard currently
Actually, I agree. In general, everthing on the toolbar does not appear in the context menu. For example, "Collapse All" and "Link with Editor" in the navigator. Marking as a dup. *** This bug has been marked as a duplicate of 53882 ***
No, our policy so far has been to provide all commands on menus. Link to Editor is on the view menu in the Package Explorer, Navigator and Java Browsing views (in the latter they're not in the toolbar because it's not expected that they'll change often). Collapse All is an exception because it's easy to collapse a number of items with the keyboard.
Just to emphasize this, if only tab access to the toolbars was provided, then to toggle p\Pin Editor would require a keyboard user to use 9 gestures to toggle it and get focus back to the view. This wouldn't be particularly usable. With it on the view menu, this would take 2 gestures (ctrl+F10, P), assuming the actions have good, non-conflicting mnemonics (which they should). The Workbench still needs to provide tab access to the toolbar, but it's a last resort for accessibility. - just_woke_up_after_yet_another_interrupted_nights_sleep_and_grumpy_nick
... and it sounds like you left your mouse at work? :-)
Do not intend to address for 3.0. This is similar to the outliner and search view issue. Notice that all the actions in the toolbar of the Java outliner and Java search page are not in the context menu (for example, sort members, show public members...). In the case of the console, the actions missing from the context menu are those that are generic to all consoles. Each page contains its own context menu with actions specific to it. However, the console itself does not have a way to add the generic actions to a page, and visa versa. It seems to be a shortcoming of the paged view. As well, one cannot use plug-in XML to contribute an action to a page in a page book view (that I can see).
I was imagining that toolbar buttons provided by the view would have accessible equivalents in the view triangle menu, not the context menu of the pane.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
