The onChange event for HTML form elements is fired when the value of that element actually changes in Firefox/Seamonkey, Opera, Safari and any other other modern Web browser. It just makes sense. Yet for some lame reason with Internet Explorer, onChange is only fired once the focus on said form element is lost, effectively making onChange act like some freakish onChange+onBlur hybrid. WTF? I’m just wondering what the design reason that the Internet Explorer team at Microsoft came up with could be, is all.
2 Responses to "onFrustrate"
The M$ design team ran out of crank that day and had to settle for low-grade heroin…
I truly wish M$ would get out of the web browser business if they can’t be bothered to get it right – my development process tends go something like:
1) Develop clients application to run in FF, Opera, Safari, Chrome, Etc.
2) Hack application to make it behave properly in IE.
A workaround is to use ‘onclick’ rather than ‘onchange’. Onlick fires when you would expect it to in IE.
They must have had the good drugs that day.