Created attachment 466060 [details] Viewport unit test in Facebook IAB (small viewport) A common issue in In App Browsers (IABs) is that the viewport units is incorrectly sized. One issue seems to be caused by SFSafariViewController having setting the wrong sizes, this is reported here: https://bugs.webkit.org/show_bug.cgi?id=255708 In apps that use WKWebView we have to rely on the app developer setting the sizes correctly. The sizes can be set using `setMinimumViewportInset(_:maximumViewportInset:)`: https://developer.apple.com/documentation/webkit/wkwebview/3974127-setminimumviewportinset Unfortunately, many apps doesn't set the viewport insets for their IABs. One example is the Facebook app, where 100vh, 100svh, 100lvh and 100dvh are all updated to be the same height as the current viewport heigh. (They all act as 100dvh). As these apps have a large user base, these IABs are a major hurdle in adapting the new viewport units. It's necessary to build fallbacks for these IABs specifically. As 100vh is dynamically sized, they cause reflow when the user is changing scrolling directions. Could setting minimum and maximum viewport sizes be enforced?
Created attachment 466061 [details] Viewport unit test in Facebook IAB (large viewport)
Another example of an app where the viewport units end up wrong is the Firefox app: https://github.com/mozilla-mobile/firefox-ios/issues/11574 https://github.com/mozilla-mobile/firefox-ios/issues/8819
<rdar://problem/108536643>