Unplanned
Last Updated: 10 Mar 2025 10:48 by ADMIN
Alexander
Created on: 06 Jun 2023 16:13
Category: DateTimePicker
Type: Bug Report
4
DateTimePicker with AdaptiveMode.Auto occasionally throws when zooming in or out

If you are zooming a page containing a DateTimePicker with "AdaptiveMode" set to "AdaptiveMode.Auto", the application crashes occasionally with the error:

Microsoft.JSInterop.JSException: Cannot read properties of null (reading 'addEventListener')
TypeError: Cannot read properties of null (reading 'addEventListener')

The more adaptive DateTimePicker instances the page contains, the more likely the error is to occur.

 

 

6 comments
ADMIN
Nadezhda Tacheva
Posted on: 10 Mar 2025 10:48

Hi Mike,

The behavior you are describing seems to be related to the same issue.

The fix for this item is not yet scheduled but I increased its priority in the backlog based on the increased votes. I encourage you to follow the item, so you can get status updates. Thus, you will get an email notification when we change the status of the issue.

Regards,
Nadezhda Tacheva
Progress Telerik

Enjoyed our products? Share your experience on G2 and receive a $25 Amazon gift card for a limited time!

Mike
Posted on: 03 Mar 2025 20:10

I seem to have a similar problem and not sure if it is related or not, so I'm putting a comment here. Let me know if this should be its own item.  In my case, this issue will occur when I resize the window too quickly.  It looks like the error is originating from the following javascript function:

bindPickerEvents() {
                    this.pickerElement.addEventListener("keydown", this.onPopupKeyDown, !0)

pickerElement appears to be null under certain circumstances. 

It appears to happen when I have multiple DatePickers within components and the AdaptiveMode is set to Auto.

Is there any update regarding fixing this issue?

ADMIN
Hristian Stefanov
Posted on: 12 Jul 2024 07:05

Hi Alexander,

I can confirm that the item is still unplanned. Until August at least, our backlog/short-term planning is filled with items of more priority and demand.

Regards,
Hristian Stefanov
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources!
Alexander
Posted on: 05 Jul 2024 10:52

Hello all,

 

one year has passed since this was created – any updates? When can we expect a fix?

 

Thank you for you reply.

ADMIN
Hristian Stefanov
Posted on: 26 Sep 2023 13:14

Hi Alexander,

Thank you for sharing additional cases in which the problem appears.

I confirm that the status of this item is still marked as "Unplanned." This means that there isn't a specific timeline assigned to it yet.

Nevertheless, as we transfer the task to our short-term backlog, the status will be updated to "Planned" along with an associated release number. This release number will indicate the upcoming release in which the fix will be implemented.

To stay updated on the progress of this item, I encourage you to subscribe to it. By doing so, you will receive email notifications for any status updates.

Regards,
Hristian Stefanov
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources!
Alexander
Posted on: 21 Sep 2023 06:37

Any update on this? We also found that zooming is not the only way to trigger this exception – merely resizing the window can also cause this:

The dialog that can be seen includes a few `TelerikDateTimePicker` components. When shrinking and expanding the browser window again, the application crashes with the same error that occurs sometimes when zooming.