There is a ticket in PAR backlog for clickable card…but it is a variant of the card component
Seems like the card has some specifics about spacing and tiling, does this have that
Needs to support a spacing POV
Is it a variant of the card, or it’s own thing, implementation wise
If anything is really different form the card, it might be need to be it’s own component
since it’s a form element, it does have some differences in how the card is use, like error handling and a11y
Is there a way to enforce the non-clickable-ness?
Not really
Jeff; Not good to have clickable elements inside the card
Jenn: Some use case could use a link, there may be future use cases.
A variant could be created if the selectable box needs to include a link or something clickable
Two a11y concerns, focus confusion with the box and elements clickable within it, will throw warnings. new click target minimum sizes, it needs clearance 24x24px. No objection to multiple actions…but we should not show focus on the card itself if there are clickable thing
Adam S: If there is no radio button or input field, is there concern from a11y POV? Jeff: Make it the same selectable element, but just hiding the element is fine
Does the icon button have an active state? Technical questions
Any feedback about how this is fitting in, repsonsive behavior?
Concern: in the case where it is supporting both view and card view, if there is ability select rows in the table view, can you still select cards or do you lose that capability? We would lose sorting and selection capabilities.
Starting use case, no selectable items or sorting
Can iterate if the use case becomes challenging
Icon button: can we use the icon button and an active state.
Not currently supported, but we can tack that onto the work.
Background color, you can use inverted colors, check the documentation
Popover should be tool tip instead, for hover instead of click
Action items
Add action items to close the loop on open questions or discussion topics:
Hilary Gordon (Deactivated) Clarify spacing for the card. Cards are used in isolation, but this does inehrent spacing, we need that built in as a spec
Jennifer Gregory clarify selectable and sortable functionality of the table in card view. Create ticket in PAR board
Decisions
Type /decision to record the decisions you make in this meeting:
e06b3d04-88cb-429d-ae58-cf2e59008748DECIDEDd4b43642-c39a-45ce-9b9a-8ad5705315e3Selectable Card component is a distinctly different component compared to the standard card component203313c8-da13-4064-a288-ebe1ec57f6a8DECIDEDSelectable Card component should not have clickable elements within it for the MVP..only the card itself should be clickable, have focus, show an error state. Revisit if the need grows or becomes challengingbcda7a39-fad9-47a9-b408-0476a6e57da7DECIDEDJennifer Gregory Toggle switch for Data Table can be put into PAR JIRA, just note if there are any additional specs details that werent discussed live in PWG
Selectable Card component is a distinctly different component compared to the standard card component
Selectable Card component should not have clickable elements within it for the MVP..only the card itself should be clickable, have focus, show an error state. Revisit if the need grows or becomes challenging
Jennifer Gregory Toggle switch for Data Table can be put into PAR JIRA, just note if there are any additional specs details that werent discussed live in PWG