-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
[Tooltip] Closing tooltip when scroll starts vs when scroll stops #1447
Comments
Hi @sunwrobert, |
Sorry, yeah I meant trackCursorAxis |
Related: mui/material-ui#38379 We discussed closing the tooltip on scroll start vs stop before but didn't reach a decision yet: https://mui-org.slack.com/archives/C02P87NQLJC/p1732704384238479 CC @colmtuite Currently it closes when scroll stops which is intentional, the docs demo demonstrates this: https://master--base-ui.netlify.app/react/components/tooltip |
Bug report
Current behavior
Hi, great library! We're using this at OpenSea and using the attachToCursor option to power one of our Collection link hoverables. However, we are noticing issues where if people are scrolling while it's attaching, it can get to a state where it no longer disappears even if the mouse is no longer on the anchor.
https://www.loom.com/share/9608676b8c904397af37d46b059ea9b9
Here's a video showcasing this. I don't have a reproducible example in a sandbox at the moment, but wondering if as a stop gap we could at least expand the Tooltip behavior to close if scrolled? Not sure of the best solution here. Thanks!
Expected behavior
Provide a clear and concise description of the expected behavior.
Reproducible example
Link to a CodeSandbox, StackBlitz, or other IDE.
Base UI version
For example v1.0.2
Which browser are you using?
Chrome/Safari/Firefox/Safari iOS etc.
Which OS are you using?
Mac OS/Windows/Other etc.
Which assistive tech are you using (if applicable)?
Voiceover/JAWS etc.
Additional context
Provide any additional context that might help us identify the problem and find a solution.
The text was updated successfully, but these errors were encountered: