Experiment with block drill down in contentOnly mode #64923
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
|
Size Change: +106 B (+0.01%) Total Size: 1.78 MB
ℹ️ View Unchanged
|
|
Nice exploration. I think there's value in the "drill down" behavior but you could argue that it's not something that should be specific to "content only". For content only it navigates to the "locked container" but it can just navigate to the parent for regular blocks/mode. |
This was referenced Sep 12, 2024
|
This is a bit stale. Going to close. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
When in contentOnly allow drilling down into sub blocks to show the full inspector panel.
Why?
See #60021
How?
Just a UX experiment. Effectively removing one condition to test whether it feels right.
Testing Instructions
This is an experiment only...
templateLock: contentOnly.Contentsection in the inspector controls.Testing Instructions for Keyboard
Screenshots or screencast
Video
Screen.Capture.on.2024-08-30.at.12-15-31.mp4