You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I think you could tag this as a feature request. I noticed there was some similar discussion regarding VirtualScroll/List in #156.
My use case is essentially a spreadsheet-type editor using an arrangement of Grid components that is essentially a hybrid between the ArrowKeyStepper (for arrow key navigation) and ScrollSync (for fixed header col/row) examples. I'm listening for certain events (e.g., clicking a cell or typing Enter) to begin "editing" a cell's contents, at which point an input in that grid cell becomes focused.
I would like to propose a way to somehow disable the arrow key behavior for the ArrowKeyStepper component, either with a prop or perhaps some kind of check for focus on an input.
Sorry if this request has been fulfilled or can already be achieved, the library changes quickly and can be difficult to follow all of the changes (I'd say that's a good thing though!).
The text was updated successfully, but these errors were encountered:
Hi, I think you could tag this as a feature request. I noticed there was some similar discussion regarding VirtualScroll/List in #156.
My use case is essentially a spreadsheet-type editor using an arrangement of
Grid
components that is essentially a hybrid between theArrowKeyStepper
(for arrow key navigation) andScrollSync
(for fixed header col/row) examples. I'm listening for certain events (e.g., clicking a cell or typingEnter
) to begin "editing" a cell's contents, at which point an input in that grid cell becomes focused.I would like to propose a way to somehow disable the arrow key behavior for the
ArrowKeyStepper
component, either with a prop or perhaps some kind of check for focus on an input.Sorry if this request has been fulfilled or can already be achieved, the library changes quickly and can be difficult to follow all of the changes (I'd say that's a good thing though!).
The text was updated successfully, but these errors were encountered: