Open Bug 100959 Opened 23 years ago Updated 2 years ago

many functions not available for keybinding

Categories

(Core :: DOM: UI Events & Focus Handling, enhancement, P5)

enhancement

Tracking

()

Future

People

(Reporter: krooger, Unassigned)

Details

(Keywords: access, helpwanted)

I want to bind other keys to the same functions as SHIFT-ArrowKey and Control-r
are bound to; unfortunately this seems hardwired in.

Wasn't the promise of XUL and using XML that everything there was currently a
button, menu item, or key combination for in mozilla could also be accessed by
user specified keystrokes, buttons, menu items, etc?
Summary: many functions not customizable → many functions not available for keybinding
I want to bind other keys to the same functions as SHIFT-ArrowKey and Control-r
are bound to; unfortunately these keybindings are hardwired and the functions
they are bound to aren't available in a form I can bind to button clicks and
keystroke combinations.

Wasn't the promise of XUL and using XML that everything there was currently a
button, menu item, or key combination for in mozilla could also be accessed by
user specified keystrokes, buttons, menu items, etc?

Component: Browser-General → User Interface Design
->Keyboard Navigation (sorry)
Component: User Interface Design → Keyboard Navigation
reassign
Assignee: asa → aaronl
QA Contact: doronr → sairuh
So, are you looking for a UI for rebinding keys?
No.  The UI is already there; it just has gaps.  For instance, the following
patch already gets me 50% of where I want to be:

--- mozilla/res/builtin/htmlBindings.xml        Thu Jul  5 19:01:33 2001
+++ mozilla/res/builtin/htmlBindings.xml        Wed Sep 26 12:21:00 2001
@@ -31,8 +31,15 @@
       </handler>

+      <handler event="keypress" key="+" command="cmd_scrollPageDown" />
+      <handler event="keypress" key="-" command="cmd_scrollPageUp" />
       <handler event="keypress" key=" " command="cmd_scrollPageDown" />
-      <handler event="keypress" keycode="VK_PAGE_UP" command="cmd_scrollPageUp" />
+      <handler event="keypress" keycode="VK_BACK" command="cmd_scrollPageUp" />
       <handler event="keypress" keycode="VK_PAGE_DOWN"
command="cmd_scrollPageDown" />
+      <handler event="keypress" keycode="VK_PAGE_UP" command="cmd_scrollPageUp" />

+      <handler event="keypress" key="k" command="cmd_scrollLineUp" />
+      <handler event="keypress" key="j" command="cmd_scrollLineDown" />
+      <handler event="keypress" key="h" command="cmd_scrollLeft" />
+      <handler event="keypress" key="l" command="cmd_scrollRight" />
       <handler event="keypress" keycode="VK_UP" command="cmd_scrollLineUp" />
       <handler event="keypress" keycode="VK_DOWN" command="cmd_scrollLineDown" />
Marking NEW
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: access, patch, review
Priority: -- → P5
Target Milestone: --- → mozilla0.9.5
-> trudelle, for reassignment
Assignee: aaronl → trudelle
Why did this have patch/review keywords?  The patch referenced does not appear
to fix this bug.  Also, major severity is clearly wrong, this is an enhancement
request. updating these fields, marking future/helpwanted.
Severity: major → enhancement
Keywords: patch, reviewhelpwanted
Target Milestone: mozilla0.9.5 → Future
Also it seems that many function are not available for xbl binding for customize
keybinding. Like open new windows, close tabs... I saw that both xul and xbl
files to implement the same functions independently. If most common functions
(the ones that already has default bindings) are all like  "cmd_scrollLineDown"
that can be called everywhere, then customize key binding will be much easier
and with less duplicated codes. Currently, all I can do is rebind scroll page
functions to "hjkl", needless to say, not very useful.

Maybe it is also an opportunity to collect all or most keybinding functions into
one place.

Oh, the original bug report seems to be not updated with the current situation
anymore. we can use XBL to bind keys. But the available global commands are not
documented and limited.
Question to bug Filler: would fixing this bug allow me, for instance, to assign a key combination to the File->Send Page option that currently has no keystroke assigned to it? (I use SeaMonkey ex-Mozilla Suite, but I guess the same option is available in FF)
QA Contact: bugzilla → keyboard.navigation
Component: Keyboard: Navigation → User events and focus handling

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.

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