bug: edge-to-edge does not resize the web view when keyboard opens

[luisbytes]

Plugin(s)

• Android Battery Optimization
• Android Dark Mode Support
• Android Edge-to-Edge Support
• Android Foreground Service
• App Review
• App Shortcuts
• App Update
• Asset Manager
• Audio Recorder
• Background Task
• Badge
• Bluetooth Low Energy
• Cloudinary
• Contacts
• Datetime Picker
• File Compressor
• File Opener
• File Picker
• Live Update
• Managed Configurations
• NFC
• Photo Editor
• Posthog
• Printer
• Screen Orientation
• Screenshot
• Speech Recognition
• Speech Synthesis
• Torch
• Zip

Version

7.1.0

Platform(s)

• Android
• iOS
• Web

Current behavior

With edge-to-edge mode enabled via the plugin, opening the keyboard does not trigger a resize of the WebView. As a result, content near the bottom cannot be scrolled into view, breaking the user experience for forms and interactive elements.

As shown in the video, inputs and the footer are hidden, and scrolling is not possible when the keyboard is open.

In Capacitor v6, with edge-to-edge disabled and without targeting API level 35, the WebView automatically resizes when the keyboard appears, allowing the user to scroll and access all content properly.

edge-to-edge-bug.mp4

Expected behavior

The plugin should allow the WebView to resize or adjust its layout when the keyboard is shown, maintaining accessibility for inputs and other bottom elements.

Reproduction

https://github.com/luisbytes/edge-to-edge

Steps to reproduce

1. Install and configure @capawesome/capacitor-android-edge-to-edge-support
2. Add an input near the bottom of the page.
3. Launch the app and focus the input.
4. Observe that the keyboard overlaps the content and the WebView does not resize.

Other information

No response

Capacitor doctor

Installed Dependencies:

@capacitor/cli: 7.2.0
@capacitor/android: 7.2.0
@capacitor/core: 7.2.0

Before submitting

• I have read and followed the bug report guidelines.
• I have attached links to possibly related issues and discussions.
• I understand that incomplete issues (e.g. without reproduction) are closed.

[robingenz]

Thank you for reporting that. Feel free to submit a PR.

[luisbytes]

@robingenz Reviewing this error in depth, it seems to be a capacitor v7 error.

[luisbytes]

@robingenz Given that this plugin was originally created as a workaround for an unexpected bug, do you think it would be appropriate to implement a proper fix for this issue now? Should I open a PR?

[robingenz]

Yes, please create a PR and I will take a look.