this post was submitted on 20 Dec 2025
43 points (100.0% liked)

Voyager

7623 readers
50 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! πŸ‘‡

Number of sponsors badge

πŸ’™

founded 2 years ago
MODERATORS
 

Using Android 13. Heres how it looks normally

collapsed inline media

top 6 comments
sorted by: hot top controversial new old
[–] Septimaeus@infosec.pub 6 points 14 hours ago

I suspect it’s the container for the comment textarea getting left behind after submission, where the vertical misalignment is the top+bottom padding of the container, because Android uses a different rendering engine for PWAs which follows slightly different rules in its box model, especially WRT flexbox.

Yeah I've been seeing this bug for years

[–] gigachad@piefed.social 4 points 15 hours ago
[–] xploit@lemmy.world 4 points 13 hours ago* (last edited 13 hours ago) (1 children)

Don't even need to post, just opening a reply can cause it as soon as the main screen is in the background. Also have been observing it for the last few months (latest Android versios).

I do wonder whether there are any people without curved display who observe this, it seemed like a mix of that and what Septimaeus has mentioned.

Edit: I always fail to recreate the issue after closing and reopening Voyager, however it generally seems to happen only after some time of app being open (not sure active scrolling through content is even necessary), at least 15-20 min from my perspective... so in that time something happens that makes android/Voyager forget appropriate app window scaling.

[–] Septimaeus@infosec.pub 2 points 11 hours ago

In that case my guess is wrong, or at least off, because that sounds like an orphaned component, or perhaps a logic misfire corrupting the state with the effect of partially activating a notification tray or something of the sort.

In the worst case, it could be a viewport dim calculation bug that has nothing to do with Voyager. IME those can persist for a long time, forcing developers to work around it.

If the behavior can be reproduced in a browser, you could use the built in devtools to narrow it down quickly.

[–] Venus_Ziegenfalle@feddit.org 3 points 13 hours ago* (last edited 13 hours ago)

Happens for me too since the last update