Here is a list of changes that will be in future release.
This release needs some time and I will wrote what have done and not.
The list will be updated while I will add new features.
You can propose new features right now or give refs to another popular issues\ideas for forms components.
<MatAutoComplete @bind-Value="Val">
<MatOption Value="Ananas">Ananas</MatOption>
<MatOption Value="Banana">Banana</MatOption>
<MatOption Value="Apple">Apple</MatOption>
</MatAutoComplete>
[x] JS API
[ ] MatMenu add full binding style open mode
@sandrohanea, @dga711 Hi! You make a lot for MatAutoComplete. Can you say what you think about my plans?
If datepicker could still pick time in the new version, that would be great.
However, would it be better for 2.0 forms if it's an standalone component, so we have MatDatetimepicker, MatDatepicker and MatTimepicker components?
Perhaps there would also be a good idea to add MatTable to the list as well, since it need some rework as well?
Would it be possible to get Minimum Date and Maximum Date added to the DatePicker component?
If it's still based on flatpickr, I think they do have the option of setting max and min.
please consider adding keyboard navigation support . for example, using the "tab" key, a user should be able to move from one item to another within a list component, and using the "shift-tab" keys combo, navigate the same items in the opposite direction. thanks!
Add Date range Picker with open calendar.
Add the date picker inline function
Hi. Thanks for the great work. Please, consider adding a multi select component that allows selection of multiple items from a select list. I suggest MatMultiselect as a name.
Please add Autofocus property for input and SetFocus method.
Thanks for your work
please consider adding keyboard navigation support . for example, using the "tab" key, a user should be able to move from one item to another within a list component, and using the "shift-tab" keys combo, navigate the same items in the opposite direction. thanks!
Maybe add TabIndex property to form elements. Would be useful in multi-columns forms.
Mat Table default row count change into 10 and the width of the last column is too large
If MatAutoComplete won't allow for object selection, we'll need an alternative to MatSelect that works the same but looks like MatAutoComplete and doesn't require the entire select list to be in the markup statically. There are major performance issues when you try to add too many of these elements on the page with lots of potential select options. Ideally for this scenario I'd like to have a combo-box like control that looks like MatAutoComplete except:
MatSelect- it's not a free-entry text control.@bind-Value to an integer foreign key field, and use a list of options objects which each have a display field and a value field (integer foreign key values), and when the user selects an option, the value field is assigned to the @bind-Value param and not the entire option object.My particular use case: I have a page where the user can build up a "system" with various hardware "components". They add a component by selecting the type, then selecting the model from a rather large list of available models for each type. Currently neither the MatSelect (too expensive to have 20 copies of 1000+ options rendered into the html in a table) nor the MatAutoComplete (can't force selection from the list as it's a free-text-entry control. Have to validate the text entry before saving) fit the requirements.
From a workflow perspective, wouldn't it be better to separate these items into issues and assigning them to a 2.0 project/milestone? then people can just grab small parts for contributing. makes working easier.
Hi! Thanks for all the work put in to this project! Much appreciated!
Are there any plans for adding support for various aria-attributes? Ref https://developer.mozilla.org/en-US/docs/Learn/Accessibility/WAI-ARIA_basics.
I'm thinking of for instance, aria-required for input-fields, and aria-selected for tabs, making the component WCAG complaint out of the box, https://www.w3.org/WAI/standards-guidelines/wcag/
Please, MatDatePicker.Culture is needed.
MatAutocomplete.Disabled property exists but is not showing with intellitype list.
anything I can help with this?
Announcement: MatBlazor 2.0.0 (9 December)
MatTable Allows add custom parameters
Most helpful comment
Would it be possible to get Minimum Date and Maximum Date added to the DatePicker component?
If it's still based on flatpickr, I think they do have the option of setting max and min.