Repository navigation
Conversation
Test using WordPress PlaygroundThe 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
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
3908ac2 to
e85a551
Compare
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
The core icons ship with WordPress and are trusted, and sanitizing them with wp_kses() is the main cost of rendering them.
e85a551 to
fa2f8de
Compare
|
@t-hamano Thanks for the review and welcome back! All make sense, I've applied them and re-test this PR. |
Trac ticket: https://core.trac.wordpress.org/ticket/66338.
Backport of WordPress/gutenberg#85083.
Skips the
wp_kses()sanitization of the core icons bundled with WordPress, inwp-includes/images/icon-library/.#12270 renders the admin bar and admin menu icons with
wp_get_icon(), so every wp-admin page now loads about 20 icons through the registry. Measurements on that PR show about +3.5 ms of server time per wp-admin page, and most of the icon cost iswp_kses(). The core icons ship with WordPress and are as trusted as the rest ofwp-includes, so sanitizing does not really protect anything.Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: code generation, with my supervision.
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.