-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[Bug]: WC Menu-Item, disabled state usability issues #21337
Copy link
Copy link
Labels
browser: chromebrowser: firefoxcomponent: menucomponent: menu-buttonneeds: community contributionDue to roadmap and resource availability, we are looking for outside contributions on this issue.Due to roadmap and resource availability, we are looking for outside contributions on this issue.package: @carbon/web-components@carbon/web-components@carbon/web-componentsseverity: 4https://ibm.biz/carbon-severityhttps://ibm.biz/carbon-severitystatus: help wanted 👐type: bug 🐛
Metadata
Metadata
Assignees
Labels
browser: chromebrowser: firefoxcomponent: menucomponent: menu-buttonneeds: community contributionDue to roadmap and resource availability, we are looking for outside contributions on this issue.Due to roadmap and resource availability, we are looking for outside contributions on this issue.package: @carbon/web-components@carbon/web-components@carbon/web-componentsseverity: 4https://ibm.biz/carbon-severityhttps://ibm.biz/carbon-severitystatus: help wanted 👐type: bug 🐛
Type
Fields
Give feedbackNo fields configured for Bug.
Projects
StatusShow more project fields
✅ Done
Package
@carbon/web-components
Browser
Firefox, Chrome, Edge
Package version
2.46.0
React version
No response
Description
The disabled state of the menu-item has several usability issues:
pointer: not allowedis not applied to the entire component, meaning dependant on where your cursor is you may or may not see it.Reproduction/example
https://stackblitz.com/edit/github-6pjxlxo4?file=index.html
Steps to reproduce
See the item in a disabled state, interact with it.
Suggested Severity
None
Application/PAL
No response
Code of Conduct