Hello,
I'm encountering an issue with the Radzen Scheduler component when navigating away from a page or component that uses it. The problem arises from the destroyScheduler function, which is automatically called during the disposal process. Here's the relevant snippet from the Radzen code (this code is called by radzen when navigating away from the scheduler):
destroyScheduler: function (ref) {
if (ref.resizeHandler) {
window.removeEventListener('resize', ref.resizeHandler);
delete ref.resizeHandler;
}
}
The issue occurs when destroyScheduler tries to access the ref parameter, which turns out to be null at the time of the function's execution. This results in a null reference error.
To provide more context:
Environment: .NET 8, Blazor with Radzen Scheduler
Issue: The ref is null when destroyScheduler is called during component disposal.
Steps to Reproduce: Navigate away from a component that uses the Radzen Scheduler, triggering the destroyScheduler function as part of the component's cleanup process.
It seems that this issue might be related to the timing of the component's disposal, where the ref is cleared or nullified before destroyScheduler can access it. Unfortunately, since this function is managed internally by the Radzen library, I'm unable to directly intervene or add null checks.
I’m wondering if this is a known issue or if there's a recommended workaround. If not, could you please consider adding a null check within the destroyScheduler function or provide guidance on how to manage this scenario?
Thank you for your help, and please let me know if you need any additional information to investigate further.