Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #255
Description of Changes
There were two main issues with the datepicker functionality:
Datepicker Executing on Inactive Inputs: In inline admin forms, the datepicker was being executed on inputs that were not yet active (those containing
__prefix__
in their IDs).Reactivating Datepicker After Adding or Removing Formsets: In forms using formsets, when a new form was added or an existing one was removed, the datepicker was not reinitialized for the new inputs.
Also, changes were made to the position and look of the calendar icon and button text to match Django's style.
Testing
I tested these changes in Django versions 4.2 and 5.1. Below are screenshots showing the updated datepicker in both tabular and stacked inline forms.
Tabular Inline
Stacked Inline