fix: prevent long unbreakable words in alert messages from overflowing #851
+9
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the issue where long, non-breakable words in alert messages would overflow the container.
Motivation and Context
Previously, if an alert contained a long string without spaces, it would extend outside the container, breaking the UI. This change ensures proper word wrapping or breaking to keep the alert content inside the container.
How Has This Been Tested?
Breaking Changes
No breaking changes. Existing alert functionality remains the same.
Types of changes
Checklist
Additional context
This fix is proactive; no issue was reported. It improves alert component resilience against unexpected input.
Screenshots:
Before:
After:
