You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After starting the execution just open the calendar and wait for the timeout which calls the destroy after 5 seconds. The result is that the calendar remains open and each iteration leads to an error
Problem not occurs in 1.12.1.
Thank you in advance.
The text was updated successfully, but these errors were encountered:
@fnagel When comparing the two versions, we found that on version 1.12.1, the widget will only hide after being destroyed once the user clicks on another part of their screen. Would you prefer to have the widget disappear when destroyed or only hide the date picker once the user clicks away?
Note that the description here is not fully correct - in 1.12.1, the datepicker UI was not hidden on destroy either! It was just hidden after the first mousedown. If you just hovered over the datepicker or clicked on any of its elements, you'd get lots of console errors even in 1.12.1.
But yes, the 1.13.2-1.13.3 behavior is worse since there's no way to get rid of the widget from the user perspective, irrespective of the underlying errors.
After upgrading from version 1.12.1 to 1.13.2 the method datepicker( "destroy" ) do not close and destroy the calendar ui.
I have prepared an example at the link below.
https://jsfiddle.net/7kdwvgp8/
After starting the execution just open the calendar and wait for the timeout which calls the destroy after 5 seconds. The result is that the calendar remains open and each iteration leads to an error
Problem not occurs in 1.12.1.
Thank you in advance.
The text was updated successfully, but these errors were encountered: