>> And how do we make certain what keyCode 122 actually does?
You make a good point. I'd bet, however, for 99% of our users it would
work. So maybe it would be worth the risk to provide the functionality
for the majority.
I'd love to find a better way though, do you have any suggestions? It
is an important usability issue for our users.
Thanks!
On Sep 26, 1:30 pm, Bertilo Wennergren <berti...@gmail.com> wrote:
> ryan.j wrote:
> >> Maybe just a way to have a
> >> button that triggers the F11?
>
> > you could change the event.keyCode of another keypress
>
> > if (e.keyCode==13) { e.keyCode=122; return e.keyCode; }
>
> And how do we make certain what keyCode 122 actually does?
> Such things are configurable. It could mean "quit the browser"
> or "go to the home page" or nothing.
>
> --
> Bertilo Wennergren <http://bertilow.com>
