-
Notifications
You must be signed in to change notification settings - Fork 794
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] Content accessible via pointer #1490
Conversation
5b6c67c
to
4ec4ba5
Compare
4ec4ba5
to
a483b01
Compare
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.
Just one question left (maybe a rename needed) but otherwise it's good to go from me.
Obviously we need to remove the debug area first though 😀
const isPointerDownRef = React.useRef(false); | ||
const hasTriggerActivated = React.useRef(false); |
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.
What does this one mean?
When I read the name I thought it was about the trigger activation (click, keydown space/enter) but looking at where the ref is updated it seems to mean something else.
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.
We needed to use pointerMove
after all for the polygon bleed change. Because of this we only want to trigger an open on the very first pointerMove
event, this flag is to describe that the tooltip "has opened" already so don't do it again until we leave and come back.
Perhaps something like hasPointerMoveOpened
?
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.
Yeah that makes more sense.
* Remain open when pointer over content * Feedback * Additional simplification * Improve grace area accuracy * Naming, remove debugging area
fixes #620
Of the options available we decided on:
CleanShot.2022-06-24.at.12.34.23.mp4