Topic: Setting autoPlayThumbs="FALSE" does not work? [SOLVED]

I am using the Drupal module Juicebox HTML5 Responsive Image Galleries (7.x-2.0-beta5)  together with Juicebox Pro 1.3.3. I try to set the pro setting autoPlayThumbs like this: autoPlayThumbs="FALSE". But I can't see any change - the thumbnails still autoplay. At the Drupal module support page they say that it can't be a an issue in the module. Is this a bug in Juicebox itself or do I misunderstand something?

And yes, all other pro settings seem to work. My pro settings look like these:

themeUrl="/sites/all/libraries/juicebox/classic/theme.css"
showOverlayOnLoad="FALSE"
showAutoPlayButton="TRUE"
showAutoPlayStatus="FALSE"
enableAutoPlay="TRUE"
autoPlayOnLoad="TRUE"
autoPlayThumbs="FALSE"
enableLooping="TRUE"
imageTransitionType="CROSS_FADE"
displayTime="5"
imageTransitionTime="1"
imageHAlign="CENTER"
imageVAlign="TOP"
buttonBarPosition="OVERLAY_IMAGE"
imageNavPosition="IMAGE"
captionPosition="OVERLAY_IMAGE"
thumbsPosition="BOTTOM"
thumbsHAlign="CENTER"
thumbsVAlign="TOP"
maxThumbColumns="3"
maxThumbRows="1"
thumbNavPosition="CENTER"
splashButtonText="Visa galleri"
splashShowImageCount="FALSE"
shareFacebook="FALSE"
shareTwitter="FALSE"
languageList="Visa tumnagelbilder|Dölj tumnagelbilder|Expandera galleri|Stäng galleri|Öppna bild i nytt fönster|Nästa bild|Föregående bild|Spela ljud|Pausa ljud|Visa information|Dölj information|Starta automatisk uppspelning|Stoppa automatisk uppspelning|Automatisk uppspelning PÅ|Automatisk uppspelning AV|Tillbaka|Köp denna bild|Dela på Facebook|Dela på Twitter|Dela på Google+|Dela på Pinterest|Dela på Tumblr|av"

Re: Setting autoPlayThumbs="FALSE" does not work? [SOLVED]

Thank you for reporting this bug.
I have logged a bug report with the developers.
Unfortunately, I do not think there is a workaround at the moment to achieve the same result that setting autoPlayThumbs="FALSE" would give.
However, the bug should hopefully be fixed in the next version of Juicebox-Pro.

Re: Setting autoPlayThumbs="FALSE" does not work? [SOLVED]

This bug has now been fixed in v1.4.0. Please see this blog entry for details.