Closed Bug 70140 Opened 23 years ago Closed 23 years ago

if no shortcut with shift is found, look for the same shortcut without shift

Categories

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

x86
Windows 98
defect

Tracking

()

VERIFIED WONTFIX
Future

People

(Reporter: jruderman, Assigned: alecf)

Details

(Keywords: helpwanted)

Jag tells me that to make Ctrl++ work on Windows (increase font size), he would 
have to define Ctrl+Shift++ (for + above =) and Ctrl++ (for the numeric 
keypad).  Currently only Ctrl+= works.

Also, in composer, Ctrl+B doesn't work if Shift is held down.  It works fine in 
wordpad and most other Windows apps that define Ctrl+B but don't define 
Ctrl+Shift+B.

If Mozilla gets a keyboard shortcut with shift in it but doesn't see a binding 
for it, it should try the same shortcut without shift.  This would partially 
solve the problem of Ctrl+(puntuation) being hard to internationalize and would 
make Mozilla's behavior closer to that of other Windows apps.
futuring... anyone feel free to take this
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → Future
A more general solution is bug 70630, "reduce keybindings by allowing modifiers 
to be ignored".
This bug seems bogus to me; we should definitely *NOT* ignore a keybinding 
modifier in all situations (such as shift).

Control-B *should* be distinguishable from Control-Shift-B.  WordPad sounds 
broken to me.

The problem of Control-+ vs Control-= on Windows sounds like a platform problem.

As for bug #70630, that might be a solution (when implemented) for the +/= issue 
on Windows but it isn't meant to reduce the number of keybindings available.

AlecF--I hope you don't mind, I'm resolving this as WONTFIX.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
v
Status: RESOLVED → VERIFIED
See also bug 139106, "Cannot switch tabs with CTRL or ALT or SHIFT pressed".
no, that's not the same - from an implementation point of view, modifiers +
mouse is different than modifiers + keybindings - disregard that last comment.
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.