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
Interesting thing: it seems like first cycle (open and close) it works fine, but starting with second open and later - it fires afterClose event right after opened.
For some cases that might be fine. But for me, since I have logic that that should 'start before it's open' (aka opened event) and 'end after it's closed' (aka afterClose). And this 'but' ruins the event flow.
The text was updated successfully, but these errors were encountered:
I faced issue with
afterClose
event.Yes, I saw this PR (#220) and your comment said that you're aware. At that time PR got merged.
Later, I assume this commit (340cc7f) should fix this issue.
But it's not. I still can see this issue here - https://ncstate-sat.github.io/popover/
Interesting thing: it seems like first cycle (open and close) it works fine, but starting with second open and later - it fires
afterClose
event right afteropened
.For some cases that might be fine. But for me, since I have logic that that should 'start before it's open' (aka
opened
event) and 'end after it's closed' (akaafterClose
). And this 'but' ruins the event flow.The text was updated successfully, but these errors were encountered: