ECHOES-1301 Change ToastContent to stretch

[gregaubert]

Part of

[netlify]

✅ Deploy Preview for echoes-react ready!

Name	Link
🔨 Latest commit	1204e6d
🔍 Latest deploy log	https://app.netlify.com/projects/echoes-react/deploys/69fa07b9072a3e00083a490d
😎 Deploy Preview	https://deploy-preview-677--echoes-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hashicorp-vault-sonar-prod]

ECHOES-1301

[sonar-review-alpha]

Summary

This PR adds a single CSS property to the ToastContent component: align-self: stretch. This makes toast messages expand to fill the full width of their parent container rather than shrinking to content width. The change is minimal and focused on improving the toast visual layout.

What reviewers should know

What to review:

• The change is in src/common/components/Toast.tsx on the ToastContent styled component (around line 212)
• Only one line added: align-self: stretch;

Context:

• This is a styling-only change that affects the cross-axis alignment in a flex container
• The impact is visual: toasts will now span the full width of their container instead of being constrained to content width
• No logic changes, component behavior, or API modifications

Testing notes:

• Visual verification of toast appearance across different message lengths and screen sizes would be helpful
• Check that toast content (text, icons, buttons) still aligns correctly with the full-width behavior

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonar-review-alpha]

LGTM! ✅

Clean, minimal change. ToastContent is a child of ToastBody which has align-items: flex-start, so without align-self: stretch, ToastContent shrinks to its content width. The fix is correct and well-targeted.

🗣️ Give feedback

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube