Hello,
Creating another thread for a another bug I believe relates to EditCellAsync is not properly editing the cell during tab press when SelectionMode Cell in Blazor | Feedback Portal (syncfusion.com)
While in batch edit mode, with the settings:
<GridSelectionSettings CellSelectionMode="CellSelectionMode.Box" Mode="Syncfusion.Blazor.Grids.SelectionMode.Cell" Type="Syncfusion.Blazor.Grids.SelectionType.Multiple"></GridSelectionSettings>
when you start editing a cell, pressing spacebar deselects the cell and you have to click the cell again to continue editing, afterwards, pressing spacebar works normally as it should (entering a white space character). Example app attached.
Hi Shannon,
Greetings from Syncfusion support.
Currently we are validating your query at our end and we will update further details within two business days on or before (13.04.2022). Until then we appreciate your patience.
Regards,
Monisha
Hi Paul ,
Thanks for contacting Syncfusion support.
We have validated and considered your query as a bug and logged the defect report “Pressing spacebar during batch edit focus out from the Edited state” for the same. Thank you for taking the time to report this issue and helping us improve our product. At Syncfusion, we are committed to fixing all validated defects (subject to technological feasibility and Product Development Life Cycle) and will include the fix in our upcoming patch release which is expected to be rolled out on or before mid of May, 2022.
You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.
Note: “Currently feedback is in review stage. It will be visible to you once validated’
Until then we appreciate your patience.
Regards
Monisha
Hi Shannon ,
Thanks for the patience.
We have validated and considered your query as a bug and logged the defect report “Pressing spacebar during batch edit focus out from the Edited state” for the same. Thank you for taking the time to report this issue and helping us improve our product. At Syncfusion, we are committed to fixing all validated defects (subject to technological feasibility and Product Development Life Cycle) and will include the fix in our upcoming patch release which is expected to be rolled out on or before mid of May, 2022.
You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.
Note: “Currently feedback is in review stage. It will be visible to you once validated’
Until then we appreciate your patience.
Regards
Monisha
Hello, Just following up to ensure this bug fix is still scheduled for this month?
Hi Shannon,
Greetings from Syncfusion.
Yes, we are currently working on this issue and it will be
included in our upcoming patch release which is
expected to be rolled out on or before 10th May, 2022. Until then we appreciate your patience.
Regards,
Monisha
Hi Shannon,
We are glad to announce that, we have included fix for the issue “Pressing spacebar during batch edit focus out from the Edited state” in our release(20.1.0.52). So please upgrade to our latest version of Syncfusion NuGet package to resolve the reported issue. Please find the Nuget package for latest fixes and features from below.
Nuget : https://www.nuget.org/packages/Syncfusion.Blazor.Grid
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.
Regards,
Monisha
Hi,
Thank you for all the hard work getting the bug fix out. Unfortunately it seems while this issue is fixed, it caused other bugs to appear:
<SfGrid DataSource="@Orders" Toolbar="@(new List<string>() { "Add", "Edit", "Delete", "Update", "Cancel" })" AllowPaging="true">
<GridEditSettings AllowAdding="true" AllowDeleting="true" AllowEditing="true" Mode="EditMode.Batch"></GridEditSettings>
<GridSelectionSettings CellSelectionMode="CellSelectionMode.Box" Mode="Syncfusion.Blazor.Grids.SelectionMode.Cell" Type="Syncfusion.Blazor.Grids.SelectionType.Multiple"></GridSelectionSettings>
Sorry, forgot to include in the latest example.
ShowConfirmDialog="false"
Hi Shannon,
Greetings from Syncfusion support.
We have checked your query and from your shared sample we could see that you have referenced scripts externally and we would like to inform that we have included breaking changes in loading scripts and styles in our latest version and javascript isolation is marked as obsolete from our version(20.1.0.47). So we suggest you to use any one of the below method to load styles and scripts externally.
Also refer the below release notes for your additional information.
Reference: https://blazor.syncfusion.com/documentation/release-notes/20.1.47?type=all#common
Example code snippet:
|
[layout.cshtml]/[Host.cshtml]
<link rel='nofollow' href=https://cdn.syncfusion.com/blazor/20.1.52/styles/bootstrap5.css rel="stylesheet"/> <script src=https://cdn.syncfusion.com/blazor/20.1.52/syncfusion-blazor.min.js type="text/javascript"></script>
|
Note: Need to disable javascript isolation while using the above ways( AddSyncfusionBlazor()).
We have modified your sample. Kindly check the attached sample for your reference.
Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/ServerApp-681889473.zip
If you still face any difficulties at your end then Kindly get back to us with an video demo of the issue to proceed further at our end.
Regards,
Monisha
Hi, thank you for the detailed response! Happy to say this has solved my issue :) Although I did notice that when pressing tab, the browsers tab menu was still selected in the first instance, but pressing tab again after that everything works fine. I managed to get around that by including some js code to prevent the default action.
/*prevent browser's tab menu from being focused when tabulating across cells in grid. */
document.addEventListener('keydown', disableTabKey);
function disableTabKey(e) {
if (e.key == "Tab") {
e.preventDefault();
}
}
Hi Shannon,
Thanks for the update
We are glad to hear that you have resolved the reported issue on your own. So we are proceeding to mark this ticket as closed. Kindly get back to us if you have further queries.
Regards,
Monisha