@@ -25,7 +25,6 @@ To encourage extensible and predictable toasts, we recommend a header and body.
Toasts are as flexible as you need and have very little required markup. At a minimum, we require a single element to contain your "toasted" content and strongly encourage a dismiss button.
@@ -41,14 +40,12 @@ Toasts are as flexible as you need and have very little required markup. At a mi
</div>
</div>
{% endcapture %}
{% include example.html content=example %}
</div>
{% include example.html content=example class="bg-light" %}
### Translucent
Toasts are slightly translucent, too, so they blend over whatever they might appear over. For browsers that support the `backdrop-filter` CSS property, we'll also attempt to blur the elements under a toast.
@@ -101,14 +96,12 @@ When you have multiple toasts, we default to vertically stacking them in a reada
</div>
</div>
{% endcapture %}
{% include example.html content=example %}
</div>
{% include example.html content=example class="bg-light" %}
## Placement
Place toasts with custom CSS as you need them. The top right is often used for notifications, as is the top middle. If you're only ever going to show one toast at a time, put the positioning styles right on the `.toast`.