@fireattack This sounds more like a UX issue than a bug to me (and it's the first time this has been reported), but we're happy to improve it if we can, at least in the new viewer that we're going to build.

At the moment we are using PhotoSwipe 4 as a viewer, which is a standard JS component and not maintained by us:

• Could you verify if you have the same issues with their demo?
• If so, can you please search the code repository and developer forum for any related issues?

That would help us get a better understanding. Also, you should check if you have a special mouse driver installed, or use custom settings for your mouse or browser.

Thank you very much! 🤗

It looks like it has been reported by others there:

dimsemenov/PhotoSwipe#1743
dimsemenov/PhotoSwipe#1604

Since ver.4 is no longer updated, one has to fix the bug themselves, such as in this fork andi34/PhotoSwipe@bffac8f.

(I don't encounter the bug in ver. 5 demo they have.)

Thank you very much, that is very helpful! Would it be acceptable for you if we fix this at a later time, for example when working on our new media viewer?

We need to focus on merging the open pull requests next and should then take care of important security related issues like 2FA, leaving little time to work on UX issues in the short term. We also shouldn't use a fork without having time to test it well.

Yeah no problem, take your time.

So, does this feature wait for the new media viewer? I saw that a lot of small fixes and enhancements are opened for the media viewer and all of these should better be fixed in the new media viewer. I would be happy to work on this home-made viewer :)