Is there a way to resolve this conflict within prototype? My portal
uses jQuery and I'm the only developer with a preference of
prototype.js. I've tried the jQuery.noConflict() with no luck. I
don't want to abandon my prototype.js skillset for jQuery but it's
looking like I'm the one that need
ll dependent
> scripts first, then load prototype and all of its dependent scripts
> subsequent to that and get away with it? Give it a shot and let us
> know...
>
> On Feb 6, 2:22 pm, david wrote:
>
>
>
> > Hi dizzyjay,
>
> > the noConflict function works great
Thanks- this looks like what I'll need to do. Hopefully the portal
owner will be accepting of the change. Too bad prototype doesn't have
the same conflict workaround (it would be much easier for me to
change).
cheers,
\\dj
On Feb 6, 11:22 am, david wrote:
> Hi dizzyjay,
>
I have a script that facilitates 3 Ajax requests. One of the requests
takes a while for the server to render because it dynamically creates
a series of .png files in a hidden div which is toggled to display
inline. Because the server takes long to render, the users are
prompted (by IE) to turn off
