Closed (fixed)
Project:
Lightbox2
Version:
6.x-1.9
Component:
Javascript
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Jan 2009 at 22:51 UTC
Updated:
7 Oct 2010 at 17:40 UTC
Hi Stella,
Maybe I don't understand this correctly, but I cannot seem to get the 'simultaneous' setting to work for the resize animation. My expectation for this setting would be that height and width are resized simultaneously. When the Lightbox opens, first the width expands, then the height. In fact, during opening, I see no difference between the settings "Width then height" and "Simultaneous". Is this a bug, or am I misunderstanding something?
Comments
Comment #1
fletchgqc commentedSame problem with 6.x-1.9. I'm not using lightbox lite, by the way.
Comment #2
mimhakkuh commentedSame issue over here (no lite modus used), subscribing.
Comment #3
digitalfrontiersmediachange line 554 in lightbox.js from
to
Comment #4
stella commentedThe lightbox is working correctly, it's just that the caption area is rendered after the image, which gives the effect of the height increasing last. If you don't have a caption for an image (or any icons appearing below the image), then you'll see that it is working as expected. You could try adjusting the time for the caption slide down under the 'animation settings' if you wish to try and make the caption appearance less noticeable.
Comment #5
digitalfrontiersmediaStella,
I disagree with your statement that the lightbox is working correctly. It obviously was not in my case. Your explanation doesn't hold water since my lightbox was switching between an image that was about 500px tall to an image that was only about 120px tall. The caption was a mere 40px or so. It was quite obviously doing the animations separately and being forked by the conditional I noted before since after making the change in the code, it worked correctly (without changing captions or any other content)--it just behaved differently--as it should.
Given that you feel the code is working correctly, I suspect this is due to the way the javascript engines in different browsers are interpreting the code (and maybe which version of the module is being used).
I experienced the issue using Mac Safari 5.0.1 and 6.x-1.9 (changing issue information to match).
If desired, I could attach videos showing the difference in the behaviours before and after the above code change.
Comment #6
stella commentedWell using 6.x-1.10 and Mac Safari 5.0.1, I still can't reproduce the issue. Perhaps you can provide a link to your site?
Comment #7
digitalfrontiersmediahmmm...weird. I upgraded to 6.x-1.10 and it does indeed work as advertised without the mod. I must have accidentally borked your code at some point and not noticed.