Looks like an error in coding. However, that might be in conjunction with something fairly unique with your page. But I think it's just an error. Here (in lightbox_plus.js):
Code:
_set_size : function(onResize)
{
var self = this;
if (self._open == -1) return;
self._page.update();
self._pos.update();
var spin = self._wrap.firstChild;
if (spin)
{
var top = (self._page.win.h - spin.height) / 2;
//if (self._wrap.style.position == 'absolute') top += self._pos.y;
spin.style.top = [top,'px'].join('');
spin.style.left = [(self._page.win.w - spin.width - 30) / 2,'px'].join('');
}
if (Browser.isWinIE)
{
self._wrap.style.width = [self._page.win.w,'px'].join('');
self._wrap.style.height = [self._page.win.h,'px'].join('');
self._wrap.style.top = [self._pos.y,'px'].join('');
}
if (onResize) self._set_photo_size();
},
The highlighted line is adding the page's vertical scroll to how far down the page the loading image should be if the overlay is absolutely positioned, which only happens in IE. However, since the loading image is relatively positioned inside the overly which also receives the added scroll as a vertical offset, this doubles the effect pushing the loading image much farther down the page as it is scrolled than seems reasonable. I just commented that line out as shown above in red, seemed to fix it.
As I say, I'm pretty sure this is an error in coding, perhaps at one time the loading image was separate from the overlay and absolutely positioned, then that line would make sense. But putting it in the overlay is a good move for efficiency in calculating things, if that's what happened, the author simply forgot about this adjustment from before and neglected to get rid of it. It would only show up in IE on pages that were scrolled vertically.
Bookmarks