I'm sorry that we do not currently have a reduced repro case, but we thought you might want to know that CSS snap points are broken in Safari in current iOS 10.3 beta 2.
More details here https://github.com/ampproject/amphtml/issues/7670
The bug has a few repro URLs.
This affects a large subset of AMP pages (likely a few 100 million). We will revert to non-snap points behavior, but this will represent a signficiant regression in UX.
Updated to reflect that this is still broken in beta 6.
Here is the URL to reproduce what Malte described below
Working slides on IOS 10.2- https://www.youtube.com/watch?v=DkI5U9Sqlm4
Broken slides on IOS 10.3 beta (test on beta 7) - https://www.youtube.com/watch?v=r6jZILTvt5E
The syntax changed to match the latest spec:
@smfr - is there a date when this would come out of beta?
Ok - Now i got clarity into what the real issue is. This is because of snap points
This is not because of the syntax change , the old syntax still works fine on the beta.
The only issue is when we set scrollLeft on the container via JS, the browser resets it back to the last known snap position set via css snapping. the right behavior would be to snap to the closest snap point.
Here is my JS BIN
And the video demonstrating what is wrong.
@Wenson Hsieh, any updates on this? will this be fixed before the beta launches?
(In reply to Sriram Krishnan from comment #6)
> @Wenson Hsieh, any updates on this? will this be fixed before the beta
Unfortunately, I cannot comment on what changes will make it into future releases. However, I will make it a priority to investigate and fix this problem on ToT.
Any update on when this would be fixed. As Malte mentioned it affects a few 100 million (AMP) pages, it would be great to get this fixed at the earliest possible!
Thanks. Unfortunately, we cannot discuss release dates, but understand that this is a very important bug for AMP.
Created attachment 306322 [details]
Reduced test case adapted from <http://output.jsbin.com/fiwiqo>
I believe this was solved in https://bugs.webkit.org/show_bug.cgi?id=170560 - can some one correct me if i am wrong?