Event is already tracked exception thrown when CellSaved is triggered in WebAssembly
Hi,
Attachment: DataGridWasmError_e7dded43.zip
please see the attached Blazor WebAssembly sample project.
It contains a simple DataGrid in BatchEdit Mode that ends the edit mode and starts it right away in the cell saved event.
This sample works with Blazor Server (I copied it from https://www.syncfusion.com/forums/159578/blazor-grid-save-change-oncellsaved) but throws a exception when being used in a wasm app:
Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: Event 436 is already tracked
Error: Event 436 is already tracked
at e.add (https://localhost:5001/_framework/blazor.webassembly.js:1:42456)
at e.setListener (https://localhost:5001/_framework/blazor.webassembly.js:1:40690)
at e.applyAttribute (https://localhost:5001/_framework/blazor.webassembly.js:1:36857)
at e.insertElement (https://localhost:5001/_framework/blazor.webassembly.js:1:35691)
at e.insertFrame (https://localhost:5001/_framework/blazor.webassembly.js:1:34562)
at e.applyEdits (https://localhost:5001/_framework/blazor.webassembly.js:1:32948)
at e.updateComponent (https://localhost:5001/_framework/blazor.webassembly.js:1:32264)
at Object.t.renderBatch (https://localhost:5001/_framework/blazor.webassembly.js:1:12129)
at Object.window.Blazor._internal.renderBatch (https://localhost:5001/_framework/blazor.webassembly.js:1:61899)
at Object.w [as invokeJSFromDotNet] (https://localhost:5001/_framework/blazor.webassembly.js:1:64421)
Please let me know if I'm facing a bug here or where I screwed up ...
Maybe this is related to https://github.com/dotnet/aspnetcore/issues/27382
Thank you!
Stefan
Attachment: DataGridWasmError_e7dded43.zip
SIGN IN To post a reply.
2 Replies
VN
Vignesh Natarajan
Syncfusion Team
January 18, 2021 12:14 PM UTC
Hi Stefan,
Thanks for contacting Syncfusion support.
Query: “This sample works with Blazor Server (I copied it from https://www.syncfusion.com/forums/159578/blazor-grid-save-change-oncellsaved) but throws a exception when being used in a wasm app:.”
We have analyzed the reported query and we are also able to reproduce the reported issue at our end. We have confirmed it as a bug and logged the defect report “Exception error when trying to edit a cell in CellSaved event” 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 including the defect fix in our weekly release which is expected to be rolled out by end of February, 2021. We will update you once the release is rolled out.
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.
Till then we appreciate your patience.
Regards,
Vignesh Natarajan
VN
Vignesh Natarajan
Syncfusion Team
November 17, 2021 10:39 AM UTC
Hi Stefan,
The reported issue is related to Blazor Framework. The reported issue was fixed in the .Net 6.0 release. We have upgraded our Blazor component to .NET 6.0 RC in our 2021 Volume 3 release. So kindly ensure the reported issue by upgrading the application to the latest .NET 6.0 framework.
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,
Vignesh Natarajan
SIGN IN To post a reply.
- 2 Replies
- 2 Participants
-
ST Stefan
- Jan 15, 2021 07:24 PM UTC
- Nov 17, 2021 10:39 AM UTC