Miles Malerba

The stackblitz does not appear to be set up correctly. The `` needs a `matChipInputFor` directive rather than a `matInput` directive (see: https://material.angular.io/components/chips/overview). I also don't think setting a `formControl`...

Hmm interesting. I made an expanded example that shows this working with other combinations of input and autocomplete but failing for chips + autocomplete. It must be some kind of...

I'm not sure using the same styles as selected & today makes sense. What happens then when today is selected & focused?

I think we decided to name our `@Output()`s across the library as `*Change` in order to work with 2-way binding syntax. It does seem like probably a bug that this...

@zarend I definitely want to look into the strange a11y behavior you're seeing, but I'll do it in a followup PR

I think maybe there are multiple things being asked for in this issue: 1. Setting the core angular material typography styles (for things like mat-option) should be down with `mat.core-theme($theme)`...

I'm not sure we want to make this change, because it just adds more complexity to our API surface. I understand that passing an empty component might not feel like...

There are plans in the works to put `afterNextRender` back outside the zone, so this may wind up not being needed

We changed `define-theme` to always derive the secondary palette from the secondary palette. This is because the M3 spec itself seems to assume that the secondary color is basically a...

@gabynevada Yes exactly, rather than automatically getting the CSS for every color variant of every component (as we got with M2, or by using the `color-variants-back-compat` mixin), it is preferable...