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
The modal window template is essentially the same between angular-ui-bootstrap and this library, so the issue exists between the two.
This plunker will demonstrate the issue in an simple environment. (use touch screen emulation)
Can anyone comment on why there's an ngClickng-click="close($event)" on this line ?
From a very shallow level of debugging, I don't see any close method on the modal window's scope or it's parents. Is it necessary? Removing it would solve a lot of ngTouch / ngClick interference between nested / child elements.
The text was updated successfully, but these errors were encountered:
Seemed like it was extraneous. I guess it boils down to a limitation of ngTouch in that any nested ngClick directives are going to have this behavior. But then again, I can't think of a reason that would be necessary!
See this issue thread for more info:
angular-ui/bootstrap#2280
The modal window template is essentially the same between angular-ui-bootstrap and this library, so the issue exists between the two.
This plunker will demonstrate the issue in an simple environment. (use touch screen emulation)
Can anyone comment on why there's an
ngClick
ng-click="close($event)"
on this line ?From a very shallow level of debugging, I don't see any
close
method on the modal window's scope or it's parents. Is it necessary? Removing it would solve a lot of ngTouch / ngClick interference between nested / child elements.The text was updated successfully, but these errors were encountered: