-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Link autocompleter: decode post title HTML entities #65589
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
Conversation
…n `fetchLinkSuggestions` where the `rendered` title (containing HTML entities) is also being decoded.
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: +19 B (0%) Total Size: 1.77 MB
ℹ️ View Unchanged
|
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.
Thank you, @ramonjd!
Waaah! All the E2E fails are passing locally for me. Looking at the commit history, I think it's affecting a lot of branches so my guess is that this PR okay. |
What?
Resolves #65578
For link autocompleters, make
title
property consistent with that infetchLinkSuggestions
where therendered
title (containing HTML entities) is also being decodedWhy?
So that the post titles are rendered correctly.
How?
Running post titles through
decodeEntities
, which is consistent with navigation links and fetchLinkSuggestions.Testing Instructions
Bob's "post" !@#$%^&*
[[
to trigger link autocompleteTesting Instructions for Keyboard
Screenshots or screencast