Unless something has changed, Wmflabs policy requires that we only use
Wikimedia CDNs. Other CDNs use cookies to track a user's actions, which
violates the privacy policy.
Magog
On Wed, Jun 24, 2020 at 3:41 PM Roy Smith <roy(a)panix.com> wrote:
OK, I got this solved. Turns out I had a bug in my
django template
inheritance, which was causing selectize to load before jquery.
In an odd sort of way, the issue with the Content Security Policy
violations turned out to be important. I knew it was a problem, but blew
off doing anything about it because it was just warnings. It turns out I
was getting a javascript console error about $ not being defined, but it
was lost in all the noise from all the CSP warnings. Once I cleared those
up, all that was left was the $ not defined error and it became obvious
what was going on.
I think there's like some basic software engineering lesson in there :-)
On Jun 22, 2020, at 10:01 PM, Roy Smith <roy(a)panix.com> wrote:
I'm mostly a python guy, who only dabbles in javascript when I can't avoid
it :-)
I've got a django-based tool (
https://tools.wmflabs.org/spi-tools-dev/spi/)
which uses selectize.js. For simple cases, everything works fine. But, if
I click on the drop-down, delete the contents, type in a new value, and
submit the form (Sock Info button), the submitted form data has case_name
blank.
Is there anybody here who is familiar with javascript and/or selectize.js
who would be willing to point me in the right direction?
_______________________________________________
Wikimedia Cloud Services mailing list
Cloud(a)lists.wikimedia.org (formerly labs-l(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud