Stabilize Accordion block#72036
Conversation
9c45b6e to
474561c
Compare
|
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: -17 B (0%) Total Size: 1.95 MB
ℹ️ View Unchanged
|
474561c to
d933127
Compare
| await expect( | ||
| page.getByText( | ||
| '2 results found, use up and down arrow keys to navigate.' | ||
| '3 results found, use up and down arrow keys to navigate.' |
| await settingsPanel | ||
| .getByRole( 'button', { name: 'Heading', exact: true } ) | ||
| .click(); |
There was a problem hiding this comment.
To avoid the Accordion "Heading" block
|
Flaky tests detected in db0d187. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/18221968617
|
|
This is very cool!! Quick drive-by comment: we probably want to add |
|
Thank you for your great work on it @t-hamano 🙌 |
ntsekouras
left a comment
There was a problem hiding this comment.
Thanks @t-hamano! Besides the small comment about the fixtures this looks good!
I believe it's fine to add contentRole in follow up to properly focus on the behavior we want.
Also noting that here we've caused block invalidation in the editor, but I guess it's fine since the block was experimental and the front end seems to work fine.
|
Thanks @t-hamano for working on this, this is coming together so well! I tested this PR in Playground. Here are my findings:
to something like
I wouldn't mention the plus, because when open, it's a cross/X. |
|
Thank you everyone for your feedback! I'll collect all the feedback suggested here and submit it as a new issue later. All tasks should be addressed in the 6.9 release. To @ntsekouras:
Yes, this is expected. That's why I didn't stabilize this block until the very end. Once stabilized, we need to maintain backward compatibility. To @hanneslsm:
This is expected behavior, as the current toggle icon is not editable. In the future, we may consider customizing the icon.
I think we should remove the content width support from the Accordion Item block. The parent Accordion block supports content width, and users will typically want to change the width of all accordion items at once.
This is likely due to the following style being applied: h1.has-background, h2.has-background, h3.has-background, h4.has-background, h5.has-background, h6.has-background {
padding: 1.25em 2.375em;
}In my opinion, this padding should not be applied to the Accordion Heading block. |
These sound good. Let's do it. |
Done here #72045 |
Done in Accordion Heading: Remove the padding from the heading when it has a background color |
|
@scruffian Thanks for the quick fix! The only remaining task may be to add |
|

What?
Closes #71732
Stabilize Accordion Block for the 6.9 release.
Why?
We've identified and resolved the tasks that need to be resolved before stabilizing this block. There are a few open sub-issues, but we believe they're all minor bugs that will be resolved in the 6.9 release.
I hope you'll take a fresh look at this block and see if it's worth stabilizing. We look forward to your feedback!
cc @mikachan @hanneslsm @joedolson @WordPress/gutenberg-core
How?
Testing Instructions