Kristiyan Kostadinov

The alternate approach broke a bunch of clients, because the first option no longer gets activated after the user filters the list.

I've got the same concern as @jelbourn: it seems like providing the signal would be a bit more code than subscribing to the router events manually and closing the overlay....

Closing since it looks like there hasn't been any activity in a while and the need for the change was unclear.

Closing since this hasn't been touched in a long time.

@elenachiosa this is unlikely to land, however you can try the new `mat-select` implementation from `@angular/material-experimental/mdc-select`. It has the exact same functionality, with the major difference being that we don't...

This change isn't necessary anymore since we no longer have a hardcoded panel height.

@jelbourn isn't that what we're doing [here in `ngAfterContentInit`](https://github.com/angular/material2/blob/master/src/lib/list/selection-list.ts#L384)?

Closing since this is quite out of date and we haven't gotten any bug reports about it as far as I can see.

Cleaning up old PRs and closing this one since it was already possible using DI. As for native dialogs, that's a different issue that we're looking into resolving by using...

I'm closing this since it's pretty breaking and way out of date. We can recreate it if we still think it's a good idea.