Skip to content
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

linting error tooltip obstructing the cursor #502

Open
revelt opened this issue May 19, 2018 · 1 comment
Open

linting error tooltip obstructing the cursor #502

revelt opened this issue May 19, 2018 · 1 comment

Comments

@revelt
Copy link

revelt commented May 19, 2018

hi guys!

Do correct me if I posted this issue on a wrong package. Also, sorry if this is a duplicate of some other issue, but I can't see any other raised about this so far.

Currently, cursor can get under the tooltip:

hidden

Notice how we can travel three lines under the tooltip and it won't disappear.

That can be annoying because I can't see my code and I'd expect the tooltip to be able to detect that it stands in the way..

I'm talking about the tooltip which devtools report as this code, linter-tooltip div:

screen shot 2018-05-19 at 06 10 58

The issue is more apparent when there are multiple panes, tight space and linting error contains lots of text, like in prettier-raised linting error messages.

@skylize
Copy link

skylize commented May 19, 2018

What would be expected behavior when the cursor collides with this tooltip? These 3 choices all seem equally valid to me, with pros and cons to each.

  1. Tooltip disappears on collision.
  2. Tooltip scrolls away to avoid collision.
  3. Tooltip ignores cursor (current behavior).

What if you have multiple cursors active? Should we watch all of them or just one? ... if just one, which?

If implementing scroll-away (# 2 above), what should we do at the bottom of the page if there is no more visible window space to move to?

In a situation where choosing between okay options that take a lot of work or an equally okay option that requires absolutely nothing, I would lean toward the reliable low maintenance option of just doing nothing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants