Intrroducing mause actions callbacks on tooltip component, to correctly handle clearing the tooltip.
Details
Details
Flow; Tested with the rest of diffs stack.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
| web/chat/tooltip-provider.js | ||
|---|---|---|
| 9 | Was it an arbitrary choice to make the leave tooltip timeout half the time of the leave source timeout? Just wondering what the relationship between them is and how the values were determined (since both time periods are so short I think they'd be indistinguishable to me) Would it maybe make the user experience slightly more predictable if both timeouts were 200ms? | |
| 100–104 | If I understand correctly, this means if the cursor re-enters the current tooltip the 200ms countdown to clear the tooltip gets cancelled. If the user moves their mouse quickly, would it be possible for multiple tooltips to become visible? Does that break any assumptions? | |
| web/chat/tooltip-provider.js | ||
|---|---|---|
| 9 | I'm open to changes here. The original reason was that the user needs more time to move cursor between message and tooltip, and the onMouseLeaveTooltipDisappearTimeoutMs was set just to prevent disappearing the tooltip when the user leaves it accidentally for a really short period of time. | |
| 100–104 |
Yes - any countdown - the 200ms countdown after mouse leaving the message, or 100ms timeout after mouse leaving the tooltip.
No, when user enters the component that calls renderTooltip the previously rendered one immediately disappears and existing timer is cancelled. | |