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 May 29, 2019. It is now read-only.
Open a datepicker-popup from a modal, with datepicker-append-to-body set to true. Click outside the modal to close it. The datepicker stays around even though its scope was destroyed.
This looks like a bug to me, but need further investigation. What appears to be happening is that the popup is binding to an incorrect template when appendToBody is used, causing a comment tag to be removed instead of the right element.
I am also having this issue, it does seem to be a bug.
Destroying the scope keeps the datepicker visible on the screen. The modal does not have anything to do with it, the issue happens with any $destroy event.
Open a datepicker-popup from a modal, with datepicker-append-to-body set to true. Click outside the modal to close it. The datepicker stays around even though its scope was destroyed.
See http://plnkr.co/edit/YdWmqYPFBNbv4vhQZc4t?p=preview
The text was updated successfully, but these errors were encountered: