You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.
Had the same issue. Just use this instead of ng-disabled: not-busy-disabled="{{ yourFlagForDisable }}"
UPD: Actually, if you need to change button disable without emitting event you should use both. ng-disabled which will enable disable button on changes of model for example, and not-busy-disabled to get back to the required disable state after "busy" is finished. Of course it would be better that not-busy-disabled were mapped to button disable attribute, then we could use only 1 directive
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
this busy function overrides the ng-disabled.
if ng-disabled = false then when busy is done, ng-disabled get ignored.
The text was updated successfully, but these errors were encountered: