I've just recently started to receive the following error. "TypeError: Failed to execute 'contains' on 'Node': parameter 1 is not of type 'Node'."
This error happens after the RadzenAutoComplete has been used and then the screen is maximized using the "Restore Down/Maximize button in MS Edge.
At the time of the error there is no popup open. There was a popup (RadzenAutoComplete) open at some point before this error but it has since been closed. So, there is a "div" in the body with class "rz-autocomplete-panel rz-popup" and style "display: none; transform: none; box-sizing: border-box; max-height: 200px; width: 286.797px; z-index: 2000; left: 51.4531px; top: 260.562px;"
When I started to notice the error I did upgrade the Radzen.Blazor NuGet package. I also noticed a new version was available this morning so I tried that one too. I'm currently at version 5.6.9 so this has been happening at least since version 5.6.7.
I am able to continue my debug session by clicking on "Continue" three consecutive times but that doesn't exactly seem like a "solution" to the underlying issue.
I have. After clicking through the error using the Continue button in Visual Studio (2022) and regaining control of the app I have tried both your suggestion of CTRL-F5 and also left click and hold on the MS Edge refresh button and selecting "Empty cache and hard refresh". Same result If I go back and perform the same actions that caused the initial error.
Using the second demo example ( Get and Set the value of AutoComplete using Value and Change event).
Type "f", select an item from the list using the arrow keys and the enter key. After making that selection use the "Restore down" and "Maximize" button. If you have the browser console open to "console" you can watch the errors as they happen.
Try it using "fr" so that there is only one selection and continue from there. I was able to consistently reproduce the error if there was just that one item to select from the dropdown.
FYI: I did try using a screen recorder but I got both monitors and it was barely visible because of the size. Sorry.