-
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
Ariakit: Update to v0.4.10 #64637
Ariakit: Update to v0.4.10 #64637
Conversation
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: +69 B (0%) Total Size: 1.77 MB
ℹ️ View Unchanged
|
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.
Things are looking good after an initial smoke test.
Should we migrate store.useState( stateProp )
to useStoreState(store, stateProp)
(new 0.4.9 feature), or is it unnecessary / premature?
I'm planning to do it in a follow-up PR. |
Now that the dependency was correctly updated, we'll see some failures related with the |
Adding |
Yup, seems like it might be coming from here: ariakit/ariakit#4018 |
I'm surprised that the changed you linked affected us, since we never set Basically, it's unexpected to me that we have to set it explicitly, since I thought it already always defaulted to (cc @diegohaz in case he can clarify why this is happening) |
@@ -220,6 +220,7 @@ const UnforwardedTabPanel = ( | |||
showTooltip={ !! tab.icon } | |||
/> | |||
} | |||
accessibleWhenDisabled |
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.
We may to have to do the same for the Tab
component
diff --git a/packages/components/src/tabs/tab.tsx b/packages/components/src/tabs/tab.tsx
index e1aa85c636..8ab67e1ca9 100644
--- a/packages/components/src/tabs/tab.tsx
+++ b/packages/components/src/tabs/tab.tsx
@@ -26,6 +26,7 @@ export const Tab = forwardRef<
const instancedTabId = `${ instanceId }-${ tabId }`;
return (
<StyledTab
+ accessibleWhenDisabled
ref={ ref }
store={ store }
id={ instancedTabId }
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.
Done in 3128041.
Agreed it's surprising - it is also documented to be |
Note that ariakit/ariakit#4018 seems to be specifically removing the default |
Yes! 🤦🏽♂️ That was unintentional. |
Here's a quick PR to reverse it with as little changes as needed: ariakit/ariakit#4056 cc @diegohaz |
Flaky tests detected in 3128041. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/10470709928
|
Currently blocked by ariakit/ariakit#4056 Will resume when there's a minor version that fixes the default of |
This suggests reverting the unintended changes caused by #4018 See WordPress/gutenberg#64637 (comment) --------- Co-authored-by: Haz <hazdiego@gmail.com>
OK, I've updated to the latest version with the Should be ready for another look! |
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.
🚀
Co-authored-by: Marco Ciampini <marco.ciampo@gmail.com>
* Ariakit: Update to v0.4.9 * CHANGELOG * Deduplicate some ariakit dependencies * TabPanel: keep tabs accessible when disabled * Tab: enable accessibleWhenDisabled specifically * Bump to 0.4.10 * Revert "TabPanel: keep tabs accessible when disabled" This reverts commit 44ede08. * Revert "Tab: enable accessibleWhenDisabled specifically" This reverts commit 3128041. * Fix CHANGELOG Co-authored-by: Marco Ciampini <marco.ciampo@gmail.com> --------- Co-authored-by: Marco Ciampini <marco.ciampo@gmail.com> Co-authored-by: tyxla <tyxla@git.wordpress.org> Co-authored-by: ciampo <mciampini@git.wordpress.org> Co-authored-by: diegohaz <hazdiego@git.wordpress.org>
What?
Updates
@ariakit/react
to the latestv0.4.10
.I'm planning to use the new APIs in subsequent PRs.
Why?
Mostly to consider a few fixes and the new
useStoreState
API that helps with React Compiler compatibility. Will be done in another PR.How?
Just updating the dependency and resolving test failures where necessary.
Testing Instructions
Composite
,CustomSelectControl
,DropdownMenuV2
,RadioGroup
,TabPanel
,Tabs
,ToggleGroupControl
,Tooltip
,Toolbar
)Testing Instructions for Keyboard
Verify all the above components are navigable with keyboard navigation like before.
Screenshots or screencast