Empty Variable Gives True Value To Disabled Attribute On Input November 26, 2023 Post a Comment I dont know if this is a problem or normal behavior. If we have a form like this: field1Solution 1: UPDATEI found the answer to this in the angular source code (<3 open source!). The ngModel controller explicitly checks for '' when the disabled input is changed. If the input strictly equals '', the element will be disabled. So this behavior is by design.Here is how to source code looks (link to GitHub, see line 142 and 217) const isDisabled = disabledValue === '' || (disabledValue && disabledValue !== 'false'); CopyThis means that you cannot use an empty string as falsy to set an input that is using ngModel to disable it. Here is how you get around itBaca JugaWhy The NgStyle Directive Is Declared Into The []?Angular2 - Call A Function From Another Standalone Component. Basically, Call Function From Outside ComponentEmpty Variable Gives True Value To Disabled Attribute On Input<inputtype="text" name="field1" [(ngModel)]="mainVar" [disabled]="someVar ? true : false" /> CopyWorking plunker exampleSolution 2: Set it to null/undefined/false, and it will not be disabled. String empty is still a value. Share You may like these postsWhy The NgStyle Directive Is Declared Into The []?Get Angular 2 Service Inside A Custom Class Instantiated By MeWhy The Ngstyle Directive Is Declared Into The []? Post a Comment for "Empty Variable Gives True Value To Disabled Attribute On Input"
Post a Comment for "Empty Variable Gives True Value To Disabled Attribute On Input"