You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CDN links point to old versions, at least for django-bootstrap-datepicker-plus which still points to version 5.0.2 even in v5.0.5 of the code itself. Is this intentional?
I found out because I got this warning in the console. "[Deprecation] Listener added for a 'DOMNodeInserted' mutation event..." coming from datepicker-widget.js. Looking at the local Javascript code shipped with 5.0.5, I see that it already uses the MutationObserver API, as mentioned in #115.
But {{ form.media }} still renders links to 5.0.2 code from the CDN that uses DOMNodeInserted.
The text was updated successfully, but these errors were encountered:
Sorry, but I'm confused. The code in the repository here on github points to 5.0.6?
But in my local installation, using command pip install django-bootstrap-datepicker-plus gives me a file in my environment "/site-packages/bootstrap_datepicker_plus/static/bootstrap_datepicker_plus/js/datepicker-widget.js" that contains code with DOMNodeInserted?
I also uninstalled the package, did pip cache purge, and reinstalled:
The CDN links point to old versions, at least for
django-bootstrap-datepicker-plus
which still points to version5.0.2
even inv5.0.5
of the code itself. Is this intentional?I found out because I got this warning in the console. "[Deprecation] Listener added for a 'DOMNodeInserted' mutation event..." coming from
datepicker-widget.js
. Looking at the local Javascript code shipped with5.0.5
, I see that it already uses theMutationObserver
API, as mentioned in #115.But
{{ form.media }}
still renders links to5.0.2
code from the CDN that usesDOMNodeInserted
.The text was updated successfully, but these errors were encountered: