Feedback: irt.org FAQ Knowledge Base Q1425

Feedback on: irt.org FAQ Knowledge Base Q1425

Sent by Ed Eddington on September 27, 2000 at 11:03:19: - feedback #1797

Worth:
Worth reading

Comments:
My problem was a related issue:

How to overcome key event unreliability for form fields inside tables with NN4?

http://www.faqts.com/knowledge-base/view.phtml/aid/5491/fid/145/lang/en

Sent by Gilles v/d Hoven on December 19, 2000 at 04:13:33: - feedback #2163

Technical:
Not technical enough

Comments:
This is not quite true;

Windows gives for both the "num-lock enter" and the "return" code 13, but macintosh browsers give for the "num-lock enter" code 3, and for the "return" code 13.

Thought you might find it usefull to know.

Sent by Carl on October 10, 2002 at 10:40:45: - feedback #4210

Worth:
Worth reading

Length:
Just right

Technical:
Just right

Comments:
Hi!

The answer to Q1425 (and Q985) seem wrong to me. When using Netscape 6 on Win98, I always get 0 from e.which when pressing Enter (both when using a text form field and when using a textarea)!

*I'd REALLY like an answer to Q985 that would work in both IE and Netscape...*

Thanks in advance!
/Carl

Sent by Joe Page on January 15, 2003 at 15:22:18: - feedback #4369

Worth:
Worth reading

Comments:
I had trouble with Mozilla since it seemed to have a little of IE and a little of NS in it.

I was able to get Mozilla to work by passing 'event' to the keyPress() function. In IE you can just reference window.event (as this example shows), Mozilla wouldn't work that way.

Here's what I used;

onkeypress="return keyPress(event)"

[here's the js function it calls]

function keyPress(e) {
if (typeof(e) == "undefined") return true;
else if (typeof(e.keyCode) != "undefined") {
if (e.keyCode == 13) {
return doSearch();
}
}
return true;
}

Sorry this isn't very detailed but I was hoping it could be of use to someone