jhm wrote:
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
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
ryan.j wrote:
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.
Does
you could throw in some browser/OS detection easily enough, but i
already agree it's not a good idea so i don't really want to end up
arguing in it's favour! ;-)
unless the client insisted on a particular method, i would (and in the
past have) gone with this page looks best full-screen, in most
you used to be able to use an activex control to simulate an F11
keypress in IE, but i honestly don't know if it still works. it's
likely to trigger a yellowbar prompt in IE these days anyway. you can
open a new window without any toolbar, statusbar etc with plain old
window.open
ryan.j wrote:
Or you could jsut have the
text best viewed fullscreen. press F11 for fullscreen or whatever if
the window res is below a certain value.
Preferable not. You can't really know which key or key combination
gives fullscreen. A lot of the time it's F11, at the present, but
it could
i think it's generally better to let users configure their own browsers ;)
I agree. This would be in response to something the user clicks
indicating they want a full-screen view temporarily. Getting rid of
all the browser toolbars, menus, etc. Maybe just a way to have a
button that triggers
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; }
On Sep 26, 8:36 pm, jhm jmay...@gmail.com wrote:
i think it's generally better to let users configure their own browsers
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
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
10 matches
Mail list logo
