W3C home > Mailing lists > Public > wai-xtech@w3.org > July 2007

Re: Keyboard navigation in viewer pane - 3 scenarios.

From: Chris Blouch <cblouch@aol.com>
Date: Tue, 17 Jul 2007 13:40:52 -0400
Message-ID: <469CFF24.9090109@aol.com>
To: chaals@opera.com
CC: Earl Johnson <Earl.Johnson@sun.com>, wai-xtech@w3.org, Tom Wlodkowski <Thomas.Wlodkowski@corp.aol.com>, Becky Gibson <Becky_Gibson@notesdev.ibm.com>

Firefox does allow me to override its own key combinations but even if 
we can doesn't mean we should. If I'm used to control-P being print we 
don't want to suddenly make it "pause audio." That would confuse users 
and break muscle memory for commonly used functions.


chaals@opera.com wrote:
> On Sat, 14 Jul 2007 08:29:08 +0900, Earl Johnson 
> <Earl.Johnson@sun.com> wrote:
>> Hi Chris;
>> My understanding, from a researcch only stance, is all keysequences 
>> can be repurposed in javascript so the browser never sees the keypress.
> ...
>> I assumed a re-purposing function/method similar to this would work 
>> for all since jabvascript, being in the page content, always sees the 
>> keystrokes before the browsxer even.
> Nope, the browser decides to pass the key (or not) which it gets from 
> the OS (or not). The web app only gets it if nobody else has already 
> claimed it - while that is the default it doesn't always happen. 
> Otherwise things like one-handed keyboard drivers would be impossible 
> to write...
> Cheers
> Chaals
> --  Charles McCathieNevile, Opera Software: Standards Group
>   hablo español  -  je parle français  -  jeg lærer norsk
> chaals@opera.com    Catch up: Speed Dial   http://opera.com
Received on Tuesday, 17 July 2007 17:41:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:51:33 UTC