Info
Follow-up from #3858 / PR #4128. Icon Button's disabled state now shows cursor: not-allowed so disabled controls read as unavailable instead of inert.
Button still uses the old pattern (pointer-events: none plus the default arrow cursor), so the two components behave differently when you hover a disabled control.
One note from the Icon Button work: pointer-events: none has to come off for any cursor to render. That means hover styling needs explicit suppression (:not(:disabled) guards on the hover rules), and title tooltips start appearing on disabled hover. That side effect should be a deliberate decision here too.
Acceptance Criteria:
- Disabled Button (all types and variants) shows
cursor: not-allowed on hover
- No hover styling applies while disabled; click/submit behaviour unchanged
- Browser test covering the computed cursor and no event dispatch (pattern exists in
icon-button.browser.spec.tsx)
Info
Follow-up from #3858 / PR #4128. Icon Button's disabled state now shows
cursor: not-allowedso disabled controls read as unavailable instead of inert.Button still uses the old pattern (
pointer-events: noneplus the default arrow cursor), so the two components behave differently when you hover a disabled control.One note from the Icon Button work:
pointer-events: nonehas to come off for any cursor to render. That means hover styling needs explicit suppression (:not(:disabled)guards on the hover rules), andtitletooltips start appearing on disabled hover. That side effect should be a deliberate decision here too.Acceptance Criteria:
cursor: not-allowedon hovericon-button.browser.spec.tsx)