You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently snackbars have a hard-set 10000 timeout. While this is appropriate perhaps for some notices (those that have actions), snackbars without actions should be much quicker.
For example, a notices that fires after you run a command (like "Hide block breadcrumbs" or when you copy a block to your clipboard "Copied "button" to clipboard" are informative, not action-seeking. You shouldn't have to interact with them (other to dismiss if they're hanging around and stacking up.
One idea is to have the NOTICE_TIMEOUT adapt based on if the notice has an action. If it does, then perhaps a longer value like 10000 is fine; otherwise something much smaller (even 5000) may work much better. We'd need to test around the specifics, but it could be much shorter.
Currently snackbars have a hard-set 10000 timeout. While this is appropriate perhaps for some notices (those that have actions), snackbars without actions should be much quicker.
For example, a notices that fires after you run a command (like "Hide block breadcrumbs" or when you copy a block to your clipboard "Copied "button" to clipboard" are informative, not action-seeking. You shouldn't have to interact with them (other to dismiss if they're hanging around and stacking up.
One idea is to have the NOTICE_TIMEOUT adapt based on if the notice has an action. If it does, then perhaps a longer value like 10000 is fine; otherwise something much smaller (even 5000) may work much better. We'd need to test around the specifics, but it could be much shorter.
gutenberg/packages/components/src/snackbar/index.tsx
Line 23 in f69f489
The text was updated successfully, but these errors were encountered: