Le jeudi 17 mai 2018 04:56:39 UTC+2, Georges Caplande a écrit :
>
>
>
> Le mercredi 16 mai 2018 06:25:22 UTC+2, Georges Caplande a écrit :
>>
>> I found a solution by creating a directive that adds or removes the 
>> *attribute* 'disabled' to the element to be processed. The attached demo 
>> shows, also, that changing the value of the 'disabled' *property* has no 
>> effect on the element.
>> Finally, a note: The fact that the button does or does not belong to a 
>> FormArray does not matter. This solution works in all cases
>> https://stackblitz.com/edit/angular-qmj3oi
>>
>> Le dimanche 13 mai 2018 06:11:56 UTC+2, Georges Caplande a écrit :
>>>
>>> I thought I had found a way to make the button disabled by taking into 
>>> account the disabled attribute (so [attr.disabled]) instead of the disabled 
>>> property ([disabled]) but it does not work. Indeed, the "supprimer" button 
>>> remains inactive regardless of the value of the "supprimerActif" property 
>>> of the component.
>>>
>>>
>>>> Le jeudi 10 mai 2018 16:28:15 UTC+2, Georges Caplande a écrit :
>>>>>
>>>>> The attached example includes a button in an element of FormArray. I 
>>>>> can not disable the button labeled "supprimer" by varying the value of 
>>>>> the 
>>>>> attribute "supprimerActif"
>>>>> An idea ?
>>>>>
>>>>> https://stackblitz.com/edit/angular-s5tmyb
>>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to