test 1
testAccount
joined 2 years ago
The image viewer is supposed to let the image draw behind the system bars, covering the full display. The tap is supposed to hide/show the systembars, to imitate full screen behaviour.
On tap it just asks Android to hide/show systembars. So its quite strange that it behaves differently here for the status bar. Probably something to do with Android 14.
See https://github.com/user-attachments/assets/ba96831c-e515-4c92-b9f4-4c73f6277926
You can selectively hide any of the scores in the account settings .
Do you remember the post? So that I can reproduce it.
oke i can reproduce it now. Whats strange that it seems to be only happening through community > post. profile > post doesn't have this.
There isn't a setting for it yet. With the rework Dessalines added a fade to the body.
I cant reproduce this, Android version? Phone? LTR/RTL ?
Can you check if you have post navigation gestures or Preset for swipe gesture enabled? Disable both and see if it still persists.
It is not a Jerboa issue,
This community has never been active and that was the latest post in Jerboa in Lemmy instance.
You can query this directly and see.
https://lemmy.one/api/v3/post/list?type_=All&sort=New&community_id=49 https://lemmy.world/api/v3/post/list?type_=All&sort=New&community_id=91
Lemmy always had some federation issues its better now then before.
But you can still see some issues. For example
lemmy.world does not have the switching language on gboard. post.
see https://lemmy.world/c/[email protected]?dataType=Post&sort=New
As a test, I tried posts from /all/, and was quickly able to find one that is visible for me from /all/ but does not appear on its own community page under new - the post on [email protected] about a 271 page document on Vance (about an hour ago).
Did you check this within the same instance? /all/ and the community page?
I checked right now and I found the post you are talking about. So it is definitely visible right now. https://lemmy.world/post/18503617
I can't see the video but It should be fixed in the next release
You still experience this with 0.71 and on which instance?
That sounds like this bug,
https://github.com/coil-kt/coil/issues/2287#issuecomment-2168638831
which is most likely the same as https://github.com/coil-kt/coil/issues/2298
view more: next ›
test 2