Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change event does not fire in IE and Edge under certain circumstances #4672

Closed
iclanzan opened this issue Aug 20, 2015 · 7 comments
Closed

Comments

@iclanzan
Copy link

I have put together this simple example to demonstrate the issue.

The problem is happening on select elements. If there are any mouse event listeners attached that would trigger a render, the onChange handler never gets called.

It looks like unlike other browsers, IE and Edge trigger mouse events on the select element when clicking on the options, but that should not prevent the change event from triggering.

@jimfb
Copy link
Contributor

jimfb commented May 3, 2016

Repro: http://jsfiddle.net/trtz1y99/

@jdalton
Copy link
Contributor

jdalton commented Nov 9, 2016

Chrome and Edge 15 (insider preview) seem to both log MouseUp and Change.

@nhunzaker
Copy link
Contributor

nhunzaker commented Jul 11, 2017

Looks like this is still a problem, so I thought I'd reproduce it on CodePen so that it could be opened in IE11:

https://codepen.io/nhunzaker/pen/OgrRgm

The change event never gets a chance to fire because the dropdown closes

@jasonwilliams
Copy link
Contributor

jasonwilliams commented Jul 12, 2018

change and MouseUp both fire for me in Microsoft Edge 42.17134.1.0 @nhunzaker
Although, the rendering of the select box is weird, it doesn't appear to expand when i click on it

@nhunzaker
Copy link
Contributor

@jasonwilliams We should confirm IE11, but I wonder if we can close this out and focus on the rendering/expansion issue separately.

@jasonwilliams
Copy link
Contributor

jasonwilliams commented Jul 15, 2018

@nhunzaker change and mouseup fire on Internet Explorer 11 too, but the rendering issue is the same as Edge. I think we should close this and open up a new issue for that

@nhunzaker
Copy link
Contributor

Sounds good. I made a quick write up (#13212). Travel and bandwidth issues make it hard for me to look much into this, but we can at least start to talk about it there.

Thanks everyone for weighing in!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants