Closed
Bug 105565
Opened 23 years ago
Closed 22 years ago
RFE: Mnemonic keyboard navigation of links
Categories
(Core :: DOM: UI Events & Focus Handling, enhancement, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
Future
People
(Reporter: risto.kankkunen, Assigned: aaronlev)
References
Details
(Keywords: access, helpwanted)
It's currently possible to cycle through the links of a page with TAB and
Shift-TAB. However, on many pages this is quite slow and frustrating because of
the big number of links.
It should be possible to jump more quickly to the link one is interested in,
based on the visible text of the link. Two suggestions:
1. Each press of an alphanumerical character should move focus to the next link
with the first first alphanumerical character matching. The first alphanumeric
character of each link could be highlighted somehow as a visual cue, when the
focus enters the document window by keyboard action (i.e. in the same case the
dotted rectangle is now drawn around a link).
2. Each press would search incrementally for the next matching link. The first
(alphanumerical) keypress would move the focus to the next link starting with
that letter, the second keypress would move the focus to the next link starting
with those two characters and so on. Some visual cue could/should be used to
show the matched characters of a link.
In both cases, perhaps the status bar could be used to give feedback as well.
The document window might be hard to read because of bad background colors etc.
I would personally prefer the second idea, I think it would make keyboard
browsing a snap. When you see a link you want to go to, just start typing it's
"name" until you see it highlighted and press return. Voila!
Assignee | ||
Comment 1•23 years ago
|
||
Very similar to http://bugzilla.mozilla.org/show_bug.cgi?id=58852
In that one, you select it from a list or sidebar panel.
I actually think both of your methods should work concurrently - that is
sequential letters of the same kind and incremental searching of several
different letters should both work. The only thing you'd lose is when something
begins with two of the same letter, which doesn't happen all that often.
Either way, pretty much the same thing as bug 58852.
I had envisioned something exactly what you're saying this myself; however,
perhaps the list or sidebar panel would be easier to do, while this one might
cause some problems with the page jumping around a lot as you type.
Assignee | ||
Comment 3•23 years ago
|
||
-> taking, as part of keyboard navigation
This is pretty much exactly what we want to do.
Assignee: mpt → aaronl
Status: ASSIGNED → NEW
Component: User Interface Design → Keyboard Navigation
Updated•23 years ago
|
QA Contact: zach → sairuh
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → Future
Updated•23 years ago
|
Keywords: helpwanted
Comment 4•23 years ago
|
||
*** Bug 117305 has been marked as a duplicate of this bug. ***
Comment 5•23 years ago
|
||
A note. Mac IE 5.1 has a working implementation of this.
Oh, and the incremental search option is better in my opinion...
How about considering the model used by good old vi? In Normal mode (i.e. no
':' prompt) typing /text<enter> moves the insertion point to the next occurrence
of "text". After that, /<enter> moves to the next occurrence.
This has the advantages of dedicating only one key (/) to this functionality,
easy handling of backspaces, and quick and single-handed (at least on US
keyboards) repeated "/<enter>"'s to get to the desired link.
Assignee | ||
Comment 8•22 years ago
|
||
*** This bug has been marked as a duplicate of 30088 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Comment 9•22 years ago
|
||
marking verified as a duplicate.
if you decide to reopen this bug, please clarify why.
search string for bugspam removal: SalviaGuaranitica
Status: RESOLVED → VERIFIED
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
•