i thing you're right for what it's worth, but the OP wanted methods of
doing it.

whether he chooses to slavishly follow WAI guidelines or make his
entire site dependant on the user not having changed their browser's
default configuration is between him and the client. if he's
developing for a project used internally (like a webapp, rather than a
site) it matters less that somebody running lynx can't use the app.

On Sep 26, 9: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>

Reply via email to