-
Notifications
You must be signed in to change notification settings - Fork 739
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Visible fires twice #612
Comments
Yeah that is rather nasty indeed. Thanks for the report. |
bbrala
added a commit
that referenced
this issue
Mar 16, 2018
The menu checked `visible` status twice, once to check if the menu should be opened and once more when the menu was opened. The logic all moved to the `show` method now so the check is only done once. This should fix issue #612
bbrala
added a commit
that referenced
this issue
Mar 16, 2018
The menu checked `visible` status twice, once to check if the menu should be opened and once more when the menu was opened. The logic all moved to the `show` method now so the check is only done once. This should fix issue #612
bbrala
added a commit
that referenced
this issue
Mar 16, 2018
The menu checked `visible` status twice, once to check if the menu should be opened and once more when the menu was opened. The logic all moved to the `show` method now so the check is only done once. This should fix issue #612
This was referenced Mar 16, 2018
The menu checked Thanks again for the report. |
bbrala
added a commit
that referenced
this issue
Mar 16, 2018
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I've tried this with even just a single list item and it seems that the visble() function always fires twice - this behaviour also occurs in V3 Beta.
This is pretty problematic when using Ajax calls to determine whether an item should be visible / invisible as it makes 2 trips to the Ajax call.
The text was updated successfully, but these errors were encountered: