-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix hover stuttering. #11675
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
Fix hover stuttering. #11675
Conversation
Codecov Report
@@ Coverage Diff @@
## master #11675 +/- ##
==========================================
- Coverage 61.27% 60.65% -0.62%
==========================================
Files 593 627 +34
Lines 32493 33879 +1386
Branches 4594 4765 +171
==========================================
+ Hits 19910 20550 +640
- Misses 11581 12335 +754
+ Partials 1002 994 -8
Continue to review full report at Codecov.
|
if (!this.coordsInsideEditor(e.clientX, e.clientY)) { | ||
// tslint:disable-next-line: no-any | ||
const hover = this.state.editor.getContribution('editor.contrib.hover') as any; | ||
if (hover._hideWidgets && e.clientX) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change looks good. Just wondering, why is the e.clientX needed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duh. That was a leftover when I was debugging it. I will remove.
Kudos, SonarCloud Quality Gate passed!
|
For #11422
We were too aggressive in our hover closing. The bug was caused by hovering over one item closing another. This is unnecessary if inside the same window still.
Note, this isn't a regression, but while figuring out if it was a regression or not, I just fixed it instead.