-
Notifications
You must be signed in to change notification settings - Fork 76
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
Epic: consistent disabled prop behavior #2655
Comments
@Esri/calcite-design-representatives can you chime in on this one? |
IMO only interactive components should have a Maybe all we need to ask is does the component need to prevent interaction? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Installed and assigned for verification. |
verified on beta.80 |
#2582 surfaced an issue where some of our components may not be implementing
disabled
appropriately. This epic should help us ensure all components implement this property correctly and prevent keyboard/pointer interaction with the element as well as its children (if applicable).Action plan
disabled
prop (including parent-child interactions):Questions
disabled
prop or only interactive ones?Related issues
The text was updated successfully, but these errors were encountered: