onchange is actually onblur

[10 weber]

After changing an input's value, a function should be triggered:accuracy: <input type="text" value="25" onchange="someFunction()" />pxbut instead, the function takes place after the input was blurred.

[jeffman]

I'm not sure if this is a question or not, but I'll comment. The change event for a text element is only fired when the focus moves away from the element and the content has changed. Otherwise, it would fire with every keystroke. Since you can trap keystrokes with keydown and keypress, I guess the designers figured it would be also useful to know when the user has committed himself to a change. So that's the change event.

[10 weber]

I'm not sure if this is a question or not, but I'll comment. The change event for a text element is only fired when the focus moves away from the element and the content has changed. Otherwise, it would fire with every keystroke. Since you can trap keystrokes with keydown and keypress, I guess the designers figured it would be also useful to know when the user has committed himself to a change. So that's the change event.

An embarrassing mistake... Thanks!

[jeffman]

Not embarrassing. I suspect most of us have pondered this particular issue at one time or another. It's not exactly intuitive.

[wirehopper]

If the input is changed, then the original value was restored, onchange doesn't fire, but onblur would.