docs: fix broken html rendering in accessibility banner#16736
Open
ApplY3D wants to merge 1 commit into
Open
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
1 participant
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.
What?
Fixed an issue where raw HTML tags were being displayed as plain text within the Accessibility page banner.
Why?
The
Bannercomponent in the documentation site does not automatically transform raw HTML strings (like<p>and<a>) into rendered elements. This resulted in users seeing the literal code instead of the intended message and link. Switching to standard Markdown ensures the content is correctly parsed and rendered by the MDX provider.How?
Updated
docs/admin/accessibility.mdxto replace the non-rendering raw HTML with standard Markdown syntax inside the<Banner>component.Fixes #16735