[Bug]: Keyboard Plugin (with resize: "native"+resizeOnFullScreen: true) resizes view wrong

[timephy]

I had originally reported this bug here: ionic-team/capacitor#8095. Where it was falsely flagged as fixed, and then ignored. I reopened it as ionic-team/capacitor#8398, where I was told to report it here, so here it is.

Even though there are the old versions listed below, as you can see from the original issue, myself and other users still report this as being wrong in new versions.

---

Capacitor Version

💊 Capacitor Doctor 💊

Latest Dependencies:

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

Installed Dependencies:

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

[success] Android looking great! 👌

Other API Details

Platforms Affected

• iOS
• Android
• Web

Current Behavior

As first described in #8055 the Keyboard Plugin resizes the view wrong, this has changed recently when resizeOnFullScreen: true was changed to now treat the CSS safearea differently.

• A gray bar appears above the keyboard when it opens
• This gray bar seems to have the height of the top-safearea

I reproduced this in a new repo with these minimal steps:

• new svelte project
• installed capacitor + Keyboard plugin
• Keyboard options resize: "native" + resizeOnFullScreen: true

https://github.com/timephy/capacitor-issue-keyboard-android

Expected Behavior

All usable space should be used, no gray bar should appear!

Project Reproduction

https://github.com/timephy/capacitor-issue-keyboard-android

Additional Information

No response

[timephy]

One user reported using this community plugin fixes the problem:

Update on this, I installed this plugin : https://github.com/capacitor-community/safe-area

And it solved the issue. The small bar that was appearing when the keyboard layout would open is gone and it all works

However I believe that using a community plugin to fix a layout issue of this plugin is not in the interest of anyone.

[Emeseis]

I'm currently using version 8.0.1 instead of 8.0.2 as a workaround for this issue.

[timephy]

to my knowledge this happens no matter the version... from 7.x to 8.x