This project is archived and is in readonly mode.
Change event is fired after blur in IE and we are not normalizing it, this is redonkulous unexpected behavior
Reported by csuwldcat | January 11th, 2011 @ 06:27 PM | in 2.0 (closed)
First off this is an IE browser issue, so MooTools is only guilty of not normalizing here. However, it is a bug that makes you want to punch a baby seal so we should probably mop this shit up foo!
Comments and changes to this ticket
-
csuwldcat January 11th, 2011 @ 06:30 PM
To fix this, set a mouseup event on the appropriate elements (really only radio and checkbox) and have that fire blur. This will cause the change fn to evaluate the state of the element and call the user's fn if it is changed.
-
-
Christoph Pojer February 23rd, 2011 @ 01:18 PM
- State changed from “new” to “hold”
- Milestone set to “1.4.0”
- Milestone order changed from “860” to “0”
What about putting this into More or somewhere else, as additional plugin? :) I'm really not sure we should put such a fix into Core. Maybe 2.0 in a specific IE.js file.
-
Christoph Pojer April 16th, 2011 @ 10:16 AM
- State changed from “hold” to “open”
- Milestone changed from “1.4.0” to “2.0”
- Milestone order changed from “6” to “0”
-
ibolmo January 19th, 2012 @ 09:27 AM
- State changed from “open” to “resolved”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Arian
Christoph Pojer
csuwldcat
ibolmo