fix: "VPNavScreenMenuGroup" component HTML not supported #3148
Conversation
This file contains 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
|
@brc-dd I apologize for disturbing you, I would like to know if my pull request can be merged. English is not my native language, so I may not have expressed myself clearly enough. If you need further explanation about this PR, please let me know. Please !! >< |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
For the visitor VitePress on the desktop, the TEXT of NAV written by NAV supports any HTML tags, which can make us achieve some simple effects, such as bold and corner markers
But when accessing on the mobile terminal, HTML was showed out
This PR keeps them consistent