starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-02-04 05:35:44 +00:00
Code Issues 1.3k Packages Projects Releases 22 Wiki Activity

RadzenDataGrid with virtualization & LoadData causes DOMException #1964

New Issue
Closed
opened 2026-01-29 18:16:11 +00:00 by claunia · 1 comment
claunia commented 2026-01-29 18:16:11 +00:00
Owner
Copy Link

Originally created by @Wortex17 on GitHub (Jan 28, 2026).

Describe the bug
When the data of a RadzenDataGrid is initialized with null and virtualization is enabled, a DOMException is thrown in Firefox and Chome.

To Reproduce
Steps to reproduce the behavior:

  1. Go to official playground sample for DataGrid virtualization
  2. Enable Debug Console of the Browser
  3. Click on 'Run' and wait for the sandbox to load
  4. See "Uncaught DOMException: The supplied node is incorrect or has an incorrect ancestor for this operation."

Expected behavior
No error should be thrown as to not clog the dev console or obfuscate real errors.

Screenshots
Firefox
Image
Chrome
Image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Firefox, Chrome

Additional context
The issue can be "circumvented" by initializing the data property of the datagrid to an actual list, but then the LoadData callback will not be used anymore.

This has been happening since at least 8.3.3, since now i thought it wa smy setup that was wrong.

I am unsure if this applys to non-WASM as well

Originally created by @Wortex17 on GitHub (Jan 28, 2026). **Describe the bug** When the data of a RadzenDataGrid is initialized with null and virtualization is enabled, a DOMException is thrown in Firefox and Chome. **To Reproduce** Steps to reproduce the behavior: 1. Go to [official playground sample for DataGrid virtualization](https://blazor.radzen.com/playground?example=DataGridVirtualizationLoadData&theme=material3) 2. Enable Debug Console of the Browser 3. Click on 'Run' and wait for the sandbox to load 4. See "Uncaught DOMException: The supplied node is incorrect or has an incorrect ancestor for this operation." **Expected behavior** No error should be thrown as to not clog the dev console or obfuscate real errors. **Screenshots** Firefox <img width="704" height="393" alt="Image" src="https://github.com/user-attachments/assets/1a8e24f9-07c8-4428-ae03-6747d1adbfc1" /> Chrome <img width="938" height="113" alt="Image" src="https://github.com/user-attachments/assets/0e6e7d38-8fa4-4244-9a74-a43c9314f22c" /> **Desktop (please complete the following information):** - OS: Windows 10 - Browser Firefox, Chrome **Additional context** The issue can be "circumvented" by initializing the data property of the datagrid to an actual list, but then the LoadData callback will not be used anymore. This has been happening since at least 8.3.3, since now i thought it wa smy setup that was wrong. I am unsure if this applys to non-WASM as well
claunia commented 2026-01-29 18:16:12 +00:00
Author
Owner
Copy Link

@enchev commented on GitHub (Jan 29, 2026):

Unfortunately, this error is beyond our control and may occur in various scenarios, even though this particular issue has already been closed: https://github.com/dotnet/aspnetcore/issues/52126

UPDATE: You can remove await Task.Yield(); to avoid this.

@enchev commented on GitHub (Jan 29, 2026): Unfortunately, this error is beyond our control and may occur in various scenarios, even though this particular issue has already been closed: https://github.com/dotnet/aspnetcore/issues/52126 UPDATE: You can remove `await Task.Yield();` to avoid this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#1964
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?