Yes. And that's one way of dealing with the problem. Another would probably be to use migrate (addition highlighted):
Code:
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
<script src="http://code.jquery.com/jquery-migrate-1.0.0.js" type="text/javascript"></script>
It brings back functionalities to jQuery that have been dropped. A benefit with this approach is that if you use a browser with console logging, it will log which dropped features are being used. That way one can update the code that uses the dropped feature(s).
I say only 'probably' though because if the main reason is something beside dropped functionality, migrate might not fix the problem and any logging it might do could be misleading.
But again, clearly the script works with jQuery 1.9, so there must be some other problem. Now of course jq 1.9 is involved, but there must be something else as well on your page, otherwise ajfmrf's demo wouldn't work.
Sometimes a newer version of jQuery uses a stricter syntax than an earlier version. I've seen this happen before. Where an earlier version might ignore excessive quotes used in a selector, a later version will not, resulting in that selector not working as expected.
Again though, it has to be more than just that, since ajfmrf's demo works. It does work in both those browsers (IE and Firefox).
Here's the link again if you missed it:
http://www.web-user.info/vic/accordion/1.html
Nice work Bud.
Bookmarks