Pawel Kozlowski

We can see that this feature request generates lots of interest which means that there are legitimate and common use-cases that are / were not not well supported. I was...

@tiberiuzuld could you please share more details / reproduction scenario? We were briefly looking into it but the types and assigned values don't match thus making the problem confusing. Your...

Thnx for the update @tiberiuzuld - yes indeed, it looks like a valid bug report, thnx!

OK, so the first case is definitively _not_ a bug and works as expected. The second `optionalArrayElement: {a: 'value'}[] = [];` case is more interesting.

@tiberiuzuld could you please update the issue description to remove references to the first case (as this works as intended?)

@markostanimirovic thnx for the additional info. My understanding of the [comment](https://github.com/angular/angular/pull/46709#issuecomment-1174873046) you've mentioned was that it was about `ng.*` public API. The `markDirty` API was always _very_ experimental and _very_...

Note: I can see how it could be confusing but when you write `` Angular has _no way_ of knowing if `my-element-with-a-typo` is a "valid" or "invalid" element name. It...

> Having the same issue when rendering some text with a "ü" character in it to a component attribute. Are you sure it is the same issue??? Please provide a...

This issue is still relevant and it is confirmed bug in the latest version of Angular, see: https://stackblitz.com/edit/angular-ivy-nuc4uz?file=src/app/app.component.ts tl;dr; is that it is all about making non-ASCII characters in Angular...

You are absolutely right - this part of the description is incorrect: > and attaches it to the view container.