320161 - Tab move shortcuts breaks Back/Fwd/Home on Mac

Status: RESOLVED DUPLICATE of bug 321128

(SeaMonkey :: UI Design, defect)

Description

[Stefan [:stefanh]]

Bug 105885 introduced the shortcuts Cmd+left/right/home for moving tabs. Those are used for navigate Back/Forward/Home on mac. It also seems that the tab move shortcuts takes precedence even if no tab is open (probably since they're in navigator.xul). This differs with toolkits version, where the same shortcuts also are used for navigate Back/Fwd and moving tab left/right.

I would expect Cmd+left/right navigate back/fwd if no tab is open. Since mac users actually have three different ways of moving Back/Fwd, the major issue here is Cmd+Home. One  possible solution might be to use Opt (that's Alt)+Home for navigating home (like Firefox).

Comment 1

[Ian Neal]

Jag mentioned this in https://bugzilla.mozilla.org/show_bug.cgi?id=105885#c119 except for windows where Ctrl+left/right/home do something different to what they used to. I'm probably used to how they are used in word :-S

Comment 2

[[e-mail]]

Alternatively we could switch the keys to Ctrl+Arrow, if they don't actually work on the Mac it's not a big loss as they're such big mouse users ;-)

Comment 3

[jag (Peter Annema)]

How about we move where we listen for the shortcuts so that they only work in the tab strip, like Firefox does?

Comment 4

[Robert Kaiser]

Beta is frozen, and the problem here is only that some shortcut keys are different than before, so not blocking Beta for that. As it could be considered a worthwile polish/regression fix, moving nomination to Final.

Comment 5

[moz]

This is a bug that causes a lot, a lot of confusion (at least to the users in windows). 

If you are in a page and use Ctrl+Home you expect to go to the beginning of the page/document (like in Mozilla Composer, Notepad, Word, Excel, Acrobat Reader and so many other programs). 

But now in Seamonkey 1.0beta the user sees he remains in the same place, and later sees that the tabs have changed!. Please, Ctrl+Home, Ctrl+End, Ctrl+Left, Ctrl+Right and so on are heavily used in a lot of applications (including Mozilla Composer), it's a great help to users to leave it as it always has been in Seamonkey, Mozilla, Netscape... and assign it to some unused keys.

P.S. As it has been talked in this bug about keys in windows, it seems a good idea to change the description of this bug to something more general.

Comment 6

[Stefan [:stefanh]]

(In reply to comment #5)
> This is a bug that causes a lot, a lot of confusion (at least to the users in
> windows). 
> If you are in a page and use Ctrl+Home you expect to go to the beginning of the
> page/document (like in Mozilla Composer, Notepad, Word, Excel, Acrobat Reader
> and so many other programs). 
> But now in Seamonkey 1.0beta the user sees he remains in the same place, and
> later sees that the tabs have changed!. Please, Ctrl+Home, Ctrl+End, Ctrl+Left,
> Ctrl+Right and so on are heavily used in a lot of applications (including
> Mozilla Composer), it's a great help to users to leave it as it always has been
> in Seamonkey, Mozilla, Netscape... and assign it to some unused keys.
> P.S. As it has been talked in this bug about keys in windows, it seems a good
> idea to change the description of this bug to something more general.

Please file a new bug about that - this bug is filed because the tab move shortcuts breaks browser Back/Fwd/Home navigation on mac.

Comment 7

[Karsten Düsterloh]

I filed bug 321128 on the Windows/KDE shortcut key issue.

Comment 8

[Stefan [:stefanh]]

*** Bug 321136 has been marked as a duplicate of this bug. ***

Comment 9

[Stefan [:stefanh]]

FYI, the patch in bug 321128 should fix this.

Comment 10

[Not interested in Mozilla any more]

This definitely needs fixing. Changing something this major dramatically affects how people use SeaMonkey. Also, I can't see why anyone would want to change the display order of tabs using the keyboard. It's such an infrequent thing to want to do it doesn't deserve a keyboard shortcut, and even it it has one it should not steal it from an existing standard. I've only used 1.8b for about a week and it's already driving me mad.

Comment 11

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

Duping to bug 321128 since the changes there will solve this, and so people can see that SM1.0 final will not ship with the bug.

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