jQuery Forum

It appears that the problem was related to the onTabSelect callback
being called differently than in 1.5.0, the resolution to issue #2340.
Once I adjusted my callbacks, it looks like we're good.
That aside, is 1.5.2, offically out and ready for production use? It
doesn't show up on the ChangeLog page.

It's officially out, but I'm late writing the changelog and the blog announcement. Will follow tomorrow.

Ok, thanks.
Not to whine, but it looks like the change that tripped me up is from
1.5.1, not the latest, and I'd suggest that bigger noise needs to be
made about what amounts to an API change. It breaks all
implementations of the affected callbacks that uses the passed
arguments. Or did I miss where that got said? All I saw was an
innocuous-seeming note about "Consistent parameters for dispatched
events and callbacks", not something like "NOTE: This change requires
rework of all callback implementations that make use of the arguments
passed."
I'm not trying to be critical, just pointing out that API changes are
important news that people should have in their face. Or maybe I just
didn't read carefully enough first time around.
Thanks again,
s

Ok, thanks.
Not to whine, but it looks like the change that tripped me up is from
1.5.1, not the latest, and I'd suggest that bigger noise needs to be
made about what amounts to an API change. It breaks all
implementations of the affected callbacks that uses the passed
arguments. Or did I miss where that got said? All I saw was an
innocuous-seeming note about "Consistent parameters for dispatched
events and callbacks", not something like "NOTE: This change requires
rework of all callback implementations that make use of the arguments
passed."
I'm not trying to be critical, just pointing out that API changes are
important news that people should have in their face. Or maybe I just
didn't read carefully enough first time around.
Thanks again,
s

Hey,
I'm sincerely sorry for the problems introduced and I'm glad you were able to resolve them.
Indeed, we should have posted more clearly that specifically the tabs plugin now works like the others - it was a fix,
but people were using buggy format before of course.
That said, for all other plugins, the change shouldn't be noticeable.
Thanks,
Paul

Well, considering that the release post isn't done yet, you could add
that warning there. Bug or not, its an API change.
The current JDK has a lot of quirks that are today considered bugs,
but are impossible to fix due to compability. We should at least
notify people about API changes, even if they are considered bug
fixes.
Jörn

1) I think it should be stated more clearly than saying "The order of
parameters for callbacks is different than previous version." How
different? What are the parameters NOW? Studying the original ticket
hasn't 100% clarified it to me. I had to simply guess & try. Ok, now I
know, but...
2) It's very important to update the docs:
http://docs.jquery.com/UI/Tabs/tabs#options
so now it's not "show - Function(ui)", but rather "show -
Function(event,ui)"...
shall I post the doc update request somewhere separately?
kind regards,
-=snobo=-

<div dir="ltr">You're more than welcome to make both updates yourself, as both the changelog and the docs are a wiki. If you think it can be made more clear, then by all means, save others from having to go through what you did (guess and check) by making it more clear.
Otherwise, this is a fine place to make the request. Just let me know if you're not able to make the changes, and I will do so. Thanks.
- Richard

Fair enough! Stupid me, I completely forgot those pages are indeed
wiki... Updated successfully. Peace.