You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Will there be any unintended consequences if we take the approach mentioned below?
Change all the events to be handled during capture phase, this offers us the following advantages:
scroll: the behavior gets inline with the browser's default context menu
works even when scroll happens anywhere on the screen. Consider a two column layout where the right one has the context menu and the left one has a scroll. The menu will close when the scroll happens in the left column(browser's default context menu works like this).
other events: there might be few elements on the screen which might do stopPropagation and prevent the context menu from closing. capturing the event fixes this issue.
Also adding a mousedown event would be helpful in cases where we have elements that are draggable.
I would be happy to work on this if you are okay with this.
The text was updated successfully, but these errors were encountered:
Currently all the event listeners that handle close are set to be handled at bubbling phase.
Will there be any unintended consequences if we take the approach mentioned below?
Change all the events to be handled during capture phase, this offers us the following advantages:
Also adding a mousedown event would be helpful in cases where we have elements that are draggable.
I would be happy to work on this if you are okay with this.
The text was updated successfully, but these errors were encountered: