Composition: Add keyboard shortcuts for Zoom (Ctrl++, Ctrl+-, Ctrl+0: ux-consistency with message reader), change shortcuts for font size to Ctrl+<, Ctrl+>; result of TB bug 738194

NEW
Unassigned

Status

SeaMonkey
MailNews: Composition
5 years ago
3 years ago

People

(Reporter: Michael Carr, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15.1
Build ID: 20130118191213

Steps to reproduce:

Font Zoom in SeaMonkey Composer behavior changed and 
SeaMonkey documentation no longer correctly documents Font Zoom in Composer.

Specifically, these NO LONGER WORK in SeaMonkey Composer:
o Decrease Font Size
    Ctrl+- (minus sign)
o Increase Font Size
    Ctrl++ (plus sign)

I noticed the change in SeaMonkey Composer a while back and thought it might self-correct, but it didn't--silly me!!!


Actual results:

After research I found the BUG was actually on-purpose change in Thunderbird and I assumed it was 100% carried over into SeaMonkey. 

But that was not the case as ...

ThunderBird COMPOSER changes may have broken SeaMonkey behavior:
here is the reply to my post on the issue (the same bug, but under Thunderbird):

https://bugzilla.mozilla.org/show_bug.cgi?id=738194
--- Comment #50 from :aceman <acelists@atlas.sk> 2013-01-31 06:26:25 PST ---
This bug is for Thunderbird only, so it can stay closed (reopening could make a mess in which patch landed in which TB version). 

*** But I see we could have changed/broken stuff for Seamonkey :(   *** 
I touched the file
editor/ui/locales/en-US/chrome/composer/editorOverlay.dtd 
with the key definitions and that one may be shared. 

*** Please file a separate bug for your report, thanks. ***


Expected results:

TWO BUGS RELATED TO THE IMPLEMENTED ZOOM CHANGES in SeaMonkey COMPOSER:

*** I can only report what happens in WINDOWS version ***

o SeaMonkey 2.15.1 > COMPOSER does not implement:
CTRL+, (aka, CTRL+<) *** does NOT work--PLEASE FIX ***
whereas the following examples all work as per new expectations (at least in Thunderbird and I assume also meant for SeaMonkey):
CTRL+. (aka, CTRL+>) works fine
CTRL+SHIFT+, (aka, CTRL+SHIFT+<) works fine
CTRL+SHIFT+. (aka, CTRL+SHIFT+>) works fine
CTRL++ does not work--I guess this is the new way things are
CTRL+- does not work--I guess this is the new way things are

o SeaMonkey 2.15.1 HELP > COMPOSER SHORTCUTS > contains OUTDATED DOCUMENTATION (that wastes a lot of time for folks like me who look at HELP before filing BUG reports):
Decrease Font Size
    Ctrl+- (minus sign)
    Cmd+- (minus sign)
    Ctrl+- (minus sign)
Increase Font Size
    Ctrl++ (plus sign)
    Cmd++ (plus sign)
    Ctrl++ (plus sign)

Comment 1

5 years ago
Confirming problem, either shortcuts or documentation must be changed (first preferable, imo)
Status: UNCONFIRMED → NEW
Depends on: 738194
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
Version: SeaMonkey 2.15 Branch → Trunk
Now that the keyboard shortcuts CTRL+> and CTRL+< are taken, it breaks my Addon Zombie keys - is there any way to disable these with about:config? What would be the general advice for Addon authors who absolutely depend on keyboard shortcuts - is there a way to disable built in ones at run time?

Comment 3

4 years ago
(In reply to Axel Grude [:realRaven] from comment #2)
> Now that the keyboard shortcuts CTRL+> and CTRL+< are taken, it breaks my
> Addon Zombie keys - is there any way to disable these with about:config?
> What would be the general advice for Addon authors who absolutely depend on
> keyboard shortcuts - is there a way to disable built in ones at run time?

You could try Keyconfig. Several addons also package the Keyconfig core files as well.
Component: Composer → MailNews: Composition

Comment 4

3 years ago
Where can I write when in GERMAN SeaMonkey the keyboard-shortcuts are not working correctly or one letter is given to 2 functions?
One Example: In mails [ALT+A] is for "Ansicht" (View) AND "Anhänge" (attachments).
You need to log in before you can comment on or make changes to this bug.