-
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
Style Book: do not use Composite store #65047
Conversation
Size Change: -32 B (0%) Total Size: 1.78 MB
ℹ️ View Unchanged
|
Flaky tests detected in eaf7a18. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/10698618119
|
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and tests well 👍
Something I've noticed is that there's a tab stop between the menu and the style book block examples. Haven't dug deeper, but it looks like it's focusing the iframe itself. This is pre-existing, but something to note and potentially fix.
Yeah, I noticed that too — it was added in #48664 by @andrewserong , who added this paragraph in the PR description:
We can't set
Not sure how solid (and worth our time) this would be. |
We could open an issue so it's documented, but I believe this isn't a big priority. |
What?
Extracted from #64723
Do not use Composite's store directly in the Style Book
Why?
See #63704 (comment)
How?
We recently made changes so that:
Composite
component accepts the same props asuseCompositeStore
;Composite
subcomponents already receive the correctstore
without need for the consumer to pass it explicitlyTherefore, we can migrate from
to
Testing Instructions
trunk
— ie. it is one tab stop, and using up/down arrow keys moves the focus on the other list items. Since the orientation isvertical
, using left/right arrow keys should not move focus across the listScreenshots or screencast
Kapture.2024-09-04.at.12.55.03.mp4