That's actually the reason for the jQuery.noConflict() mechanism - so that if you do load multiple copies of jQuery, you have a way to make them all independent of each other. In your portal example, there might be code that depends on a particular version of jQuery, so it's possible for different widgets to use their own versions.
For your page, is there a reason you need to load two copies at all, given that they are the same version? That's just extra overhead. -Mike > From: Zach Leatherman > > Aforementioned co-worker here. > > I think we had mistakenly thought that the jQuery object was > getting re-used and jQuery.fn was being overwritten, which > looking back at the code obviously isn't the case. > > If this hasn't been a problem yet, maybe it isn't worth looking at. > Seems like this might cause unexpected behavior when using > jQuery in bookmarklets or in a portal style app where content > can come from multiple authors. > > --Zach --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
