[Bug]: Too much bottom safe area when keyboard is visible

[aeharding]

Capacitor Version

➜  test-cap git:(master) ✗ npx cap doctor
💊   Capacitor Doctor  💊

Latest Dependencies:

  @capacitor/cli: 8.0.2
  @capacitor/core: 8.0.2
  @capacitor/android: 8.0.2
  @capacitor/ios: 8.0.2

Installed Dependencies:

  @capacitor/ios: not installed
  @capacitor/android: 8.0.2
  @capacitor/core: 8.0.2
  @capacitor/cli: 8.0.2

[success] Android looking great! 👌

Other API Details

➜  test-cap git:(master) ✗ npm --version
11.6.1
➜  test-cap git:(master) ✗ node --version
v24.11.0

Platforms Affected

• iOS
• Android
• Web

Current Behavior

With the latest capacitor v8.0.2, I noticed a strange issue where the bottom padding safe area will be ~ the size of the open keyboard, when the keyboard is open. This makes too much scrollable space appear in the webview.

This was originally spotted here: #8309 (comment)

❌ Incorrect behavior

IMG_0585.mp4

Expected Behavior

The bottom safe area should be 0 when the keyboard is open.

✅ Correct behavior

This issue does NOT happen with capacitor v8.0.1 or v8.0.0. In those versions it works as expected. Example:

IMG_0586.mp4

Project Reproduction

https://github.com/aeharding/cap-kb-blank-space

Additional Information

Device info: Google Pixel 7 with GrapheneOS. Android 16, webview v143.0.7499.146.0

[ionitron-bot]

This issue has been labeled as type: bug. This label is added to issues that that have been reproduced and are being tracked in our internal issue tracker.

[zarko-tg]

Try this: #8309 (comment)

[derWebdesigner]

@zarko-tg I did but for me, it didn't resolve the issue with the blank area behind the keyboard. I fully restarted and rebuilt the app. Is there anything else I need to do to make this work? Thank you very much in advance, since this bug is blocking me from deploying my next app update.

[zarko-tg]

@zarko-tg I did but for me, it didn't resolve the issue with the blank area behind the keyboard. I fully restarted and rebuilt the app. Is there anything else I need to do to make this work? Thank you very much in advance, since this bug is blocking me from deploying my next app update.

@derWebdesigner Which Android version do you see the problem? Some specific or on any version?

[derWebdesigner]

@zarko-tg I'm currently testing on an old Pixel 5 with Android 13 because I always want to be sure that it works for all devices. I will give it a try on a newer device and see if it changes over there but I still wouldn't be able to push it to the Play Store like that when only the latest Android version actually works.