Webmaster Forum / HTML, CSS, Scripts / JavaScript / July 2005

The keyboard generates two codes per press for these keys, the first is always 0. For convenience some browsers may
suppress the first code.
I can't test this mod, but unless someone knows a better way, it may be worth a try

function catchkey(e) {

 while(e.keyCode==0)
 ;
 debug(e.type+":"+e.keyCode);
}

--
Stephen Chalmers
547265617375726520627572696564206174204F2E532E207265663A205451323437393134

Mike,

This is apparently a Safari bug which you can easily get around.

function go() {
  document.addEventListener("keydown",catchkey,false);
  document.addEventListener("keyup",catchkey,false);
}

W3C DOM supports two propagation schemes: bubbling and capture. Bubbling
means that an event propagates from the element on which it occured down
the document tree to document root (this is called the bubbling phase -
keyword: BUBBLING_PHASE), then from the document root back to the
element (this is called the capture phase - keyword: CAPTURE_PHASE).

When you specify "false" as third argument for the addEventListener
method, it means that event is propagating by bubbling, thus the event
is doing a round robin. As a consequence, you can catch the event a
first time when it is in the BUBBLING_PHASE, and a second time when it
is in the CAPTURE_PHASE.

In your case, you need to catch the event only once, in BUBBLING_PHASE,
and prevent its further propagation by using method stopPropagation like
this:

function catchkey(e) {
  debug(e.type+":"+e.keyCode);

  e.stopPropagation();
  // Note: for IE, you would use this declaration:
  // window.cancelBubble = true;
}

hih,

JJS.