Ted Sander

So it would be simple but there is one problem and that is here: https://github.com/dart-lang/angular_components/blob/860d16150e134ac9cb4c7833d4e15087c96da8c6/lib/material_input/material_auto_suggest_input.dart#L511 As you can see the blur is programatically fired. Before I make the change would...

The architecture of the stepper isn't optional. It actually re-parents the content of a view to the step itself. See warning here: https://github.com/dart-lang/angular_components/blob/c6cb3d783e72ff1ed7974f18b7f169778c73d39b/angular_components/lib/material_stepper/material_step.dart#L14 I don't see us fixing this limitation...

I think I have a solution but I won't be able to implement it for awhile (going on vacation.) A workaround is to set the value on the next turn:...

We are reworking how the button works for the new material design, and it will be backed by a button, but we won't be fixing this for the previous version.

First off thanks for reporting. This code definitely assumes you are only going to change one input at a time which is an invalid assumption. I do think moving to...

The build system doesn't really allow using the !default modifier. Our build system is designed to work with really large projects which means we have the restriction of compiling at...

[value] is the selector for the content of the expansionpanel. I don't see us changing this anytime soon as it is a breaking change, but that is going to conflict...

I think we just wrote a fix for this in the last couple of days. A new release should occur today or early next week. Can you see if the...

Probably going to be awhile before this is fixed. It is very atypical to use a tab panel without any tabs. A simple workaround is to add an *ngIf the...

@zacharydenton I remember there was a UX conversation on this. What was the outcome of that conversation?