I am sorry for a super vague description, but unfortunately this is the best I can do.
We have upgraded Ember (+cli) from 2.10 to 2.13.3 and we started using ember-cli-babili instead of ember-cli-uglify. All browsers seem to have been doing just fine, but IE 11 would not trigger any events to the Ember components. The Ember application would boot up just fine and render with no issues, the cursor and CSS would change with hover events, but no hover event would be sent to a component. Same with clicks - clicks would not trigger actions and clicks on link-to components would just refresh the page because the browser would be just clicking a link with no JS handler.
This situation would happen about 95% of the time. The remaining 5% everything would be ok. This leads me to a suspicion that there might be some race condition, but I am not sure what it could be.
I am sorry for a super vague description, but unfortunately this is the best I can do.
We have upgraded Ember (+cli) from 2.10 to 2.13.3 and we started using ember-cli-babili instead of ember-cli-uglify. All browsers seem to have been doing just fine, but IE 11 would not trigger any events to the Ember components. The Ember application would boot up just fine and render with no issues, the cursor and CSS would change with hover events, but no hover event would be sent to a component. Same with clicks - clicks would not trigger actions and clicks on link-to components would just refresh the page because the browser would be just clicking a link with no JS handler.
This situation would happen about 95% of the time. The remaining 5% everything would be ok. This leads me to a suspicion that there might be some race condition, but I am not sure what it could be.
Again, I am sorry for the lack of information.