ngFor over complex data does not work for custom-elements in IE and Edge (freeze)
See original GitHub issue🐞 bug report
Affected Package
@angular/core
Is this a regression?
Not testet in older Version
Description
If you iterate over a complex array (array consisting of Objects) on an custom-element with *ngFor and the custom element deffers a render/update in a task or microtask angular freezes on IE11 and Edge. If you iterate over an array of basic-types everything works fine.
🔬 Minimal Reproduction
Repository to reproduce: https://github.com/mzeiher/ngFor-custom-element-bug
Custom Elements defined here (one which renders directly, one defers render to a microtask, one defers render to a setTimeout): https://github.com/mzeiher/ngFor-custom-element-bug/blob/master/src/app/app.component.ts
Angular Template: https://github.com/mzeiher/ngFor-custom-element-bug/blob/master/src/app/app.component.html
just run npm start
, un-comment line 5 and 6 in app.component.html
and startup Edge or Internet Explorer 11. The page freezes, looks like the renderer is stuck in an endless loop (if the render is defered to a microtask the browser obviously freezes, if defered to a setTimeout the render just re-renders in an endless loop)
🔥 Exception or Error
IE11 and Edge freeze, renderer stuck in endless loop
🌍 Your Environment
Angular Version:
Angular CLI: 7.3.6
Node: 11.12.0
OS: win32 x64
Angular: 7.2.10
Source code is ES5, @webcomponents/webcomponentsjs polyfill is loaded for Edge and IE
If you need more code sample just let me know it.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
I will check it, thanks!
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.