Closed yinonov closed 1 year ago
Carbon has a good 'Notification pattern' explanation with details on all notification (user feedback) components https://carbondesignsystem.com/patterns/notification-pattern/#notification-types.
By design, their inline alert and pattern look the same, but they have different functionalities
Top is inline and bottom is banner
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
reopening as we're still missing one or several component(s) and @AyalaBu is working on that topic.
the Carbon summary @jshenkman linked is a good document to compare to. so here's an attempt:
notes:
This issue is stale because it has been open for 30 days with no activity.
@AyalaBu What should we do with this ticket? Are you still working on the design?
@rinaok The design is finished: https://www.figma.com/file/JJNgZvt1qf3ydYmOwbE3Jg/Vivid-UI-Kit---3.0-WIP?node-id=21271%3A142119&t=DTrdMW2piZjbOokz-1
The component still needs to be migrated.
The issue was moved to JIRA: https://jira.vonage.com/browse/VIV-1009
Banner
Addresses a scenario where page notifies a user of an important message in an intrusive manner.
Most UX design name the equivalent vivid banner as banner, some call it toast 🤷♂️. Most use the role
alert
internally. some assign log as rolew3c school
w3 aria
nord
spectrum
Atlassian
Carbon inline
Carbon Toast
[ ] Banner - consider renaming to alert?
[ ] Banner - default to role
A dismissible element requires programmatic handling of user alert and disruption As Banner is no longer a dismissible element, rather has natural flow display, it might not need that programmatic handling
Snackbar
Addresses a scenario where a page notifies a user of a system occurrences and often requires immediate user attention
Overlaps with Toast
Some library maintainers allow multiple stacked instances