Okay, it turns out that I initially had noConflict() within a function
on .ready. This turns out to be a bad idea. Moving noConflict() inline,
below the library include (as below) works fine, and prevents the need
to load noConflict() multiple times.
~ ~ Dave
DaveG wrote:
Unfortunately this is on an internal environment, and I can't create an
external test file -- I don't have access to a server environment that
Ajax.update can call. I know, that's not much help, sorry :)
~ ~ Dave
Brandon Aaron wrote:
You shouldn't need to call noConflict more than once. Could you post
up an example?
--
Brandon Aaron
On 6/1/07, *DaveG* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I'm using prototype and jQ on the same page. I'm using noConflict().
<script src="/javascripts/jquery.js" type="text/javascript"></script>
<script type="text/javascript">
jQuery.noConflict();
</script>
Everything is happy. Until I use prototypes Ajax.Update(). The
response
is a bunch of javascript calls that include calls to prototype
routines,
like Element.show(). It seems that I need to include a call to
noConflict() at the start of the response, otherwise $ does not
point to
prototype.
Am I doing something fundamentally wrong here? Why do I need
subsequent
calls to noConflict()?
~ ~ Dave
