Sayontan Sinha
Sayontan Sinha
My guess is that this piece of code is causing the issue: ``` .on( 'touchmove pointermove MSPointerMove', function( e ) { if( !wasTouched( e.originalEvent ) || options.quitOnImgClick ) return true;...
I have found a fix for this issue. The gist is that `wasTouched` is returning an incorrect value in Chrome, when you move the mouse over the lightbox, causing things...
I believe the issue occurs on Chrome running on touch-enabled Windows machines. Windows machines that are not touch-enabled seem immune to this.
I would like to add to this issue. This is my use case: I have a gallery/lightbox plugin written for WordPress, which pulls data from multiple sources and displays them...
Any plans of incorporating this?
Looks really nice - I will keep an eye out for v1.
For now I have a workaround - I am reinitializing the lightbox with the same selector, and that seems to be taking care of the issue.
Hi, I see that you have created this issue for yourself quite a few years back. Given the current state of support for Promise, is it possible to now remove...
I think you got hit with the latest WordPress update. It looks like Swipebox is not compatible with the version of jQuery included in this. This may be an issue...
OK, I had to dig around a bit and I think I found the problem. The issue is that Swipebox relies on $.selector, which was removed in jQuery 3.0 (https://api.jquery.com/selector/)....