Open Bug 269306 Opened 20 years ago Updated 2 years ago

use left/right arrow key to move into input element with type=text and textarea element, and out with alt+[/]

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: nian.liu, Unassigned)

References

Details

(Keywords: access, Whiteboard: sunport17)

*** Bug 241160 has been marked as a duplicate of this bug. ***
Depends on: caretnav
Keywords: access, sec508
Whiteboard: sunport17
Blocks: caretnav
No longer depends on: caretnav
In caret mode, and in form control: - ctrl+shift+up goes to just before current form control - ctrl+shift+down goes just after current form control In caret mode, and not in form control: - ctrl+shift+up: not sure whether it should go right before or right after previous form control, or do nothing. For now, nothing is okay. - ctrl+shift+down: not sure whether it should go right before or right after next form control, or do nothing. For now, nothing is okay. In regular mode (not caret browsing): - ctrl+shift+up goes to prev form control - ctrl+shift+down goes to next form control
(In reply to comment #2) > In caret mode, and in form control: > - ctrl+shift+up goes to just before current form control > - ctrl+shift+down goes just after current form control No, if it is a textarea, ctrl+shift+up/down is used for selecting lines. > In regular mode (not caret browsing): > - ctrl+shift+up goes to prev form control > - ctrl+shift+down goes to next form control Why we need these? Tab/Shift+Tab is enough.
(In reply to comment #3) > (In reply to comment #2) > > In caret mode, and in form control: > > - ctrl+shift+up goes to just before current form control > > - ctrl+shift+down goes just after current form control > No, if it is a textarea, ctrl+shift+up/down is used for selecting lines. Ginn, try it. Shift+up and shift+down are used for selecting lines, but ctrl+shift+up/down doesn't do anything. > > In regular mode (not caret browsing): > > - ctrl+shift+up goes to prev form control > > - ctrl+shift+down goes to next form control > Why we need these? > Tab/Shift+Tab is enough. You don't have to implement that now, but it would be nice to have a skip to next form control command. It's currently very difficult to get to the first form control such as a search text field, when there are a lot of navigation links. Opera and various screen readers implement a prev/next form control for this reason.
(In reply to comment #4) > Ginn, try it. Shift+up and shift+down are used for selecting lines, but > ctrl+shift+up/down doesn't do anything. In most of browsers and editors, ctrl+shift+up/down is as same as shift+up/down. Some of them are using ctrl+shift+up/down as selecting paragraphs. > You don't have to implement that now, but it would be nice to have a skip to > next form control command. It's currently very difficult to get to the first > form control such as a search text field, when there are a lot of navigation > links. Opera and various screen readers implement a prev/next form control for > this reason. Sounds reasonable, I know Safari has this feature.
(In reply to comment #5) > In most of browsers and editors, ctrl+shift+up/down is as same as shift+up/down. > Some of them are using ctrl+shift+up/down as selecting paragraphs. Wow. I had no idea about that. I just tried it in wordpad on Windows and you're right. We should file a bug on implementing that. So my top 3 choices are: 1. Ctrl+alt+arrow, if not already used on the Linux desktop 2. Alt+shift+arrow, but leave it for directional navigation when not in caret browsing mode. 3. Home home or End end (press key twice in a row while in a form control). First press works as normal, and second press with no keys or clicks in between moves you to before or after the control.
(In reply to comment #6) > (In reply to comment #5) > > In most of browsers and editors, ctrl+shift+up/down is as same as shift+up/down. > > Some of them are using ctrl+shift+up/down as selecting paragraphs. > Wow. I had no idea about that. I just tried it in wordpad on Windows and you're > right. We should file a bug on implementing that. Already done a while ago: bug 127844.
QA Contact: keyboard.navigation
Component: Keyboard: Navigation → User events and focus handling

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: nian.liu → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.