-
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
Site Editor: Start in Select mode #30187
Conversation
Size Change: +12 B (0%) Total Size: 1.41 MB
ℹ️ View Unchanged
|
Could this be beneficial for the post editor too? |
@ellatrix no idea, I've opened this PR for @jameskoster to play around 😄 |
Thanks @Copons :) I think there could be potential here. It certainly seems sensible for the modes to behave consistently regardless of whether you're in the site or post editor. And as templates are often more complex in terms of nesting, Select mode feels like a suitable default in the Site Editor. As a next step for this branch, it would be cool to revert the outline effects we currently see in edit mode in the site editor, so that it matches the post editor. Then we can explore updating the outline styles in Select mode based on the recent design work. I should be able to help with that part :D The one thing I'm struggling with a bit is how one gets back to Select mode when they're done editing a block. It should be a simple interaction that doesn't require clicking the mode selector. Clicking an empty space to deselect the current block and switch to the default mode makes sense. But there may not always be empty space, or the empty space may not be obvious. In #27849 (comment) the idea of having a "frame" of empty space around the template in the site editor has gained some traction, so perhaps that could serve this purpose. Edit: One oddity I noticed, and should be addressed – when Select mode is active in the post editor you have to click through container blocks to select the children. In the site editor you select the children directly. The post editor behaviour is preferred. This would effectively implement the click-through pattern explored in #30156 |
Description
How has this been tested?
Screenshots
Types of changes
Checklist: