So following on from my comment above, I'm hoping I have the answer you're after. It's not precisely the same as your situation, but the errors were exactly the same, and the issues involved were very similar.
In my situation, we had an
<apex:tabPanel> on a custom Account page with different
<apex:tab>s corresponding to different bits of Account information.
In each of these, we were using
<apex:composition> to pull in different visualforce pages laying out this information.
In one of these pages pulled in using
<apex:composition> I was importing jQuery and a few other bits and bobs to get some enhanced table functionality. Now as the
<apex:tabPanel> tag had the attribute
switchType="server" set, I was surprised to find my static jQuery resource was being pulled into the page's source when I wasn't viewing the jQuery tab. This was of course combined with the fact that none of the tabs functioned correctly, and I was getting exactly the same error messages as you.
So long story short - it didn't matter which tab I was viewing, something about the
Of course, my first thought was "OK, easy fix, slap
jQuery.noConflict() into a
<script> tag inside the page where I import jQuery". No such luck. While using the
<apex:tabPanel> does pull any js imports from non-active tabs in, it doesn't pull any
<script> tags an.
So I chucked the same thing into the page containing the
<apex:tabPanel> instead (with a check that the jQuery var had been attached to the window). And bam: the errors were gone :)
So to bring it on home/TL;DR
On the page containing the
<apex:tabPanel> (not necessarily the page that actually imports jQuery, unless it can be accessed/is used in other contexts where there may be a conflict on the $ alias!) chuck the following in. This checks to see if jQuery has been loaded onto the page. If it has, it calls jQuery.noConflict(). The major side-effect of this, for those unfamiliar with noConflict, is that you now cannot use the $ alias for jQuery, and instead need to use the full jQuery namespace var.