-
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
Late escape Navigation blocks #37870
Conversation
Ok this PR seems to have a few issues. Let me revisit with a more critical eye and iron out some of these. |
Ok @swissspidy and @tellthemachines this is RfR again. I appreciate your patience with this PR. In all honesty I could have handled it with greater care and attention. That's my fault for trying to take on too many blocks at the same time. I've made the necessary changes and we now have a limited subset of changes which should be easier to review. |
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 the iteration, this is looking much better now!
I'm not sure the test failures are legit, so restarted the build, let's see how that goes.
Ok I think were now seeking a 👍 on this one. |
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.
LGTM with one question about escaping inline styles
Description
This is not a security problem. This PR simply moves escaping of all PHP output to be as "late" as possible. This means we avoid escaping variables until they are output in the HTML markup.
This is a WP Core best practice.
How has this been tested?
Screenshots
Types of changes
Checklist:
*.native.js
files for terms that need renaming or removal).