Missing micro-interactions in table
See original GitHub issue- Keyboard shortcuts (using
<Hotkey>
)- Copy
cmd+c
-
Paste(can’t do because table is data agnostic, we don’t know what data you’re putting in there)cmd+v
- Move selection
up
/right
/bottom
/left
- Select the cell immediately to the right
tab
- Select the cell immediately below
return
- Select the cell immediately to the left
shift+tab
- Select the cell immediately above
shift+return
- Type any character to edit
- Copy
- Right-click menu
- When the right-click menu is open, we should block scrolling
- Right-click menu should be dismissed when clicking outside of it
- Right-clicking on a selection shouldn’t change the selection
- Right-clicking on a cell should select said cell
- Right-clicking on a column should select said column
- Right-clicking on a row should select said row
- Editable (header) cells
- Clicking outside of an cell being edited should disable editing
- Ability to click on the edited text to place cursor and make a text selection with the mouse
- Make editable cells and editable header cells consistent
- Selection
- Clicking on “…” in cell shouldn’t select the cell, similarly to other “…” (header for instance)
- Column headers and row headers should reflect the current selection
- Clicking on a selected cell shouldn’t deselect it. Cmd+clicking on a cell should deselect it. (#1073)
- Range select rows/columns
shift+click
- Add rows/columns/cells to selection
cmd+click
- Add to selection rectangle
cmd/shift+up
/cmd/shift+right
/cmd/shift+bottom
/cmd/shift+left
- Clicking on a cell and dragging out of the table should widen selecting the active selection region
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:8 (5 by maintainers)
Top Results From Across the Web
5 Mistakes to Avoid When Designing Micro-interactions
5 Mistakes to Avoid When Designing Micro-interactions · 1. For the love of god, restrain yourself · 2. Don't sacrifice your narrative on...
Read more >Improve UX through Microinteractions (with Examples)
A micro-interaction is a deadly weapon of a UX designer that can add fun and ease of use to any design. Here's how...
Read more >Micro-interactions: why, when and how to use them to improve ...
Anything a user sees, hears, or feels while a microinteraction is happening is feedback. Loops and Modes determine the meta-rules of the microinteraction....
Read more >Powerful Microinteractions to Improve Your Prototypes - UXPin
Microinteractions are rarely noticeable until they're notactually there. To make your prototype come alive, use these microinteractions.
Read more >9 Microinteractions to Inspire Your Next Project - UX Planet
Microinteractions, paired with a well-planned design, ... Without error alerts, you'd be clueless and lost in your journey through the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@llorca These look great – can’t wait!
Any thoughts on adding onCellDoubleClick/onRowDoubleClick callbacks? I’m trying to build a “library”-esque table component where rows are a single item in one’s inventory with different columns being attributes of the item. Users should be able to double click to “open” up an item. My solution so far feels a bit hacky – and is ugly without one of the above proposed fixes: “Clicking on a selected cell shouldn’t deselect it. Cmd+clicking on a cell should deselect it.”
It also forces me to write some css so that the clickable div fills the whole cell instead of just the cell text (Ideally I’d be able to hook in at a higher level like the Table component and have an “onRowDoubleClick”.
Thanks for the great component 😃
Just checked off a bunch of these