Repository navigation
May be a bug when manually trigger change detection after Worker.onmessage #14027
Description
I'm submitting a bug report
Current behavior
This is my question in stackoverflow
I create a plunker demo here
I use three methods to trigger change detection, and ApplicationRef.tick() and ChangeDetectorRef.detectChanges() does not work well.
Expected behavior
In the demo, after add a tab, and click the list, the background should change
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
use angular material tab group
Please tell us about your environment:
windows10 enterprise
VS Code
npm lite-server
- Angular version: 2.2.0
- Browser: [Chrome ]
-
Language: [ TypeScript 2.1 ]
-
Node (for AoT issues):
node --version= 6.9.4
Reacted by lmz, Tero Parviainen and Leng.Jryun
Activity
LiuMengzhou commentedon Jan 20, 2017
666
teropa commentedon Feb 28, 2017
I'm also seeing this. The accepted answer to the Stack Overflow question states:
This seems to be true, except that there's nothing obvious about it to me. If this is by design, I think it needs to be addressed in documentation.
starDustZhi commentedon Mar 10, 2017
It is true that worker.onmessage is not covered by NgZone.
BUT after I trigger change detection in another way, the thing is wired.
I have created a plunker demo here
JiaLiPassion commentedon May 28, 2020
Worker.onmessage should be patched with the latest version, will close this for now.
Dassderdie commentedon May 29, 2020
@JiaLiPassion
What is the latest version in this context? I just had a few very confusing hours debugging this until I stumbled over this issue. I'm using
[email protected]and[email protected]...angular-automatic-lock-bot commentedon Jul 1, 2020
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
JiaLiPassion commentedon Jul 1, 2020
@Dassderdie ,
Worker.onmessageis patched several versions ago, so the0.10.3should work, if not , could you create a new issue? thanks.