Topic: Datepicker documentation problem
Expected Behavior Samples should run without any errors.
Actual Behavior After pressing "Cancel" or "Escape", both display and scroll remain blocked.
Root Cause The documentation contains an error in UMD-based examples: the datepicker is initialized twice—once via the data-mdb-datepicker-init attribute, and a second time using the new Datepicker() constructor in JavaScript. This double initialization causes conflicts.
Important Note When initializing the datepicker programmatically using new Datepicker(...), you should not also include the inline initialization (data-mdb-datepicker-init) on the same element.
There are no examples that have double initialisation. Did you copy the first HTML and JS from the same example?
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Answered
- User: Pro
- Premium support: Yes
- Technology: MDB Standard
- MDB Version: MDB5 9.0.0
- Device: PC
- Browser: Chrome
- OS: W11
- Provided sample code: No
- Provided link: No