 | | Re: Search button —David Eaton
|
| | | (...) Actually, I was recently playing with this (using MSIE 5.0, NN 4.05) and I think the results were the same in MSIE and NN: onkeypress: - This performs the function when ANY character is entered, but STOPS the submit if further characters are (...) (25 years ago, 17-Mar-00, to lugnet.admin.general)
|
| | | |
| | | | | Re: Search button —Todd Lehman
|
| | | | | (...) Does that work even if the user has disabled JavaScript? --Todd (25 years ago, 17-Mar-00, to lugnet.admin.general)
|
| | | | | |
| | | | | | | Re: Search button —David Eaton
|
| | | | | | (...) Well, no-- but it certainly doesn't hurt :) DaveE (25 years ago, 17-Mar-00, to lugnet.admin.general)
|
| | | | | | |
| | | | | Re: Search button —Mark Koesel
|
| | | | "David Eaton" <deaton@intdata.com> wrote in message news:FrL7Ln.7vs@lugnet.com... (...) the (...) quickly!). (...) character (...) Yeah, they are basically the same. MSDN claims they are different, but they appear to function identically in IE5. As (...) (25 years ago, 17-Mar-00, to lugnet.admin.general)
|
| | | | |
| | | | | | Re: Search button —David Eaton
|
| | | | (...) something I didn't do, which is to expressly trap for the enter key-- You used "window.event.keyCode", which apparently is different in NN (I looked briefly in O'Reilly's Dynamic HTML-- apparently it's a bit different for each browser, but (...) (25 years ago, 18-Mar-00, to lugnet.admin.general)
|
| | | | |
