https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29450
Bug ID: 29450
Summary: Allow flatPickr to instantiate in any order
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Templates
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
Currently, we automatically instantiate a flatPickr instance for any input
fields that have the flatpickr class.
This instantiation is handling within a loop and works well in most cases.
However, if the the input is paired so we have a start/end date pair and the
start date is pre-populated with the template you are faced with javascript
errors.
This is because the pre-populated value triggers our onClose function that
resides in the instantiation settings. The onClose looks for the associated
'end' input and grabs the flatpickr instance to set the minDate property.. but
as we've not yet hit the end input field the flatpicker instance for that field
doesn't yet exist.
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
