-
Notifications
You must be signed in to change notification settings - Fork 78
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
[List/List Item] Add non-interactive option to remove hover/pointer changes #8634
Comments
➕ from me on this one. |
Another option could be an ‘interactionMode’ prop with “static” / “interactive” values like we added in Table. Maybe not quite the same but it could enable this in all selection modes, not just a single one. This could make the label area non focusable / hoverable in all selection modes, leaving the selection affordance and any action-slots interactive. |
Not sure how that would work in |
Broad question about this one. Is this a selection mode or is it something that would disable selection modes altogether? Like readOnly? If readOnly, does that then get confusing when actions are slotted? Maybe not? |
Added design recommendations to the top. @geospatialem Not sure if we want to update the title or anything else? |
…nter changes. (#10473) **Related Issue:** [#8634](#8634) ## Summary - Add `interaction-mode="interactive" (default) | "static"` prop. - Setting `interaction-mode="static"` and `selection-appearance="icon"` removes hover/pointer changes from main content area. - Setting `interaction-mode="static"` and `selection-appearance="border"` falls back to interactive hover/pointer changes and logs console warning message. - Setting `interaction-mode="static"` and `selection-mode="none"` removes hover/pointer changes.
Installed and assigned for verification. |
…nter changes. (#10473) **Related Issue:** [#8634](#8634) ## Summary - Add `interaction-mode="interactive" (default) | "static"` prop. - Setting `interaction-mode="static"` and `selection-appearance="icon"` removes hover/pointer changes from main content area. - Setting `interaction-mode="static"` and `selection-appearance="border"` falls back to interactive hover/pointer changes and logs console warning message. - Setting `interaction-mode="static"` and `selection-mode="none"` removes hover/pointer changes.
Check existing issues
Description
We restored
list
's pointer and hover states for consistency in #6700, as it was previously supported and discussed when implemented in #6123.We should add a new selection mode to remove the hover/pointer behavior for someone that wants the existing
selectionMode
of"none"
and different styling.Acceptance Criteria
Add a new selection mode to remove the hover/pointer behavior for someone that wants the existingselectionMode
of"none"
and different styling.Maintain the restored pointer behavior whenselectionMode
is"none"
chip-group
andchip
should also have similar behavior. If so, a new issue, or issues if multiple components are impacted, can be createdchip
is used on its own or in achip-group
withselection-mode="none"
they are not interactive.Relevant Info
Created as a result of the efforts of #6700 and related #6123.
Refer to #6700 (comment) for more details.
This would also close #5664 based on this comment.
Which Component
list
list-item
Example Use Case
2.2.0
example with default: https://codepen.io/geospatialem/pen/ExMvGZJ2.2.1-next.1
example with pointer: https://codepen.io/geospatialem/pen/XWGaopOPriority impact
p4 - not time sensitive
Calcite package
Esri team
Calcite (dev)
Calcite Design Solution
Based on team discussion, we recommend the following:
Add an
interaction-mode=“interactive” (default) | “static”
prop.static
removes interaction styling and pointer changes.If using
static
withselection-mode="single" | "single-persist" | "multiple"
, theselection-appearance
modes would be affected in the following ways:selection-appearance=“icon”
would still function in thestatic
mode. The icon would remain the hit area for selection, but interaction styling and pointer changes would be removed from the main content area.selection-appearance=“border”
would conflict withstatic
mode.interactive
may make the most sense here as falling back to an icon appearance feels more disruptive and could be potentially more difficult for a user to debug.The text was updated successfully, but these errors were encountered: