`disabled` on mdInput doesn't work when formControl directive is used(works with native el)
See original GitHub issuesee http://plnkr.co/edit/AvPMHB3lzqwaexypHkUR?p=preview
I’ve read some issues on angular/angular
and apparently disabled
shouldn’t work at all when reactive forms are used. But it looks like it does on native elements and doesn’t on element with mdInput
directive.
cc @kara
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:6 (3 by maintainers)
Top Results From Across the Web
angular - Reactive forms - disabled attribute - Stack Overflow
Use the following directive in the template and pass in the disabled state using [disableControl]="disabled" on the form control in the template ...
Read more >Disabling Form Controls When Working With Reactive Forms ...
When working with Angular Reactive Forms there are times when you need to disable/enable a form control, for example: <input [formControl]="formControl" ...
Read more >Can't Bind to formGroup Not Known Property Error in Angular
Angular is trying to tell us that it doesn't know about the formGroup directive on the <form> element in your component. This usually...
Read more >Angular directives for Bootstrap - AngularUI
To enable swiping, load the ngTouch module as a dependency. Use a <uib-carousel> element with <uib-slide> elements inside it. uib-carousel settings.
Read more >error: formcontrolname must be used with a parent formgroup ...
You'll want to add a formGroup directive - Angular reactive forms ... is printed if I use disabled in the template but not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can reproduce this bug, but it seems to work when adding the disabled directive manually.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.