-
Notifications
You must be signed in to change notification settings - Fork 35
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
Some features #64
Comments
I achieved the result I wanted to say by adding 4 different points. I mark it below. Thus, if we add the " In fact, I have found and corrected a shortcoming in coding on this occasion. You check the line going to " This is exactly that part: Places I've addedSpecified as "// Added"
If there is a useful point, it is a great pleasure for me. Good luck with. |
Hi @ionurboz! |
Well it seems it's more a dom structure issue than a missing feature. |
If an "outside trigger" has been added to a trigger, a feature must be added to exclude it from its own children.
I explained it at length below. But let me describe it briefly, if we make a click, if it corresponds to an element inside the element, it will never activate its status, since it accepts it as a double click or trigger then external click.
with data-toggle-outside
Scenario 1
#el-1
active.Scenario 2
#el-1
as soon as it becomes active it becomes passive immediately.Because considers to be an outside element it.
Scenario 1 + Scenario 2
#el-1
Active in first click, passive in second clickNothing is wrong here, because when scenario 1 is repeated twice, the same thing will happen.
Scenario 1 + Scenario 3
#el-1
Active in first click, passive in second clickNothing is wrong here, because
<span>
is an outside element.with data-toggle-outside-parents
Scenario 1
#el-1
active.Scenario 2
#el-1
active.Scenario 1 + Scenario 2
#el-1
Active in first click, passive in second click.Scenario 1 + Scenario 3
#el-1
Active in first click, passive in second click.The text was updated successfully, but these errors were encountered: