-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Section Styles: Prevent flash of variation styles in post editor #63071
Conversation
Size Change: +4.46 kB (+0.25%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
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 If 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. |
This will make the id retrieval a little more robust in case query string params are added to the URL in future etc.
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, thanks for addressing the feedback.
This testing extremely well for me, and with some pretty hefty exploration of Section Styles. (Meaning my testing goes beyond just the Outline button.) LGTM for sure, with the hope it can get into RC3!!! |
It looks like the switch to |
This reverts commit 3f0f7b5.
After a brief look into the e2e failures, I'm not sure we can assume a standard URL to leverage Given the suggestion was noted as a "nit", I've reverted it for now in the interests of ensuring this fix lands for the next 6.6 RC. |
There is a backport for the PHP changes here available in WordPress/wordpress-develop#6959 |
There was a conflict while trying to cherry-pick the commit to the wp/6.6 branch. Please resolve the conflict manually and create a PR to the wp/6.6 branch. PRs to wp/6.6 are similar to PRs to trunk, but you should base your PR on the wp/6.6 branch instead of trunk.
|
) Co-authored-by: aaronrobertshaw <[email protected]> Co-authored-by: talldan <[email protected]> Co-authored-by: ellatrix <[email protected]> Co-authored-by: bgardner <[email protected]> Co-authored-by: justintadlock <[email protected]>
Cherry-pick and merge to the wp/6.6 branch here: |
) (#63111) Co-authored-by: aaronrobertshaw <[email protected]> Co-authored-by: andrewserong <[email protected]>
…dPress#63071) Co-authored-by: aaronrobertshaw <[email protected]> Co-authored-by: talldan <[email protected]> Co-authored-by: ellatrix <[email protected]> Co-authored-by: bgardner <[email protected]> Co-authored-by: justintadlock <[email protected]>
Fixes: #62668
What?
Preloads theme and global styles data from REST API to avoid flash of variation styles in the post editor.
Why?
The flash of styling looks pretty rough and negatively impacts the experience of using the post editor when there are block style variations applied to blocks in the post.
How?
block_editor_rest_api_preload_paths
filter to preload everything required for global styles data in the block editorurl
option.Testing Instructions
Screenshots or screencast
Screen.Recording.2024-07-03.at.1.17.15.PM.mp4
Screen.Recording.2024-07-03.at.1.16.48.PM.mp4