3 ms·
The tapping top of screen hasn't been fixed, as it likely is hard to do. As for other work on scrolling: Person contracted to fix some webkit issues: http://f
by kyrra 9y ago
The tapping top of screen hasn't been fixed, as it likely is hard to do.
As for other work on scrolling:
Person contracted to fix some webkit issues: http://frederic-wang.fr/amp-and-igalia-working-together-to-improve-the-web-platform.html http://frederic-wang.fr/amp-and-igalia-working-together-to-i...
HN discussion made some news about scrolling changes made due to AMP's bug reports: https://www.macrumors.com/2017/05/22/scrolling-changes-coming-to-mobile-safari/ https://www.macrumors.com/2017/05/22/scrolling-changes-comin...
- ComputerGuru 9y agoAMP scrolling is still broken. I don’t see why it needs to touch the scroll behavior at all. Plain html is both fast and scrolls naturally. It doesn’t break mobile safari. I don’t get why Google needed to render AMP on such a way that they need to try hard to emulate native scroll behavior (still getting it wrong, previously it was too fast and now it’s a smidge too slow) instead of just using the native behavior.
- epistasis 9y ago>The tapping top of screen hasn't been fixed, as it likely is hard to do. Plain HTML+CSS is hard to do? Google has gone to an exceptional effort to make things not work like they do by default. That it's even more effort to now get basic UX back shows just how misguided the entire team is.