-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Fix problem with encoding of css entities when post with existing block level custom css is edited by user without unfiltered_html #11104
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
Closed
glendaviesnz
wants to merge
5
commits into
WordPress:trunk
from
glendaviesnz:fix/block-custom-css-bug
+23
−5
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
292f17d
Fix problem with encoding of css entities when post with block level …
glendaviesnz 51f3c12
Fix WP version
glendaviesnz 35eab15
Sanitise CSS separate to other attribs
glendaviesnz a007350
Revert "Sanitise CSS separate to other attribs"
glendaviesnz 19537ea
switch to encoded string to stop kses mangling
glendaviesnz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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 getting up a fix!
I was wondering: what is the important sanitization step for block CSS attributes?
wp_kses()treats the CSS string as HTML. But should it?I'm wondering if an alternative solution would be to target the
cssattribute and run it throughwp_strip_all_tagsrather thanwp_kses.Or running through something similar (or reuse this same validation in a helper) that @sirreal and @dmsnell worked on in
WP_REST_Global_Styles_Controller::validate_custom_css()for https://core.trac.wordpress.org/ticket/64418There, for users without
unfiltered_html,&and>in block custom CSS were being double-encoded by KSES + JSON, so the CSS broke.(Sorry Jon and Dennis - you've become my default go-to brains trust for this stuff 😄 )