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
When a sheet is locked but has a few cells unlocked, and those cells have custom editors, the editor in a cell is not displayed when the selection is moved from a locked cell to an unlocked cell via the keyboard. Selecting the cell with the mouse does display the editor.
The problem is in SelectionHandler.onCellSelectedWithKeyboard(...). At the end it has these lines:
however, newSelectedCellSet() expects the selected cell values to already be changed, in particular the spreadsheet.cellLocked property. Since it still has the value from the previous selection, the logic doesn't flow properly.
However, just reversing the two lines causes a different problem, as the second line depends on the value of spreadsheet.customCellEditorDisplayed, which is set by the first call.
I have extended the component in my app to override the caller of this method and essentially repeat the first call after the second, but that's not the best solution. Since it works when clicking with the mouse, there should be a path to unifying the logic that behaves the same for keyboard and mouse navigation.
The text was updated successfully, but these errors were encountered:
When a sheet is locked but has a few cells unlocked, and those cells have custom editors, the editor in a cell is not displayed when the selection is moved from a locked cell to an unlocked cell via the keyboard. Selecting the cell with the mouse does display the editor.
The problem is in SelectionHandler.onCellSelectedWithKeyboard(...). At the end it has these lines:
newSelectedCellSet();
spreadsheet.updateSelectedCellValues(column, row);
however, newSelectedCellSet() expects the selected cell values to already be changed, in particular the spreadsheet.cellLocked property. Since it still has the value from the previous selection, the logic doesn't flow properly.
However, just reversing the two lines causes a different problem, as the second line depends on the value of spreadsheet.customCellEditorDisplayed, which is set by the first call.
I have extended the component in my app to override the caller of this method and essentially repeat the first call after the second, but that's not the best solution. Since it works when clicking with the mouse, there should be a path to unifying the logic that behaves the same for keyboard and mouse navigation.
The text was updated successfully, but these errors were encountered: