Thanks for this useful library. We've recently found what we would consider to be a bug. If the user right-clicks to trigger the menu and the browser window is small enough compared to the menu, then the menu may overlap the mouse when it opens, and the mouseup will immediately invoke a command, which is probably not what the user intended.
(In our actual application, the menu is bigger, so the window doesn't have to be quite so small for the problem to occur.)
In this scenario, there should be a minimum time that the mouse button has to be held down before a mouseup will invoke a command, or perhaps the first mouseup should never invoke a command and another click should always be required.
I tried to search for an existing issue report, but I may have the wrong search terms...
Thanks for this useful library. We've recently found what we would consider to be a bug. If the user right-clicks to trigger the menu and the browser window is small enough compared to the menu, then the menu may overlap the mouse when it opens, and the mouseup will immediately invoke a command, which is probably not what the user intended.
Here's a demo using the main demo page:
(In our actual application, the menu is bigger, so the window doesn't have to be quite so small for the problem to occur.)
In this scenario, there should be a minimum time that the mouse button has to be held down before a mouseup will invoke a command, or perhaps the first mouseup should never invoke a command and another click should always be required.
I tried to search for an existing issue report, but I may have the wrong search terms...