3 ms·
Well, the wrapper has the same scrolling as the rest of the system and pages now.
by madeofpalk 9y ago
Well, the wrapper has the same scrolling as the rest of the system and pages now.
- coldtea 9y agoYes, but still implemented non-natively -- along with all kind of other bizarro differences that might be lurking.
- madeofpalk 9y agoNo, AFAIK the only reason that view had different scrolling was because it was an overflowing div which had the -webkit-overflow-scroll: touch property to give it any momentum. This page should demonstrate the same scrolling behaviour as AMP pages on iOS, without any 'custom' non-native scrolling https://s.codepen.io/joshhunt/debug/Xgeyoo https://s.codepen.io/joshhunt/debug/Xgeyoo
- Touche 9y agoI worked on a website that experienced this same problem several years ago. The designers were pretty insistent on a design that would require the crappy non-native scrolling, but luckily management stepped in and said no to them. Point being, UX should dictate design, not vice-versa. If you can't implement something the way you want without messing up something as important as scrolling then don't do it. The irony here is that the two most important features of the web are arguably URLs and scrollable pages. And AMP screwed up both of them.
- dbbk 9y agoIt is implemented natively. It's just a scrolling div versus a scrolling page. It's not a custom scrolling implementation.