Allow using an action button in multi-line inline/toast notifications #7181
Labels
component: notification
proposal: open
This request has gone through triaging. We're determining whether we take this on or not.
type: enhancement 💡
Summary
Typically, when we use inline/toast notifications in our product, we are using multi-line notifications. (It's rare for our descriptions to be super brief, so we like the more optimal layout of the multi-line.) Along those same lines, usually our action description in the button is around 3 words long, which can take up quite a bit of horizontal space. If we could have action buttons in the multi-line notification as well as the single line, that would be great!
I believe this is a design and development change, since the multi-line component would need to support an action button.
Justification
Currently, our FEDs will be using a custom version of the component for more optimal layout. Going forward, it would be more optimal and efficient for our devs to be able to use a "approved" component
Desired UX and success metrics
Unfortunately, because of the complexity of our product, it's very rare that when we use an inline notification, that we have very brief descriptions. It's a constant negotiation with our Information/Content Developer to keep these descriptions short, but sometimes it simply needs to be a little longer. If the description is longer and has an action, then it doesn't look very good to use the single line notification with an action.
Here's a real world example I came across recently:
Context of the notification:
Having an action element in a multi-line notification is much better in this case.
Specific timeline issues / requests
For now, our devs are able to use the custom component I mentioned above, so it is not urgent. But it's definitely a nice to have!
NB: The Carbon team will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!
Available extra resources
I'm happy to help with building the component in Sketch if necessary. I'm sure my FED colleague could be consulted as well for the custom component that he created.
Carbon is a collaborative system. We encourage teams to build components and
submit them for integration as either add-ons or core components.
The text was updated successfully, but these errors were encountered: