#12882: jQuery.noConflict() in admin breaks site specific code with jQuery
-------------------------------------------+--------------------------------
Reporter: krej...@i3.cz | Owner: jezdez
Status: assigned | Milestone: 1.2
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: jQuery admin
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Comment (by gabrielhurley):
Personally I'm a fan of namespacing Django's copy of jQuery.
That way developers who want to use the vanilla admin jQuery can do so
with a reliable, stable namespace for it while those who want their own
copy, own plugins, etc. can do so conflict-free. That strategy would work
well with the custom admin code I have written currently and seems like a
more maintainable mechanism in the long run.
Preventing loading of multiple jQuery instances via template blocks sounds
messy and likely to be broken by people hacking at the admin.
Rob Hudson's code definitely works but still feels brittle to me, like if
someone includes their script in the wrong place. I'd rather see something
more robust and separate.
That's my $0.02 for what it's worth.
--
Ticket URL: <http://code.djangoproject.com/ticket/12882#comment:24>
Django <http://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-upda...@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.
