-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Make the useDisabled hook stable #40890
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
Conversation
|
Size Change: -18 B (0%) Total Size: 1.24 MB
ℹ️ View Unchanged
|
0263779 to
0b74ee1
Compare
0b74ee1 to
208d061
Compare
|
Not sure if this needs a dev note for 6.1 release. Adding label just in case. |
|
@mburridge together with #40631 It might be a good Dev Note. What do you think @youknowriad |
|
This would be good as part of a general "new apis" dev note if there's such thing. On its own, it's pretty light. |
|
The part about useDisabled could be as follows. useDisabledIn some circumstances, such as block previews, all focusable DOM elements |
What?
This PR just removes the "experimental" status from the useDisabled hook. The Disabled component has been around for some time now and this just makes it more easy to use without extra wrappers.
Testing Instructions
Nothing to test here really, there are no functional changes to the hook itself.