iPad keyboard obscures chat window

AI-generated summary

Users have reported that on iPads, the on-screen keyboard obscures the chat window in Discourse, making chat difficult to use. PeakProsperity first flagged the issue, noting the user was on iPadOS 16.3.1 using Safari, and provided a screenshot similar to one posted by awesomerobot, who confirmed a regression in the overlay chat mode. As a workaround, awesomerobot suggested using fullscreen chat mode, which avoids the overlap. Further investigation confirmed the issue stems from the difficulty of reliably repositioning elements above the virtual keyboard. The planned fix is to disable the “drawer” chat mode on iPads and force fullscreen mode, though this has not yet been implemented. schneeland confirmed the issue persists in version 3.3.0.beta2 -dev, sharing another screenshot to illustrate the overlap.

One of our users has reported that the on-screen iPad keyboard obscures the chat window in Discourse, making it very challenging for her to use the chat functionality on an iPad. Thought I would flag it here in case it’s something that can be improved upon. Thanks.

2 Likes

Do you have a screenshot or any other information that could help us troubleshoot? iOS version could help too.

I do see a regression with the overlay version of the chat and the keyboard… is this the same issue?

In the meantime it may help to use fullscreen chat (there’s an expand button), which seems to avoid this issue

Screenshot 2023-03-13 at 4.20.27 PM

2 Likes

Below please find a screenshot, which is similar to the one you posted. She is using iPadOS 16.3.1 and Safari as the browser. Hope this helps!

1 Like

This is helpful, thanks! we’ll look into it

1 Like

Ah I just had to refresh my memory on this… It’s difficult to reliably reposition an element above the virtual keyboard when it’s opened, so we plan on disabling the “drawer” mode of chat on iPad and will force full-screen mode, but we haven’t gotten to it yet.

3 Likes

Just to double check: the last statement is still valid? Because I still see this issue on 3.3.0.beta2-dev.