SlideBack | A library to close an activity with swipe gestures | iOS library

Most likely the problem caused by 2 x id="clicker". Using unique ids for the buttons should solve to problem.

Next, since slideIndex declared globally it doesn't require plusDivs middle-ware.

I would also suggest to use clearer functions and variables names for the sake of better readability. Check these: slideDivs vs showDivs, step vs n, slides vs x, etc. It maybe doesn't sound like a big deal on the given example, but it is a good habit and will save you a lot of time when working on bigger projects.

There are also some minor optimizations possible, such as changing visibility in one loop and caching slides outside of sliding function to avoid selecting it again on every click. Check the snipped for suggested rewritten code.

Try this to increase in the moving position as below.

It looks like a bug in macOS 10.14.
There's actually a rdar for that: https://openradar.appspot.com/44135683

Meanwhile, there's a simple workaround.

I assume you are using NSPasteboard.writeItems, with a custom data class implementing NSPasteboardWriting.

I can definitely confirm this crashes on macOS 10.14.

Instead of NSPasteboardWriting, you should adopt NSCoding.

This means implementing:

• init?( coder: NSCoder )
• func encode( with coder: NSCoder )

Then, instead of using NSPasteboard.writeItems, use NSPasteboard.setPropertyList:

You should add the transition to your img.

Your also setting (in your js) the display to none. So you're basically removing the img before the transition can be seen. displayis also a non-transitionable attribute

Instead of display, try using opacity and setting it to either 0 or 1 (depending wether you want to show it or not)

then you could also add a transition for your opacity (maybe differently timed) and have a nice effect)