-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Notification] Actionable/Persistent variant #8703
Comments
For now, we are going to constrain the amount of action buttons in the new toast to only one action. We had a few iterations of what two action buttons would look like but after much discussion we believe it would be best to stick to one for the time being. We couldn't find that many use cases for two and the ones we did, the actions seemed redundant. update! We are going with the small tertiary button. Visual specs for toast with actions |
Cloud Pak for Data and the Cloud Pak Platform have already been including links in toast notifications as these are always accessible later from the Notification list page |
Summary
ToastNotification was updated as part of #8406 to use only an accessible
role
ofalert
,status
, orlog
in v11. This change meant that Toast would no longer accept interactive elements/buttons/children. This leaves InlineNotification as the only notification component to allow action buttons.This leaves a big gap for teams needing actionable notifications that mimic the visual styling of a Toast notification.
The proposal here is to add a new notification variant with the following requirements:
position: relative;
role
ofalertdialog
timeout
optionPersistentNotification
,AlertDialogNotification
,ActionableNotification
I originally intended to deliver this as part of #8560, but it was clear this needed visual/ux design.
The text was updated successfully, but these errors were encountered: