-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Click close #12
Comments
Hi! Thanks for the report and sorry for taking some time to answer. Like with #9, most likely your dropdown content is attached outside of the model container (e. g. attached to If that is the case, then the solution is to manually check in the away handler whether the event originated from the dropdown content. |
|
@sanyashvets I found a simple solution |
Looking at this with a fresh eye, this should have already been fixed in 2.1. You may only be affected by this if you are using Vue < 2.5 and VueClickaway < 2.1. Try updating, and if you are still being affected by this, please open a new issue with a repro. |
I have a modal with
v-click-away
directive installed on it withmodalClose
event. And also I have dropdown's<li>
, buttons with (v-if
,v-show
in modal) and@click
events on it. I have no idea why, but modal fires itmodalClose
event byclick
onli
andbuttons
. Yes, I can use@mouseup
or@mousedown
events instead of@click
, but I think I have to tell u about this issueP.S. thx for plugin. It's great!
The text was updated successfully, but these errors were encountered: