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.
Furthermore, if I run the web socket example from the repro in Internet Explorer 11 I get:
Secret payload not found where expected! Zones are not working! :-( <root>
woppa684
changed the title
Websocket messages do not trigger change detection in Internet Explorer
Zone.js does not work in Internet Explorer 11
Sep 29, 2016
woppa684
changed the title
Zone.js does not work in Internet Explorer 11
Zone.js does not work for web sockets in Internet Explorer 11
Sep 29, 2016
When I add "WebSocket" to the "NO_EVENT_TARGET" array it DOES work, so:
var NO_EVENT_TARGET = 'ApplicationCache,EventSource,FileReader,InputMethodContext,MediaController,MessagePort,Node,Performance,SVGElementInstance,SharedWorker,TextTrack,TextTrackCue,TextTrackList,WebKitNamedFlow,Window,Worker,WorkerGlobalScope,XMLHttpRequest,XMLHttpRequestEventTarget,XMLHttpRequestUpload,IDBRequest,IDBOpenDBRequest,IDBDatabase,IDBTransaction,IDBCursor,DBIndex,WebSocket'.split(',');
@vicb Could this be the cause? For now I will patch it like this in our zone.js so we can continue without all the extra detectChanges calls or NgZone.run's ...
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
The text was updated successfully, but these errors were encountered: