#16776: jQuery.noConflict(false) in jquery.init.js leaks the admin jQuery into
the
global namespace
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Milestone: 1.4 | Component: contrib.admin
Version: SVN | Severity: Normal
Resolution: | Keywords: jQuery admin
Triage Stage: Design | Has patch: 0
decision needed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 1
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by jezdez):
* stage: Unreviewed => Design decision needed
Comment:
The problem of using `jQuery.noConflict(true)` (and which is what was
changed to `jQuery.noConflict()` in r16415) is that it removes //any//
jQuery from the global namespace, even if it's the jQuery shipped with a
3rd party app.
So, with the current state of `jQuery.noConflict()` you should be able to
put another jQuery **after** Django's jQuery and it should just work
because it's overwriting the `jQuery` object in the global namespace.
Unless I misunderstand something the `django.jQuery` object should then
still be the same Django-jQuery.
--
Ticket URL: <https://code.djangoproject.com/ticket/16776#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
