Replies: 1 comment 1 reply
-
| I believe you're looking for #2585 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
-
| I believe you're looking for #2585 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Heyo. I’m working with the React Aria
Table(via React Aria Components) and ran into an interaction limitation that I wanted to ask about and get your thoughts on.Context
We have a table with:
selectionMode="multiple"(row selection enabled)A common user expectation for this type of UI (similar to file explorers or data grids) is:
Problem
Currently, text selection inside table cells is effectively disabled.
From what I understand, this is due to the
usePressinteraction model, which intentionally disables text selection during press interactions.This makes sense for consistent press behavior, but it creates a limitation:
What I’ve tried
I was able to partially work around this by preventing the press interaction from reaching the row (I think I read this somewhere in a comment Devon made):
This allows text selection to work, but:
onPointerDownCaptureseems more reliable, but still not idealWe (the design system team) also suggest to our users to use a copy button. However our users (product teams) don't always know what data is going to be in the table. Or which cells may be the ones their users will want to copy.
Question
Is there a recommended pattern for supporting this kind of mixed interaction?
More specifically:
allowTextSelectiononTable/Row/CellSummary
Would love to hear how you’d recommend approaching this.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions