By clicking “Sign up for GitHub”, you agree to our terms of service and

I made this fiddle with a little more info on event order, and the fix should still work with keyboard use as well. To work with jQuery Datepicker onchange(), use the datepicker onSelect event.This will show which date we added currently and changed to. It also discusses a feature detect that could be adapted to check for the change event.

This is not a bug, this is just how the event model works. GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together. I haven't been able to find any official bug reports, but a similar issue is discussed on StackOverflow. // Pointer events in IE10, IE11 can be handled as mousedown. Assigning to the DOM .value property doesn't fire a change event either, so this isn't specific to jQuery and doesn't need jQuery documentation. Should these inconsistencies in .prop(), the change event and the :checked pseudo selector be fixed in the jQuery core, or would you prefer to see plugins provide a patch/workaround here? It is possible to work arround this issue by manually firing the change event for indeterminate input elements.

Example. This event is limited to elements,