Users report a persistent bug on Android tablets where the on-screen keyboard overlaps the composer when replying to posts after scrolling down a topic — a behavior not seen when scrolling up or on phones. ljpp notes this has existed for a long time and is not a recent regression, though it affects few users due to declining tablet usage and iPad dominance. Moin confirms the issue on their tablet and observes it doesn’t occur immediately after opening a new tab on Discourse Meta, suggesting a possible state dependency. Further testing by Moin reveals Firefox behavior varies depending on whether the toolbar is visible, and Moin finds that opening and closing full-screen chat breaks the composer’s keyboard positioning until the page is reloaded. merefield and Heliosurge report similar issues on Pixel devices (mobile), even affecting editors like theme and form templates — though adding blank lines can temporarily workaround the visibility issue. The bug appears tied to viewport state, browser UI, and possibly chat interactions, but remains unresolved and under investigation.
Our users have discovered a bug that impacts Android tablets, but can also be reproduced using the Chrome dev tools as an emulator.
The repro pattern seems to be:
—> Keyboard overlaps the composer
When scrolling upwards, this does not happen. Seems to impact only tablet form factor - never seen this on a phone.
Is this a regression or was it always like this?
Not sure about “always”, but definitely it is not a recent regression – the behavior has been like this for a long time.
Tablets have lost popularity (to smartphones) over the years and a majority of them are iPads, so this does not impact many users in our community or globally.
This issue has now occurred on my tablet as well. However, it does not happen after I open a new tab with Discourse Meta. Is there anything I can do to help find the cause of this problem?
The tab did reload now. But I’m still interested in whether there is something I can check if it happens again.
When using Firefox, it seems to depend on whether the toolbar is shown or not.
Opening and closing full-screen chat also affects how the composer and keyboard interact. It functions properly until I open the full-screen chat. Afterwards it fails.
My Pixel (albeit mobile) keyboard hides the Chat Composer completely.
My Pixel does the same also with places like theme editor & form-templates editors. Though adding a lot of blank lines makes it so you can see what your editing.
