Is toast action/close intentionally designed to not resume?

[gdfreitasdev]

I was wondering why the components <Toast.Action>|<Toast.Close> does not resume the paused state when clicked.

It maintains the state of paused for new upcoming toasts which imo might not be the ideal behavior as it will require user interaction to resume toasts automatically again.

What do you think? Should this be filed as a bug?

To reproduce we can use official docs: https://www.radix-ui.com/docs/primitives/components/toast#close

1. Click on "Add to calendar"
2. Click on "Undo" inside toast
3. Click on "Add to calendar" and notice that it won’t disappear automatically anymore

This can also be reproduced on other libraries/design systems that uses Radix internally

• https://ui.shadcn.com/docs/components/toast
• https://vercel.com/design/toast#action-cancel

[jvzaniolo]

@gdfreitas This issue is happening because when you click the dismiss/close button, it changes the context.isClosePausedRef current value to true, so when you create a new Toast, it does not reset its value to false and this verification doesn't trigger the startTimer function to dismiss the Toast automatically.

primitives/packages/react/toast/src/Toast.tsx

Line 538 in eca6bab

if (open && !context.isClosePausedRef.current) startTimer(duration);

I opened a PR to fix this and another similar issue with resetting the ref current values.

• [Toast] Fix duration value during rerender and Toast.Close issue #2236

[gdfreitasdev]

That's what I was suspecting, thanks for the response @jvzaniolo . I'll subscribe to your PR.

[adolfoscheidt]

I had the same issue, thanks too! Subscribing to the PR as well