-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In Google Chrome (73.0.3683.75, 64-Bit): Picker closes immediately after showing #155
Comments
I have encountered the same error on Chrome Version 73.0.3683.75 (64-bit). I will check and fix it. Thank you for reporting. |
for quick fix i just tried this |
thank you! |
showing error in browser console for me DateTimePicker.min.js:64 Uncaught ReferenceError: oDTP is not defined Thanks |
In which example you are encountering this issue? Please mention file name. |
same bug here, Version 73.0.3683.75 (Official Build) (64-bit) |
work for me |
1. Fix for Google Chrome (73.0.3683.75, 64-Bit): Issue #155 by @shareefhiasat 2. Adds korian language i18n files 3. Other maintenance tasks
Fix by @shareefhiasat is working for me. Please check by using latest library javascript files. |
@nehakadam Can you publish a new version that includes the fix? |
@nehakadam Thank you, 0.1.39 fixed it for me. |
Still same issue here with Version 73.0.3683.103 (Official Build) (64-bit), tested with 0.1.38 and 0.1.39. I also tried the temporary fix above with no luck. |
Okay, my issue was specifically related to the fact that the DateTimePicker modal dialog DIV element was within another jQuery modal dialog's DIV element. I moved it outside and this problem went away. There is still a conflict that I think should be corrected - but I was also unable to track it down in a short time, and element outside of the other resolved the issue. |
Hello!
In Google Chrome (73.0.3683.75, 64-Bit):
The DateTimePicker closes immediately after showing.
You can try the demo 'Basic Usage of DateTimePicker with '.
Who can confirm this?
Kind regards,
Gerald
The text was updated successfully, but these errors were encountered: