[Bug]: Don't use calculated bottom inset if keyboard is visible

[insel-maz]

Capacitor Version

Capacitor 8.0.0

Other API Details

Platforms Affected

• iOS
• Android
• Web

Current Behavior

In version 8.0.0 SystemBars sets too much bottom padding for --safe-area-inset-bottom if the keyboard is visible.

Expected Behavior

Don't use the calculated bottom safe area inset if the keyboard is visible.

No bottom inset is needed (e. g. by the navigation bar) if the keyboard is visible.

Project Reproduction

capacitor/android/capacitor/src/main/java/com/getcapacitor/plugin/SystemBars.java

Line 167 in 1ef73a3

if (keyboardVisible) {

Additional Information

To fix this you could possibly add
safeAreaInsets = Insets.of(safeAreaInsets.left, safeAreaInsets.top, safeAreaInsets.right, 0);
to

capacitor/android/capacitor/src/main/java/com/getcapacitor/plugin/SystemBars.java

Line 167 in 1ef73a3

if (keyboardVisible) {

[1600822305]

[Bug]: SystemBars 为什么不能禁用??? 这和我项目中的键盘管理完全冲突 为什么不能禁用SystemBars ？？？

[ionitron-bot]

This issue needs more information before it can be addressed. In particular, the reporter needs to provide a minimal sample app that demonstrates the issue. If no sample app is provided within 15 days, the issue will be closed.
Please see the Contributing Guide for how to create a Sample App.
Thanks! Ionitron 💙

[eric-horodyski]

Hi @insel-maz,

Could you please attach a reproduction project that demonstrates the issue? Once we have that we can continue looking into this issue. Thanks!