I had also noticed images being rendered in the wrong size lately. They’ll look normal at first, but if you scroll past them, then scroll back up; some images are ~150% size and falling off the edge of screen.
I haven’t encountered this yet. How recently? Since 84? or on 83 ?
That is a known problem, its because of the images,
I didn’t expect to find this here. You can ask Jerboa stuff in the Jerboa community.
We used to receive lots of noise regarding “Jerboa not working” due to external factors, i.e not caused by Jerboa. To avoid this and help/inform the user. I created this “verification” system.
Upon account login/switch or invalidation (like networks calls start failing)
the active account under goes verification.
This means Jerboa checks if:
Usually this doesn’t take long. I should probably document this somewhere but not sure where.
Maybe you enabled gesture navigation in Android.
There is such setting Jerboa.
Are you talking about the textsize changing when interacted with? I am not aware of that issue.
I can make one if you need it
Tables in a spoiler tag seem to have visual issues. Hmm interesting if you open it couple times it does properly render.
see test post https://lemmy.world/post/35633591|
Yeah, like what was written here already, the preview description is kinda scrollable. its a known bug, the markdown components use an AndroidView with a TextView. I haven’t found a way yet disable that scroll.
Scroll past mark read is supposed to work. If it doesn’t can you make a bug report, with some basic info (android version) + repro
Yes I worked on that update.
I meant more in adding such an option.
Yes we could but the “complex” part is the"link intercepting" part.
Jerboa still has a lot of issues, it just hasn’t been priority yet.
Stopping autoplay wouldn’t work so well for the feed video component. If you have to interact to see the video play, you might as well open it in the videoplayer. Maybe adding a disable “video display in feed” option would be a better idea.
The biggest problem is not the domain registering. We already link all “popular” lemmy instances through a script. The hard part is rather the id of that link is local to the instance. If ur on lemmy.world and click on lemmy.ml post we would need to translate the id of lemmy.ml to the id that it would be on lemmy.world. (This is possible) But a lot of work to hook that in correctly. We would need to intercept the link at the right place. Further if the post hasn’t federated yet. We would need to switch to that instance (lemmy.ml) to then show the post.
Yes, I have changed that logic.
Reasoning: From the feed you can already see the image or click into image. If you click on a post you want to either read the full post or the comments. The image is a distraction here.
It is black on black so it isn’t visible. I made a fix for it.
Sure, always the best place
For those affected you can temporary disable navigation bar in settings. And then you can navigate using the drawer.
It’s been fixed a while ago, just not released yet. There is few blockers.
84 contained fix for images rendering too large in comments. So it shouldn’t happen anymore