Repository navigation
Remove compat function for unsupported unprefixed style states - #84531
Conversation
🤖 PR meta 🤖🎉 PropsIf 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. Updated as activity occurs, without notifying anyone named here. Add the 📦 Bundle sizeSize Change: -905 B (-0.01%) Total Size: 8.58 MB 📦 View Changed
⚡ PerformanceShow the resultsClient side metrics exclude the server response time. front-end-block-theme
front-end-classic-theme
media-processing
media-upload
post-editor
site-editor
🏁 Flaky testsSome tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information. pushes earlier threads above the canvas to keep the selected one aligned in
|
|
Is normalizeStyleStateAliases also a candidate for removal? |
Same question here, or is that for a separate PR? There's also the code in this file - https://github.com/WordPress/gutenberg/blob/trunk/packages/global-styles-engine/src/style-state-back-compat.ts |
Oh yes we should remove that too! No reason not to do it all in the same PR. |
|
🧹 |
talldan
left a comment
There was a problem hiding this comment.
LGTM, very thorough, and nice that this will simplify the codebase in the future!
bc7dc5f to
5742afc
Compare
What?
Removes
gutenberg_resolve_style_state_aliasesand all its calls. This function was introduced in #79210, before style states shipped to core, and it was meant to provide temporary back compat for unprefixed states for two Gutenberg plugin releases only. We can remove it now!Testing Instructions
Add some style states (viewport and/or pseudo) to some blocks, save and ensure everything displays as expected on the front end.
Use of AI Tools
copilot + gpt-6 luna used. reviewed by me.