Summary: | Allow flatPickr to instantiate in any order | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
Component: | Templates | Assignee: | Martin Renvoize (ashimema) <martin.renvoize> |
Status: | RESOLVED WORKSFORME | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | ||
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: |
Bug 29450: Allow flatpickr to instantiate in any order
Bug 29450: Allow flatpickr to instantiate in any order |
Description
Martin Renvoize (ashimema)
2021-11-10 10:49:22 UTC
Created attachment 127507 [details] [review] Bug 29450: Allow flatpickr to instantiate in any order This patch updates the flatpickr wrapper code to allow for cases where the startdate/enddate pickers are pre-populated and thus the onClose event of the startdate pickr may be fired before the enddate flatpickr is instantiated.. which leads to an error. Created attachment 127621 [details] [review] Bug 29450: Allow flatpickr to instantiate in any order This patch updates the flatpickr wrapper code to allow for cases where the startdate/enddate pickers are pre-populated and thus the onClose event of the startdate pickr may be fired before the enddate flatpickr is instantiated.. which leads to an error. Removed a console.log statement I errantly left in.. otherwise, latest patch matches the previous upload. Can you remember where you observed this bug? Hi Martin, could you please add a test plan for this? (In reply to Katrin Fischer from comment #5) > Hi Martin, could you please add a test plan for this? Ping! |