Hi there
Working with grid component, Batch editing Mode, When I do not want to allow edition to the last column the tab keyboard is not working as expected it seems is getting stopped in the last column and does not dow to the next row as is expected. This only happens when the last column does not allow editing, if you set the AllowEditing to true it goes to the next row.
I also noticed when I set AllowEdition to false in any column it is necessary to press the tab keyboard twice to go to the next cell.
Adding a demo project.
public async void KeyDownHandler(KeyboardEventArgs args, int? OrderID, string leftField)
{
if (GridInstance.IsEdit && args.Key == "Tab")
{
var rowIndex = await GridInstance.GetRowIndexByPrimaryKeyAsync(OrderID); await GridInstance.EditCellAsync(rowIndex + 1, leftField);
}
}
|
Hi
Thanks for the answer, but if I do not know which one will be my last editable column (columns can be showed and hidden by column chooser). For example, if I have an editable column hidden in my column chooser And I decide to show it to the grid the tab won't go to the next editable cell but will automatically go down to the next row.
Another example is if the user decides to hide the column with the edit template and show other columns, the bug of the TAB keyboard will be still present.
I mean is a workaround but not a solution where the bug is not present anymore, I think using edit templates for all of the columns just for that is not okay since we have to bind values and be aware of the component rendered in each column when we have de EditType prop for a column.
In that case, can this be considered a bug?
Thanks for the answer It is already working fine, in the version you mention, think not big issue to use just templates for id