NOTE: It's over a decade ^(!!) since I wrote this answer. The input event has become ubiquitous, and should be used instead of this hack.

^{What does keydown/keyup even mean for tablet and voice input devices?}

The event handler only sees the content before the change is applied, because the mousedown and input events give you a chance to block the event before it gets to the field.

You can work around this limitation by giving the browser a chance to update the field's contents before grabbing its value - the simplest way is to use a small timeout before checking the value.

A minimal example is:

<input id="e"

    onkeydown="window.setTimeout( function(){ alert(e.value) }, 1)"

    type="text" value="cow" />

This sets a 1ms timeout that should happen after the keypress and keydown handlers have let the control change its value. If your monitor is refreshing at 60fps then you've got 16ms of wiggle room before it lags 2 frames.

A more complete example (which doesn't rely on named access on the Window object would look like:

var e = document.getElementById('e');

var out = document.getElementById('out');



e.addEventListener('input', function(event) {

  window.setTimeout(function() {

    out.value = event.target.value;

  }, 1);

});

<input type=text id=e value=cow>

<input type=text id=out readonly>

When you run the above snippet, try some of the following:

• Put the cursor at the start and type


• Paste some content in the middle of the text box


• Select a bunch of text and type to replace it