question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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:closed
  • Created 4 years ago
  • Comments:6 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
JiaLiPassioncommented, Apr 9, 2019

I will check it, thanks!

0reactions
angular-automatic-lock-bot[bot]commented, Sep 19, 2019

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Angular - Custom Elements not working on Firefox & Microsoft ...
Angular custom elements does not support IE. Here is a workaround to Customize Angular 4+ App Bootstrap and have it support with IE....
Read more >
Angular ngFor - Learn All Features, Not Only For Arrays
Let's learn a ton of hidden ngFor features that are not often mentioned, but mot of all we are going to learn how...
Read more >
angular/angular - Gitter
Hi. I'm trying to target the Shadow DOM element created by the Angular Materials menu item but I'm having some trouble and have...
Read more >
UNPKG - @angular/core
On IE the function doesn't have its own `name` property, but it takes it from. 439, // the lowest level in the prototype...
Read more >
Custom Elements & Shadow DOM with Angular 8|7 - Morioh
Angular makes it easy to work with custom elements and shadow DOM by providing an easy to use API on top of the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found