-
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
Upgrade Reakit to version 1.3.4 #28013
Conversation
Size Change: +4.07 kB (0%) Total Size: 1.3 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.
🎉
Thanks @diegohaz 👍🏻 I raised that in the past, it looks like we should look into how we could stop duplicating bundled code from Reakit: We could add shared APIs to gutenberg/packages/a11y/src/index.js Line 40 in 61f57f4
Any thoughts? |
@gziolo I don't really know how to interpret that table. I expect that when we use both |
The issue exists inside the WordPress core/Gutenberg plugin. It won't be an issue for JS apps that use one entry point and code splitting. We have a long list of entry points. They are externalized between each of them and referenced through |
That makes sense! Why do you think that line ( |
It might be my personal resistance to side effects in packages. Maybe we could lazy execute it when |
@youknowriad, is #28013 (comment) something we should plan for WordPress 5.7 or you think we can delay further? |
Do you think the solution here could be to use components from "Components" that rely on reakit instead of using reakit directly in the other packages? |
Yes, that would work as well since |
This PR upgrades Reakit to version 1.3.4.
The most relevant feature is that composite items are now automatically sorted when their position change in the DOM, so we don't need to call
unstable_sort()
manually anymore.Changelog since v1.1.0
1.3.4 (2021-01-06)
Bug Fixes
CompositeItem
tabIndex fix (#821) (1390d31)1.3.3 (2021-01-03)
Bug Fixes
CompositeItem
withtabindex=0
on the first render (#817) (3d81514)1.3.2 (2020-12-11)
Bug Fixes
state
prop (#799) (a21bb2b), closes #798Menu
scroll jump (#801) (96f5dd5), closes #7511.3.1 (2020-11-26)
Bug Fixes
Dialog
(#793) (d9a49ef)1.3.0 (2020-11-12)
Features
Role
component (#728) (5fa51a7)shift
option touseCompositeState
(#727) (7861395)Combobox
component (#688) (ad7063b)includesBaseElement
option touseCompositeState
(#726) (cf3ba56)onChange
when settingCompositeItemWidget
value (0b5b3cb)1.2.6 (2020-11-12)
Bug Fixes
unstable_virtual
option on mobile devices (#783) (ecdc4ef)Composite
(#784) (9bcbfe6)1.2.5 (2020-09-22)
Bug Fixes
Composite
infinite loop on Firefox (#748) (4a1c644), closes #747disabled
prop being passed to elements that don't support it (#725) (d982a61), closes #722as
prop (#736) (c594166)1.2.4 (2020-09-03)
Bug Fixes
1.2.3 (2020-08-24)
Bug Fixes
1.2.2 (2020-08-17)
Bug Fixes
focus
method exists on the dialog disclosure element (#710) (85dd073)Composite
for React 17 (#711) (0ad76e6)unstable_virtual
istrue
on React 17 (#715) (81ec3a3)focus
/blur
event order inComposite
(#713) (891976b)1.2.1 (2020-08-13)
Bug Fixes
RadioGroup
s (#703) (212adbd), closes #7021.2.0 (2020-08-06)
Features
Grid
component (#685) (51e17fb)composite.sort
method (#690) (1f66168)id.setBaseId
method (#691) (5c52c71)Menu
instead ofMenuItem
on mouse click onMenuButton
(#694) (d57b97f)1.1.2 (2020-07-18)
Bug Fixes
composite.unstable_sort
on Firefox (f973f77)Dialog
focus loss (#682) (8ae0da7), closes #677MenuButton
not receiving focus afterMenu
closes (#692) (e649f20)1.1.1 (2020-06-21)
Bug Fixes
Composite
references (9d9eff2), closes #667 (comment)