Re: Keyboard navigation in viewer pane - 3 scenarios.

Thanks Chris!

An fyi from the engineer I'm working with on this:

 > Here is a link that suggests it's possible to prevent the browser from
 > displaying the print dialog.
 >
 >     http://ims.co.nz/blog/archive/2006/06/13/1823.aspx
 >
 > In my own testing, I'm able to listen for the ctr-p key code. However, I
 > have not been successful in preventing the browser from displaying the
 > dialog. That doesn't mean this is not doable, I just haven't figured it
 > out.
 >

Earl


Chris Blouch wrote:
> 
> 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.
> 
> CB
> 
> 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 Thursday, 19 July 2007 15:49:19 UTC