Fix design issues with recent react-intl upgrade #25272
Merged
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.
The
react-intl
upgrade changed the behavior ofFormatted*
components to not wrap translated messages inspan
tags anymore. While this is a pretty good change, it changes the DOM structure and breaks some of Mastodon's styling.Finding all the places where this change breaks the styling may be a better long-term solution, but it's also a much more involved one, so this commit changes
react-intl
's configuration to always wrap formatted messages in aspan
tag.See also: https://formatjs.io/docs/react-intl/upgrade-guide-3x#breaking-api-changes