I'm submitting a ... (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
When a websocket calls obs.next (in various methods) it will not cause the dom to be updated in IE10.
If I remove the websocket and instead of the observable.create just do a timeout that emits the value like
setTimeout(() => { obs.next('some value'); }, 100)
then things work fine. it is only when the websocket is calling the obs ( or calling a function which calls the obs).
Expected/desired behavior
Expect the websocket.onmessage to cause the dom to reflect new data
Reproduction of the problem
My plnkr doesn't load in IE, but here is the link http://embed.plnkr.co/T3osLgSKOenaMQD1bBmG/
The changeset that reproduces the issue can be seen here
https://github.com/matthewdaniel/angular2-ie10-bug/commit/eaf8a7cef79550d3b0a7c80fc711595b71c6b3da
What is the expected behavior?
In chrome the text will show after 1 second but in IE it doesn't show. However in my app i have something bound to a form element and as soon as I click into that the result shows.
What is the motivation / use case for changing the behavior?
Trying to get a shared list of items to be dynamically updated between concurrent users. User A clicks list item 1 and user B sees it now as being edited.
Please tell us about your environment:
ng new -> brokect is currently at rc.4 - backend doesn't matter since i can reproduce it with echo.websocket.org
- Angular version: 2.0.0-rc.4
- Browser: IE10 IE?
- Language: Typescript
I'm submitting a ... (check one with "x")
Current behavior
When a websocket calls obs.next (in various methods) it will not cause the dom to be updated in IE10.
If I remove the websocket and instead of the observable.create just do a timeout that emits the value like
setTimeout(() => { obs.next('some value'); }, 100)
then things work fine. it is only when the websocket is calling the obs ( or calling a function which calls the obs).
Expected/desired behavior
Expect the websocket.onmessage to cause the dom to reflect new data
Reproduction of the problem
My plnkr doesn't load in IE, but here is the link http://embed.plnkr.co/T3osLgSKOenaMQD1bBmG/
The changeset that reproduces the issue can be seen here
https://github.com/matthewdaniel/angular2-ie10-bug/commit/eaf8a7cef79550d3b0a7c80fc711595b71c6b3da
What is the expected behavior?
In chrome the text will show after 1 second but in IE it doesn't show. However in my app i have something bound to a form element and as soon as I click into that the result shows.
What is the motivation / use case for changing the behavior?
Trying to get a shared list of items to be dynamically updated between concurrent users. User A clicks list item 1 and user B sees it now as being edited.
Please tell us about your environment:
ng new -> brokect is currently at rc.4 - backend doesn't matter since i can reproduce it with echo.websocket.org