-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Details: fix multiselect in Chrome #55888
base: trunk
Are you sure you want to change the base?
Conversation
Size Change: -2 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
The initial details block was very different from what we have today. The style settings that where once proposed were removed. |
Flaky tests detected in 422b301. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6769143990
|
With #53282, this block now supports block spacing. So wrapping the content in a div will make a big difference in layout. In other words, in this PR, the block spacing settings are only applied to elements within the content, so no space is applied between the summary element and the first element of the content. Editor (This PR)Editor (Trunk)FrontendI don't have a strong opinion on whether space should also be applied between the summary element and the content, but I think at least the markup on the editor side and the front end side should match. |
What?
Fixes #55671.
Unfortunately this seems to be a bug in Chrome. In Safari and Firefox it's working correctly. Here's a simple reproducible case: https://codepen.io/iseulde/pen/poGRjYK
A simple workaround is to wrap all the details content in a div.
Tbh, I'm not sure why we didn't save the content in a div from the start, it would add a lot more styling options on the front-end as well. Right now you can't pad and colour all contents for example. Should we add the div in the save function as well?
Why?
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast