Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CoordinatorLayout Height Not Restored After Keyboard Closes on App Switch in Low-End Devices (Only on Incognito mode) #160

Open
1311-hack1 opened this issue Oct 29, 2024 · 0 comments

Comments

@1311-hack1
Copy link
Contributor

Description:

When using the toolbar to type(search on Incognito mode) and then quickly switching to another app, the CoordinatorLayout does not fully restore its height after the keyboard closes, resulting in a misaligned or shrunken layout of the rootView on return to Wootzapp. This issue seems to be specific to low-end devices, where limited resources prevent the CoordinatorLayout's height from recalculating correctly in the background when the keyboard closes.

Steps to Reproduce:

  1. Open Wootzapp on a low-end device.
  2. Switch to incognito mode.
  3. Focus on the toolbar input field to open the keyboard.
  4. Begin typing and then quickly switch to another app without manually closing the keyboard.
  5. Return to Wootzapp and observe that the CoordinatorLayout height remains reduced, as if the keyboard is still open, causing layout misalignment.

Expected Behavior:
The CoordinatorLayout should restore to its original height after the keyboard closes, ensuring the toolbar returns to its correct position and the layout realigns when switching back to the app.

Observed Behavior:
On returning to Wootzapp, the CoordinatorLayout height remains reduced, resulting in the toolbar appearing higher than normal and disrupting the layout.

Proposed Solution:
Consider adding a check to detect keyboard closure when the app resumes from the background, especially on low-resource devices, to ensure that the CoordinatorLayout height recalculates properly even in low-resource conditions.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant