Matthieu Riegler

The scrolling looks broken. ex: https://ng-dev-previews-fw--pr-angular-angular-58610-adev-prev-undk8pcw.web.app/api/router/Router#events If you click on `events`, it scrolls down to the bottom of the page.

You're right the demo doesn't exihibit the issue anymore. Maybe I was hitting the cache.

The text should be updated to match the code example. Signals are the way to go today.

Fwiw, we've updated this tutorial : https://next.angular.dev/tutorials/first-app/05-inputs As a more general topic, we indeed want to improve the learning story around signals and rework a bit the learn-angular tutorial. https://next.angular.dev/tutorials/learn-angular

The change should be done in the other direction. Explaining the usage of the signal input.

@abhideepd Do you intend to do the required change ?

If you inject `ElementRef` in your directive you'll get access to the host element.

Can you share more on what exact use case you're trying to address ?

There are legit breakages in G3, some projects extend the `AsyncPipe`.

@tjlav5 fwiw, extending is not part of our public API policy. https://github.com/angular/angular/blob/6d3849ffc85cc52b0eba3836b24f10895621acbe/contributing-docs/public-api-surface.md?plain=1#L55-L59 Your alternative seems interesting though !