useHover's delay and restMs do not work on some Linux machines

These issues were discovered while working on https://github.com/mantinedev/mantine/issues/2569

Myself and another user were experiencing mouseOnly would not work on our machines. Once I discovered this and fixed it, I immediately noticed that tooltip delays were not being honored.

I tried restMs as well, but the outcome is the same.

The closeDelay works on the elements, but only if the page remains focused. If the button is hovered while the page is not focused, then the closeDelay also has no effect.

I believe this is because of the way Linux is handling mouse input, though I’m not sure how exactly.

So of course, I don’t really expect mouseOnly to be fixed, but certainly the delays should work as intended?

Here’s a CodeSandbox derived from the tooltip docs:

• https://codesandbox.io/s/awesome-lehmann-if4106?file=/src/App.js

I believe this issue can be reproduced on any machine by using VMWare - although that is an untested assumption. Importantly, this issue does not only affect VMWare - it just seems the best way to reproduce the problem.

Assuming that VMWare on any machine can produce the issue, one could try a ready-made Kubuntu image via VMDK file with VMWare Workstation Player

If there’s any more useful information I can provide, please let me know.

Tested with versions 0.10.2 to 0.13.2

Thanks for all of your hard work!

[atomiks]

It will take like two seconds to fix — and yeah I’m guessing it’s just a bug with Linux/Chromium that’s unfixable and we just need to work around it. If you want, you can make a PR that checks for both mouse and pen, in the meantime before release, you can just use patch-package and patch on an additional check for “pen”.

[atomiks]

If it’s recognized as pen then that definitely is gonna break the logic as it needs to be mouse 😆 uhmm I guess touch is more important to be ignored for than pen so maybe we can check for both