fix(module:overlaytrigger): premature reset of _mouseInTrigger #2036
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤔 This is a ...
🔗 Related issue link
Fixes #2035
💡 Background and solution
PR #1977 had broken the
Popover
. That PR added setting of_mouseInTrigger = true
when trigger was clicked and then was setting it back to_mouseInTrigger = false
. However, due to current way theOverlayTrigger
works, the_mouseInTrigger
is set to 'true' much earlier (probably in js callback tomouseenter
event). I believe this is a both performance and design issue.OverlayTrigger
registers all the events (mouseenter
,mouseleave
,focus
,blur
,click
,contextmenu
) regardless of what will be the real trigger. I actually mentioned that in issue #1130. I already started working on that optimization, but it proved to be much more complex and it takes me much more time.I also tried to do a regression test, but I gave up. Not because it is impossible, but because this test is more complex than it is worth and it cannot provide 100% accuracy. For the test to be written in a reliable manner, the optimization has to be done (the one I mentioned in the paragraph above).
📝 Changelog
☑️ Self Check before Merge