-
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
Page Content Focus: Default insertion point to the Post Content block #51773
Conversation
Size Change: +71 B (0%) Total Size: 1.42 MB
ℹ️ View Unchanged
|
Flaky tests detected in 04047c6777639d0654f11eb1dfaef0537171787c. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5340628144
|
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.
Work well for me in testing and is a big improvement over what we have. In future we may want to also consider adopting this behaviour even if blocks outside the post content block are selected (e.g. featured image).
If someone else can give the thumbs up on code LGTM
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.
Worked for me as shown in your video. Code looks good to me :) 👍
04047c6
to
6a936ff
Compare
…WordPress#51773) * Page Content Focus: Default insertion point to the Post Content block * Don't prioritise patterns if there is a specified root
What?
Follows #50857.
Makes it so that when you are focused on editing a page's content in the site editor and no block is selected, the global inserter will insert blocks into the end of the Post Content block.
Why?
This mimics the post editor and is what users would expect when editing page content.
How?
Adds a special case to the existing
__experimentalGetInsertionPoint
selector in thecore/edit-site
store.Testing Instructions
Screenshots or screencast
Kapture.2023-06-22.at.11.35.40.mp4