|
|
On Fri, 7 Oct 2005 13:28:39 +0000 (UTC), Matthew Winn
<o*@matthewwinn.me.urk> wrote:
>On Fri, 07 Oct 2005 14:54:41 +0200, Tim Altman <do.not@xxxxxxxxxxxxxxx> wrote:
>> On Wed, 05 Oct 2005 13:14:46 -0400, John Chambers <jcsd@xxxxxxxxxxxxx>
>> wrote:
>> >OTOH, in my short time with opera, most of the differences I've seen are
>> >rather petty. For example, on my Mac, all the other 7 browsers I have
>> >use CMD-N to open a new window. With opera, this opens a new tab, which
>> >is CMD-T in all the others. To get a new window you type Shift-CMD-N.
>>
>> We've actually had quite a bit of discussion about these keyboard
>> shortcuts internally. While CMD-T would be more compatible with other
>> browsers, CMD-N makes more sense considering the conventions of OS X.
>> Unfortunately, we'll probably cave and change the shortcut at some
>> point because other browsers made bad choices with their shortcuts.
>> CMD-T is already mapped to another function in Opera, so we'll have to
>> move that, too. Of course, that'll cause an uproar among current
>> users familiar with that shortcut. But what's a minority browser to
>> do? :)
>
>Can't you ship two or three keyboard mapping files with Opera? One
>Opera standard mapping (used as the default), one that's designed
>around IE's shortcuts, and so on? Then users who need to switch
>between browsers frequently can easily change their default Opera
>shortcuts to a set that causes fewer "which browser am I in?" errors.
Yes, we can, but it's already "easy" enough for users to remap the
problematic shortcuts.
--
Tim Altman
Core QA
Opera Software
Remove NO SPAM from e-mail address to reply
|
|