MDN-Browser-Compatibility-Report-2020

library for that, it's not even large, it's a small JavaScript dependency. But it annoys me that you need these workarounds for doing simple stuff like that. The library was later confirmed to be ​ body-scroll-lock ​ , where bodyScroll L ock.js indeed does a bunch of work only for iOS. It has 269k npm downloads per week, which has to be considered a lot for a browser compat workaround.

Another developer had issues with scrolllntoView's "smooth" mode not being supported on Safari, also requiring the use of a JS workaround:

For "scroll to element", there's a "smooth" property [...] I think it's Safari that doesn't support [it]. We just added a polyfill for it, it's like 2 KB so it's not a big deal. Fortunately the build systems we have are pretty good at putting in a polyfill for what's not widely supported.

That same developer had also encountered issues on Firefox for iOS:

I've encountered a scroll issue in Firefox on iOS where there's something about the way that Safari is embedded in the iOS app that messes up scroll position sometimes. Because I think that Safari embedded is calculating internal values based on what it thinks is the viewport, and the app is actually wrapped in a smaller viewport because of the UI controls. That's my guess. So the scroll is a little bit off and I have to scroll with two fingers sometimes to get it to like jump out of the containing window.

The overscroll behavior of mobile browsers, sometimes called scroll bouncing" or elastic scroll, came up in multiple interviews:

Apple adds a little custom scroll at the end of pages. There's a special effect when you scroll to the end. That behavior was kind of disturbing us in one of our layouts that we had built for desktop and mobile. The scroll worked fine in Chrome on iOS and in Chrome and Safari on macOS. But in Safari for iOS [...] that scroll was interfering with our scroll. Sometimes, if you slide somewhere it would scroll and if you slide with a different angle or you slide very fast then the scroll wouldn't work directly. That was an issue where there was no solution or help on the internet, so we had to get creative and redesign some of the screen to get around this problem. I don't really know what that problem actually is, but most of the internet

Made with FlippingBook - professional solution for displaying marketing and sales documents online