601324 - Add Terminal.app-style keyboard shortcuts for changing tabs

Status: RESOLVED WONTFIX

(Camino Graveyard :: Tabbed Browsing, enhancement)

Description

[S Woodside]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.2.12pre) Gecko/20101001 Camino/2.1a1pre (like Firefox/3.6.12pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.2.12pre) Gecko/20101001 Camino/2.1a1pre (like Firefox/3.6.12pre)

I often use Terminal.app and while Camino uses option-command-arrow to switch tabs, Terminal uses shift-command-arrow. It would save me a lot of cursing if Camino supported shift-command-arrow as well.

One issue with this keyboard shortcut is that it's already in use specifically in the case that you are editing text in a textfield, e.g. in a form like this one or the location bar. The possibilities are:

1. Allow shift-command-arrow to change tabs only when text is not being edited (it would have two effects depending on context, so it could be confusing)

2. Have shift-command-arrow always change tabs, and don't allow it's traditional effect in textfields.

3. Don't allow shift-command-arrow to change tabs because it's already sometimes in use and changing it would be bad/confusing.

Based on observing users I find that it's rare to see people use shift-command-arrow while editing text, so eliminating it might not have much of an impact.

Reproducible: Always

Comment 1

[Chris Lawson (gone)]

Please don't file NEW enhancement requests in products you're not actively working on.

You're more than welcome to change tab-switching shortcuts to whatever you wish via System Preferences.

Cmd-Shift-Arrows is a vital text-editing behaviour on Mac OS X from the System 7 days and we're not making it go away.

Comment 2

[S Woodside]

@Chris The Camino home page instructs me to file enhancement requests using the "bug reporting helper". See http://caminobrowser.org/documentation/bugzilla/#feature . It specifically says to "pick “Enhancement” as the severity at the last step.". There is no specification in that document that I must be actively working on the project. If that FAQ does not match the current policy then the FAQ should be changed.

I'm not filing this bug because I can or cannot change that behaviour on my system -- I know I can. I'm filing this because I suspect that there are other uses who experience the same problem.

I've set this re-opened because your objection takes care of case 2 in my request but doesn't deal with case 1.

It is in fact confusing to have to deal with conflicting keyboard shortcuts in different apps, and so dismissing the concept out of hand doesn't seem appropriate. Thanks.

Comment 3

[Chris Lawson (gone)]

You're more than familiar enough with Bugzilla to know that you should be filing enhancements as UNCONFIRMED. I shouldn't be having to tell you this.

We are not changing our keyboard shortcuts for the reasons already outlined in several places. Complain to Apple for being inconsistent, both within their own applications and in comparison to the HIG.

Comment 4

[S Woodside]

There's no way specify whether a bug is filed as NEW or UNCONFIRMED in the "bug reporting helper" at https://bugzilla.mozilla.org/enter_bug.cgi?format=guided&product=Camino ... perhaps you should file a bug against that system so that it will default to UNCONFIRMED. Otherwise you will regularly be getting enhancement requests as NEW since that's what happens when people follow the FAQ.