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 Jan 9, 2023. It is now read-only.
Thanks for digging into this. As it is currently implemented the button needs to be present in the dom once the promise-btn directive (in this case on the form element) is $compiled.
Currently there is also no easy way to set this up as the button elements need event handlers to be attached. Listening for dom changes inside of the form would be complicated and costly performancewise, but I'm open to suggestions!
One alternative would be to use a child directive on the buttons, but this would require a huge refactor of the component, make the usage more complicated and possibly break existing implementations.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a form like this
By debugging, I found that
getSubmitBtnChildren
does not find buttons with theng-if
directive.A workaround is to use
ng-show
instead. Is there any way to wait until all thoseng-if
are already resolved?The text was updated successfully, but these errors were encountered: