Open guuurris opened 3 years ago
Duplicate of https://github.com/angular/components/issues/17743
I think that the title of #17743 is the same, but what it was actually asking for was inheriting the disabled
state from the closest fieldset
. I think that we can keep this open, but we'll have to do some investigation on whether we can make the accessibility work for this. We could use aria-readonly
, but we'll have to check if it makes sense on a combobox
.
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation.
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.
This is still an issue today and i believe its very similar to how disable work the difference is essentially if the field is included in the this.form.getValue()
which disabled i not but readonly should be.
Feature Description
It should be possible to use a readonly property similar to have disabled is used with mat-select (Material Select component)
Use Case
When re-submitting a form where some select field should not be editable but resent. Property disabled will in this case simple remove selected value from form.
This is an example that show how it would be used and how it works now: https://stackblitz.com/edit/angular-fj6kyz?file=src/app/select-overview-example.html