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
{{ message }}
This repository was archived by the owner on Feb 26, 2024. It is now read-only.
First of all, this is duplicate of angular/angular#10350 but I thought this location might be more appropriate. I think that a websocket message is not automatically ran in the Angular zone in internet explorer.
Run the plnkr below in chrome for example and clicking the button wil nicely increment the message. Running this in IE you will see that the update in the view lags 1 message behind (check with the message in the console). In our current applications we have to manually do a zone.run (see also the commented lines in the plnkr) to trigger change detection while in the other browsers this is not needed.
First of all, this is duplicate of angular/angular#10350 but I thought this location might be more appropriate. I think that a websocket message is not automatically ran in the Angular zone in internet explorer.
Run the plnkr below in chrome for example and clicking the button wil nicely increment the message. Running this in IE you will see that the update in the view lags 1 message behind (check with the message in the console). In our current applications we have to manually do a zone.run (see also the commented lines in the plnkr) to trigger change detection while in the other browsers this is not needed.
http://plnkr.co/edit/ANsjSo27QldcInUXRlV2?p=preview