176900 - Command plus numeric keypad plus key doesn't increase font size

Status: VERIFIED DUPLICATE of bug 153836

(Camino Graveyard :: Accessibility, defect)

Description

[Ben Rosengart]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021026 Chimera/0.5+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021026 Chimera/0.5+

Chimera uses command-= to increase font size.  Mozilla and OmniWeb both use
command-+.  Chimera should change to the de facto platform standard.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Greg K.]

Mozilla doesn't use command-plus. It uses command-=. Using command-plus would
require using command-shift-=. There is no "de facto platform standard."

Comment 2

[Ben Rosengart]

There is a plus on the number pad that doesn't require shift.  This is what
I've been using.

Ok, I tested OmniWeb and Mozilla and here's the deal: Mozilla accepts either one,
OmniWeb only accepts plus.  And Chimera, as we know, only accepts the equals sign.

I would be awfully pleased if Chimera accepted both, as Mozilla does.

Comment 3

[Greg K.]

Confirmed using Chimera/2002102704 on 10.1.5. Command+(numeric keypad plus)
doesn't increase font size, though it does in Mozilla (and the numeric keypad
minus key works, obviously since it's the same character as the hyphen key).

Revising summary and reassigning to Accessibility.

Comment 4

[Simon Fraser [no longer active]]

We rely on Cocoa's shortcut key matching for these keys. We need to write some
code to catch the keypad keys.

Comment 5

[Ludovic Hirlimann [:Usul]]

Confirming with 2003082402.

Comment 6

[Samuel Sidler (old account; do not CC)]

Font sizes should increase with both command+(+) and command+(=) on the keypad
as Mozilla does.

I'm sure this is easy enough for 1.0 as it's just a matter of catching the key
command.

Targeting for 1.0, adding Wevah to CC (can you take this?).

Comment 7

[Wevah (Nate Weaver)]

This is already fixed, and it's a dupe. Woohoo!

*** This bug has been marked as a duplicate of 153836 ***