-
Notifications
You must be signed in to change notification settings - Fork 740
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
Calling .contextMenu('hide') throws an error #351
Comments
Good catch, kind of weird. I'll try to make some time this week to go through this issue. |
Well, I'm (ab)using the menu intensively and therefore find some things, which aren't seen easily! :D |
The easiest way to get a feature in is to open a issue to discuss and then make a pull request. But i do try to create features that i feel are good additions. The problem is my time is sometimes a little limited :) |
Could you please inform me if this feature is already implemented or not? Thanks a lot |
I searched the repos and found the clicked element gets a classname: |
Thanks a lot :) You are right, I could have checked that. |
Seems fixed see #352 |
Hi again!
Apparently manually firing the .contextMenu('hide') function to manually hide the menu causes the following line to trigger an exception. The root.$menu is empty when function is triggered manually (i.e. JS function $menu.contextMenu('hide')). When tracing the js-code, the value is filled if event is triggered when user clicks away, but not when js fires the function.
line:636:
root.$menu.trigger('contextmenu:hide');
result:
Uncaught TypeError: Cannot read property 'trigger' of undefined
The text was updated successfully, but these errors were encountered: