Bug 301857 – iOS 26 WebView Viewport Shrinks After Keyboard Dismiss in Cordova iOS 7.1.1 - Xcode 26

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: Layout and Rendering

Problem
- On iOS 26, the infamous "keyboards shrinks webview height" problem occured again.

What is expected to happen?
- The viewport height should NOT shrink on the iOS 26 when virtual keyboard shown and dissmissed. (focusing on input elements etc.)

What does actually happen?
- The viewport is 812px before the keyboard shown, 744px after keyboard dismissed.
- The viewport height does not recalculate.
- Breaks "position: fixed" elements and overscrolls the body.

Same issue a few years ago:
- https://github.com/apache/cordova-ios/issues/417

Reproduce the problem
- Create a new cordova project with Cordova.
- Add iOS platform.
- Change "www" folder and "config.xml" file with the provided. (www.zip & config.xml.zip)
(www folder contains simple html which shows 100vw x 100vh element and input)
(config.xml for "disableOverscroll" property)
- DO NOT use cordova to build.
- Open XCode and select the iOS platform folder.
- Build with XCode and run the app on device.
- Notice the centered input element. Tap/click on it.
- Check the viewport_height BEFORE focusing input: 812px (keyboard-dissmiss-before.png)
- Check the viewport_height AFTER focusing input: 744px (keyboard-dissmiss-after.png)
- Notice the difference between the two values. (812px -> 744px with no way to re-calculate it)

Environment, Platform, Device
- iOS 26.0.1
- Cordova iOS 7.1.1
- iPhone 12 Mini

Version information
- Built in Xcode 26

Created attachment 477259 [details]
ZIP file contains simple HTML project and also screenshots of the console that shows values

[Simon Fraser (smfr)]

Please test in iOS 26.1 when available and let us know if it's fixed.

[Radar WebKit Bug Importer]

<rdar://problem/163965981>

Created attachment 477283 [details]
iOS 26.1 Fixed - the proof image

(In reply to Simon Fraser (smfr) from comment #2)
> Please test in iOS 26.1 when available and let us know if it's fixed.

Yes!
I tried it on Public Beta 26.1 RC and can confirm that it fixed. (They probably fixed it before my bug report)
Then, I realised that the 26.1 itself got released last night and just tried on it and yes, also confirm that 26.1 fixed the issue.
I hope it stays that way.

Thanks for you for reply, the team for the fix.

[Simon Fraser (smfr)]

Thank you for testing.