-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Disabled html attribute is not set on Button if passed in as prop to MenuItem #7816
Comments
As far as I have tested, |
I have investigated this further and found that |
This reverts commit 0f37665. Fixes chakra-ui#7269, chakra-ui#7816 and chakra-ui#7905 and also enables the only currently known workaround for chakra-ui#7965. Removing the ability to use the disabled-prop posed a breaking change, which is hereby fixed.
* Revert "refactor: button disabled prop" This reverts commit 0f37665. Fixes #7269, #7816 and #7905 and also enables the only currently known workaround for #7965. Removing the ability to use the disabled-prop posed a breaking change, which is hereby fixed. * docs: update --------- Co-authored-by: Segun Adebayo <joseshegs@gmail.com>
@Mikunj #8462 has been merged, If satisfied, you may close this issue, the fix should be shipping with Chakra 2.8.3. |
Awesome 🎉, seems to work as intended now 😃 |
Description
If you pass in a
Button
as anas
prop toMenuItem
and disable it, it will not render with thedisabled
html attribute. Everything else works as expected: Button cannot be clicked, menu item cannot be focusedThis issue is not present in
@chakra-ui/button: "2.0.15"
Examples
Link to Reproduction
https://codesandbox.io/s/modest-hoover-yfrdt6?file=/src/index.js
Steps to reproduce
No response
Chakra UI Version
2.7.1
Browser
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: