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
{{ message }}
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
Reproducing this turned out to be a little more subtle than just making the entire table readonly. The problem arises when the navigation goes through an editable cell.
If all cells are readonly, the initial mouse click will set the focus on some <td> and it will remain there through keyboard navigations.
If rows are not all readonly, keyboard navigation will eventually be on an editable cell and the focus will change to be on an input. When the focus changes to another editable cell there's no problem: the focus is moved to the new input, but if a readonly cell is selected, there is no focused element. Making it impossible to move the selection through the keyboard anymore.
Using the standalone app (for simplicity, will be the same with callbacks).
Not sure when this regression appeared, probably
<=1.0.0
.Modify
eee
andfff
columns indata.ts
withNavigating with the keyboard, upon reaching columns
eee
orfff
, won't be able to move from the cell afterwards.The text was updated successfully, but these errors were encountered: