When the composer moves up due to the keyboard on mobile opening, the top of the composer is blocked by the site header.
Reply composer (normally):
Now:
Topic composer (normally):
Now:
The issue discusses a UX problem on mobile where the site header overlaps the topic and reply composers when the keyboard is active. NateDhaliwal reports that the composer’s top is blocked by the header, providing before-and-after images to illustrate the issue. chapoi initially couldn’t reproduce it, suggesting it might already be fixed. NateDhaliwal clarifies that the header is no longer visible due to the fullscreen composer, which chapoi confirms is intentional to maximize writing space.
When the composer moves up due to the keyboard on mobile opening, the top of the composer is blocked by the site header.
Reply composer (normally):
Now:
Topic composer (normally):
Now:
This I can’t repro anywhere atm. Maybe already fixed in the meantime? ![]()
I think so. The site header is no longer shown when the composer is opened (because of the fullscreen composer, possibly?).
Yes, that’s intentional, to maximime the space to write.