Skip to content

KSES: Allow SVG presentation attributes in safe_style_css#12169

Open
t-hamano wants to merge 2 commits into
WordPress:trunkfrom
t-hamano:65457-svg-kses-filter
Open

KSES: Allow SVG presentation attributes in safe_style_css#12169
t-hamano wants to merge 2 commits into
WordPress:trunkfrom
t-hamano:65457-svg-kses-filter

Conversation

@t-hamano

@t-hamano t-hamano commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Ports WordPress/gutenberg#79172 to Core.

Trac ticket: https://core.trac.wordpress.org/ticket/65457

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 4.8
Used for: Porting the Gutenberg change and drafting tests; all changes were reviewed and edited by me.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

t-hamano and others added 2 commits June 13, 2026 22:59
`safecss_filter_attr()` only keeps an allowlist of CSS properties, so SVG
presentation attributes such as `fill` and `stroke` are stripped from inline
styles when SVG markup is sanitized with `wp_kses()`. Add the SVG-specific
presentation attributes to the `safe_style_css` allowlist so they are
preserved.

Co-Authored-By: Claude <noreply@anthropic.com>
Cover the SVG presentation attributes added to the `safe_style_css`
allowlist to ensure they are preserved by `safecss_filter_attr()`.

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Hi there! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

@t-hamano t-hamano marked this pull request as ready for review June 13, 2026 14:07
@github-actions

Copy link
Copy Markdown

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props wildworks.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant