-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
fixes #14962 - ContextMenu | onHide, onShow event is not being triggered when you right click twice continuously #14964
Conversation
context menu onshow event should not be inside onOverlayAnimationStart since it is not being fired when context menu is clicked twice simultaneousl
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
…ing triggered when you right click twice continuously the event should be called before calculations of position. the previous commit made some view bugs when items before onShow was modified
Hi @ymg2006, Thanks for the effort and support! Could you please link the related issue with the PR and tag me afterward so I can include it in the milestone and merge your PR? Also could you please put onHide and onShow emitters after the |
moved onHide event emitter after visible set, the onShow is not moved because when we dynamically want to change context menu items it gets in the correct position, so I put it before this.position() and visible set true method.
@cetincakiroglu the issue link is: #14964. |
… visible exactly like onOperatorChange
The issue link is not correct it's your PR link. Please link the PR with an active issue if it exists or open a new issue describing the malfunction and link the PR. |
@cetincakiroglu |
Hi, Thanks for the effort and support! |
context menu onshow event should not be inside onOverlayAnimationStart since it is not being fired when context menu is clicked twice simultaneousl
Defect Fixes
When submitting a PR, please also create an issue documenting the error and manually link to an issue or mention it in the description using #<issue_id>.
Feature Requests
Due to company policy, we are unable to accept feature request PRs with significant changes as such cases has to be implemented by our team following our own processes.
Smaller scaled feature implementations such as adding a property to a component will be considered for merging.