Closed
Bug 58987
Opened 24 years ago
Closed 24 years ago
No keyboard access for tab control
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
VERIFIED
FIXED
People
(Reporter: aaronlev, Assigned: bryner)
References
Details
(Keywords: access)
For example, go to the Cookie Manager under Tasks - Privacy and Security -
Cookie Manager - View stored cookies. There is no way to keyboard from tab to
tab. In windows this is done with Control-Tab and Shift-Control-Tab, but this
may not work for Unix users. On my KDE system, Control Tab moves through the
desktops.
However, there needs to be some way to move through the items via the keyboard.
Reporter | ||
Comment 1•24 years ago
|
||
As Sarah and I discovered, tabbed dialog box navigation is different in Modern
and Classic.
In modern, it doesn't work at all.
In classic, you have to click on a tab widget first, then you can arrow through
them.
Comment 2•24 years ago
|
||
I see this too on Win98, setting all/all.
On Win Classic and Win98, you can also Tab through the tabs, which isn't right
(you should only be able to arrow through them).
OS: Linux → All
Hardware: PC → All
Comment 3•24 years ago
|
||
Chaning the qa contact on these bugs to me. MPT will be moving to the
owner of this component shortly. I would like to thank him for all his hard
work as he moves roles in mozilla.org...Yada, Yada, Yada...
QA Contact: mpt → zach
Comment 5•24 years ago
|
||
So let's use (Shift+)Control+Tab. Apart from Alt+Tab, we can't avoid every
possible modifier+specialkey combo just because it might be taken up by
over-eager window managers. That's not reasonable.
Reassigning to Bryner -- I think he has a bug on this already.
Assignee: mpt → bryner
Component: User Interface Design → Keyboard Navigation
QA Contact: zach → sairuh
Reporter | ||
Comment 6•24 years ago
|
||
Please use www.mozilla.org/projects/ui/accessibility/mozkeyintro.html, and the
associated keys cross-reference list, when suggesting keystrokes.
Ctrl+Tab is currently being taken by pane/frame navigation.
If we also use it for tabbed dialog navigation, be aware that would need to
override frame navigation. Therefore, once a user navigated into the sidebar,
they wouldn't be able to get out.
That's what the cross-reference is for, so we don't get into these keyboard
conflict situations.
Comment 7•24 years ago
|
||
Aaron, that is not correct.
Control+Tab is not `taken' by frame/pane navigation, because there are no
tabbed dialogs in Mozilla which also use frames (and there never will be, on my
watch). <http://mozilla.org/projects/ui/accessibility/mozkeylist.html> clearly
suggests Control+Tab for navigating between tabbed dialogs.
And once a user navigated into the sidebar, they would so be able to get out
again, by typing Control+Tab again. The sidebar does not use a tab control, and
<http://mozilla.org/projects/ui/accessibility/mozkeylist.html> clearly suggests
(Shift+)accel+PgUp/PgDown for navigating between sidebar panels. (That keyboard
combo is far from ideal, but the main point is that it's not Control+Tab.)
In future, if you disagree with your own keyboard spec, please discuss your
disagreement in the relevant newsgroups before using it as an argument in
Bugzilla. Thanks!
Assignee | ||
Comment 8•24 years ago
|
||
aaronl -- I did go ahead and implement ctrl+[shift+]tab as a shortcut for
changing tabs. If you think that behavior isn't correct, please file a new bug.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Keyboard: Navigation → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•