I've seen similar posts when Apple announced that there won't be Flash on mobile Safari. And I agree with Chrome team decision to force passive on document level listeners.
Also, note that not many people complained about "blocking
video/audio autoplay on mobile browsers", because it's good for users.
BUT:
- Passive event listener detection is horrible and it baffles me that they start thinking about proper way only now.
- The announcement of this breaking change was quite silent. Chrome has so many influencers on social media, but almost no one shared/explained this change properly.
I'm not planning to stop working on PhotoSwipe, it's under active development. There will be a WordPress plugin soon (with paid pro version), so project will be partly monetized.
> Yeah, so we'd have to carry that exception over in every other piece of software we create that uses it
The license is MIT, you don't need to add anything else.
> The >300 open issues and what seems like tons of ignored pull-requests
Old version of PhotoSwipe was not developed me and I did not manage repository. Previous owners just passed development to me a few months ago https://twitter.com/PhotoSwipe/status/444134042787930113 and I started working on a new version.
I can assure you that all new issues and pull-requests will be managed appropriately.
Then you should make it more clear that you're just asking people not to make a Wordpress plugin from it and it's not part of the license. Right now that is not clear at all.
Mh, I saw the notice that it changed hands but somehow it didn't click that the issues were older... sorry about that then, and great to hear that it now has an active maintainer! Good luck with it!
It's in good hands now, no worries. Check his previous work and you will see, he is the master of touch! Royalslider pwned all sliders on day 1 now they have all copied it :)
I'm still trying to isolate it, but it seems that in gallery mode, when mfpClose is fired, it gets into a infinite loop, which causes the stack to overflow, and ultimately cause the page to crash.
I'm using jQuery 1.9.1 and Twitter Bootstrap. On a whim, I looked at your example code and noticed you were using Zepto. I tried switching to Zepto, and this fixed the issue with your gallery, and it closed properly. However, it breaks Bootstrap.
Did you only test with Zepto? There might be an issue in jQuery, where you're selecting elements incorrectly, thus spawning too many events.
It's really great that you draw a custom cover image for every single plugin.
Suggestion: make all navigation ajax-based and display the items right away (don't wait until all items are finished loading). This will make your site much-much more faster.
Also, note that not many people complained about "blocking video/audio autoplay on mobile browsers", because it's good for users.
BUT:
- Passive event listener detection is horrible and it baffles me that they start thinking about proper way only now.
- The announcement of this breaking change was quite silent. Chrome has so many influencers on social media, but almost no one shared/explained this change properly.