Multiple auto-dismiss toasts #7024
Assignees
Labels
bug
Something isn't working
Comments
|
looks like this useHover onHoverEnd isn't called And it only happens if you dismiss the outer most toast such that the toast region become smaller behind the cursor. This means that in most browsers onPointerLeave isn't called. It's debatable if it's a bug in the browsers or not, they've declined to take action on this so far. See #3522 for some other related issues. We may need to do some hit detection on toast region resize to determine if we're still hovering. Or we could delay the removal |
devongovett
moved this from 🩺 To Triage
to 📋 Waiting for Sprint
in RSP Component Milestones
matthewdeutsch
moved this from 📋 Waiting for Sprint
to 🔬 To Investigate / Verify
in RSP Component Milestones
reidbarber
moved this from 🔬 To Investigate / Verify
to 🏗 In Progress
in RSP Component Milestones
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Provide a general summary of the issue here
When you open multiple auto-dismiss toasts together and you close the first (top) toast, all other toasts stay paused. It should keep running and dismiss when the timeout is finished
🤔 Expected Behavior?
All toast should be dismissed after the timeout is finished when it's no longer hovered.
😯 Current Behavior
The other toasts stay paused and you will have to hover over the other toasts to get them back running.
💁 Possible Solution
No response
🔦 Context
No response
🖥️ Steps to Reproduce
Version
0.1.1-beta.54
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
iOS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response
The text was updated successfully, but these errors were encountered: