mobify / scooch

A mobile-first JavaScript-driven content and image carousel

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Does not work on iOS8

opened this issue · comments

On request of Jansepar,

Neither doesn't Scooch carousel work on iPhone 6 models. Tried on https://mobify.github.io/scooch/ with Chrome and Safari and the javascript gets stuck after viewing 2nd slide.

FYI below my old report.

  • Petro

"Hello,

Just purchased iPhone 6 Plus and tested carousel on my website and and with your examples. You can only slide to the next slide once and then the slider will get absolutely stuck - cannot slide anywhere after that. Tested on latest Safari and latest Google Chrome. Obviously it works on other devices just perfect.

If there is any way to pull out some javascript debug reports or anything out of the phone please let me know and I will gladly help you out.

Best regards,
Petro Mäntylä"

@Jeronefi I can confirm I can repro this behaviour using the iOS8 simulator:

image

Yep, can also repro. This may just be a problem with the documentation page as we haven't seen this issue in production yet.

I found the issue on my own website after launch of iPhone 6 with the older version of mobify carousel. Please slide the product image to the right (first make sure user agent is "phone" (iOS 8) to load mobile version of website) http://jerone.com/Mens/Long-Sleeves/Jacket-Scotch-&-Soda/

Looks like this happens only with full-width carousels and not in all environments.
Not quite sure what causes it.

Meanwhile there's a CSS workaround:
.m-scooch .m-item {
-webkit-transform: translate(0);
transform: translate(0);
}

This issue is also appearing on http://www.perfumania.com - the homepage slider can't slide past the second slide. It also isn't possible to click in any links in items past the first slide.

However, @Bielousov 's workaround solves both issues.

Same swiping issue on http://www.tommybahama.com - can click slide links though.

It looks like this is caused by a WebKit/iOS bug. I have filed an issue to hopefully get it resolved:

https://bugs.webkit.org/show_bug.cgi?id=137313

PR is now open with @Bielousov 's fix :)

Fixed as of 0.4.1