Kristiyan Kostadinov

Note: I ran an initial TGP for this and it broke a bunch of targets. It likely introduced a behavior change somewhere.

Closing since I'm approaching removing the mixin functions differently.

Each component on the docs site has one live example showing how to use its harness. Here's the one for the autocomplete: https://material.angular.io/components/autocomplete/examples#autocomplete-harness. There's also a "Testing" section in the...

If we put everything in a `dialog` element, my understanding is that the browser will present it as a dialog to assistive technology. Most of our overlay-based components use patterns...

Yes, this is working as expected. The idea was to mimic the behavior of the native `select` and `option` elements with `mat-select` and `mat-option`.

You still have the ability to control what the trigger looks like using the `mat-select-trigger` element. There's a live example in the docs: https://material.angular.io/components/select/examples#select-custom-trigger

Alright, I'll reopen the issue but it's worth noting that there are other use cases that need to be considered. E.g. if we were to match the reset option to...

> If the list of mat-options contains an "empty" value, than that initial/blank state doesn't make sense to begin with. So they shouldn't be able to get to it from...

Blocked on the new API being available in g3 and existing users being migrated.

Giving this a lower priority, because the idea is that you'd use either the `value` or a `FormControl`/`ngModel`, not both.