Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Block Editor: Disable click-through on desktop. #17239
This PR disables inner block click-through on large,
As expressed in #16888 and #17088, click-through degrades the experience on larger viewports. If the viewport is large enough to click on block paddings, we don't need the click-through behavior to edit inner blocks, so it adds unnecessary friction.
That said, we could revisit the feature in another form for a future release.
How has this been tested?
It was verified that click-through is disabled on large,
Types of Changes
New Feature: Disable click-through on larger viewports where just clicking on paddings is viable and requiring multiple clicks to edit inner blocks degrades the experience.
Thank you for this! For anyone curious about more context, and what happens next, I'd like to share some here.
The goal of the "clickthrough" (aka parent-first) interface was to make it easy to select any layer of a block that features nesting. Consider the columns block, where you have to select individual columns to set their dimensions. With the clickthrough interface in place, it's trivial to dig through and configure each layer of a block. That's one example, but there is no limit to how deep a block can nest, and when each layer can have properties, it's important to think about how we can provide simple access to each of those layers.
Even if that interface probably still needs refinement — visual feedback, shortcut keys and the like — it's still definitely a layout first interface. Which is only one half of a block editor.
The other half is editing and writing, and unfortunately that experience suffered from the clickthrough interface. Being able to click the label of a deeply nested Button block and edit it is virtually unbeatable as far as editing templates, which are likely to grow in capabilities soon.
So, in the name of refining the clickthrough experience, it's good to disable it for now to give it more time in the oven. Those refinements are tracked in two tickets I'd recommend you watch if you want to follow along:
@epiqueras There's something wrong with the milestones. Should that be 6.5? Its marked as "Future" (and some others too): https://github.com/WordPress/gutenberg/issues?q=is%3Aclosed+milestone%3AFuture
Yeah, 6.5 is not created yet. They get added when preparing the next release I think.…
On Thu, Aug 29, 2019 at 6:37 PM SchneiderSam ***@***.***> wrote: @epiqueras <https://github.com/epiqueras> There's something wrong with the milestones. Should that be 6.5? Its marked as "Future" (and some others too): https://github.com/WordPress/gutenberg/issues?q=is%3Aclosed+milestone%3AFuture — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#17239?email_source=notifications&email_token=AESFA2F3T5GIFEFGGLG2J2DQHB2XNA5CNFSM4IRLOOTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5QIZ2A#issuecomment-526421224>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AESFA2BSA7J5WTU2PH4ISL3QHB2XNANCNFSM4IRLOOTA> .