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

Re: Keyboard navigation in viewer pane - 3 scenarios.

From: earl johnson <Earl.Johnson@Sun.COM>
Date: Mon, 16 Jul 2007 10:17:36 -0700
To: wai-xtech@w3.org
Message-id: <469BA830.2070708@sun.com>

Bummer but thanks Charles.

This makes it sound like there is no way to guarantee browser and 
desktop component key sequences can be harmonized when the browser or 
desktop have already claimed them for another use. Is this correct or is 
there some other way to tell the browser and desktop "send these 
keystrokes to the web component for its use instead of claiming them"?

Earl

btw - it's probably clear now but the research mentioned below was all 
"book" based, not prototype testing.


Charles McCathieNevile 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 Monday, 16 July 2007 17:15:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:15:43 GMT