-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation: formatting the allowed styles #19477
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for reviewing, folks! |
@retrofox be careful with that planet destroyer! |
No kidding, he's so cute as destructive! 😱 |
Nice work! I was also thinking to create a PR but @retrofox did nice work. Below are my findings. Backend: https://share.getcloudapp.com/xQu0zkwJ Before Code:
Before Front End : https://share.getcloudapp.com/ApuOxoe5 After Code:
After Front End: https://share.getcloudapp.com/p9u5X4Z1 |
Thanks, @maheshwaghmare for your comment.
I did a quick research about how to tackle this issue and found |
I wouldn't be too concerned about performance with strings as short as we can expect in a label |
So we could consider switching to |
oh, my bad, yes absolutely, I think I'd prefer |
Description
This PR handles rightly applying HTML format to menu items, avoiding escape HTML characters for those ones which are allowed.
Fixes #19473
How has this been tested?
You can format the menu items using the toolbar of the navigation menu. So far, it's possible to set up bold, italic, code, underline, strikethrough, span text, and inline-image.
In order to test it, just apply some format to the navigation item and confirm that the format s applied as expected in the front-end.
Screenshots
Types of changes
Checklist: