You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using IE 11 if one has an input component with a placeholder attribute and an onChange handler, the onChange handler will be called when clicking the input without typing anything in, just clicking it.
I made a reproducible case in codepen here: http://codepen.io/anon/pen/BoGQyZ If one opens it in IE and look in the console and clicks the input with the placeholder they should see an event from the onChange handler.
It seems to be a known issue that Microsoft is unwilling to fix. However if one of React's goals is to normalize the onChange event as the documentation implies this needs a workaround. One possible solution would be to check if the input that triggered an input event is focused at the moment.
The text was updated successfully, but these errors were encountered:
@jimfb I think it makes sense to normalize it, but unless we solve all of these problems then it seems kind of fruitless... and last I checked solving entirely in the event system didn't seem realistic. So that leaves solving it inside a wrapper-component which is trivial but would leave out the DOM bubbling (relying on that is a bad idea IMHO, but people do it), but it's trivial and safe to implement this wrapper-component yourself, so it doesn't seem very high priority to me.
Using IE 11 if one has an
input
component with aplaceholder
attribute and anonChange
handler, the onChange handler will be called when clicking the input without typing anything in, just clicking it.I made a reproducible case in codepen here: http://codepen.io/anon/pen/BoGQyZ If one opens it in IE and look in the console and clicks the input with the placeholder they should see an event from the
onChange
handler.It seems to be a known issue that Microsoft is unwilling to fix. However if one of React's goals is to normalize the onChange event as the documentation implies this needs a workaround. One possible solution would be to check if the input that triggered an
input
event is focused at the moment.The text was updated successfully, but these errors were encountered: