-
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
Block Editor: Fix the 'Reset all' bug for the 'ResolutionTool' component #68296
Conversation
Size Change: +21 B (0%) Total Size: 1.84 MB
ℹ️ View Unchanged
|
Flaky tests detected in 43a244e. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12493384209
|
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!
packages/block-editor/src/components/resolution-tool/stories/index.story.js
Show resolved
Hide resolved
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. |
Thanks for testing, @t-hamano! |
What?
PR fixes a bug in the
ResolutionTool
component that occurs when it fails to rest a value via the "Reset all" action. I've also updated the story to match the editors' current design/behavior (see screencasts).Why?
Noticed while working on #68294.
When the consumer doesn't control the
ToolsPanel
, resolution tools might need to implementresetAllFilter
.Testing Instructions
npm run storybook:dev
.Testing Instructions for Keyboard
Same.
Screenshots or screencast
Before
CleanShot.2024-12-25.at.16.48.26.mp4
After
CleanShot.2024-12-25.at.16.48.48.mp4