Jeremy
in memoriam 1991-2020
Sure, move ahead and upgrade it. Fix the errors in the way from you not using jQuery v1.5 using custom functions or modifications to core library... But what happens when the library is updated to support jQuery 1.5... If you wrote custom functions, its like say "F*** off, developers!" and require a rewrite of tooltip functionality (again). And what if they introduce the upgrade in a different way, then you'll still be royally screwed. To them I say, using libraries means that you must wait for components to update, then, and only then, can you possibly THINK about moving to the newest versions.True to form, post 4 has been edited. I won't even bother to comment this time, make up your own minds.
View attachment 10286
Does anyone here think that moving now to a major new version of jQuery and potentially introducing a swathe of new bugs from undocumented backward compatibility issues (especially when we at release candidate stage and are concentrating on cleaning up bugs) is a good idea?