Evgeniy OZ

It can be narrowed even further: https://stackblitz.com/edit/stackblitz-starters-o3eivrnt?devToolsHeight=33&file=src%2Fmain.ts ```ts @Component({ selector: 'my-app', template: ``, imports: [ChildComponent], }) export class App {} @Component({ selector: 'app-child', template: ``, }) export class ChildComponent {...

The workaround is simple: ```ts private readonly injector = inject(Injector); protected readonly displayValue$ = defer(() => toObservable(this.displayValue, { injector: this.injector }).pipe( startWith(null) ) ); ``` https://stackblitz.com/edit/stackblitz-starters-aapwxsuc?file=src%2Fmain.ts

@csisy-bt4w as happens with any cold observable. Use `shareReplay()` if you want multiple subscriptions (and not only in this case).

@csisy-bt4w that's correct!

Forgot to mention: this also causes significant layout shifts and drops the Lighthouse score from 98 to 72. Just one single thing.

@thePunderWoman I will try tomorrow. Just checked if it's not a known issue.

@AndrewKushnir > do you see a different behavior if you remove i18n attributes from elements in your template? no, same behavior. And when I run `ng serve`, it prints this:...

Here is the reproduction: https://stackblitz.com/~/github.com/e-oz/bug-with-i18n You can see that the cat is alive and dead simultaneously for a fraction of a second. Here is the repo: https://github.com/e-oz/bug-with-i18n

This issue is not about app stability. No matter what, both parts of if/else should never be rendered together. > Angular hydration logic on the client identifies that the server-rendered...

#52912 says "Add more info to Angular Hydration warning message when app not stable within 10 seconds" - this issue is surely not about the warning message, and stabilization happens...