this post was submitted on 10 Oct 2023
15 points (100.0% liked)

Voyager

5653 readers
46 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 1 year ago
MODERATORS
 

https://lemmy.world/post/6565352

Can't scroll if starting with finger on the movie. And becomes major issue when video is large enough to fill entire screen. Iphone 13.

top 9 comments
sorted by: hot top controversial new old
[โ€“] Z4rK@lemmy.world 5 points 1 year ago

Same with gifs.

[โ€“] aeharding@lemmy.world 3 points 1 year ago (2 children)

This is an iOS 17 bug, but it's already fixed by apple engineers. Just needs time to make it downstream to everyone's devices ;)

[โ€“] Hobbes@startrek.website 3 points 1 year ago

Great, thank you!

[โ€“] aeronmelon@lemm.ee 1 points 1 year ago (1 children)

Do you mean it's fixed in 17.1?

[โ€“] aeharding@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

I'm not sure the exact release version of the patch

Edit: Confirmed fixed in iOS 17.1 beta 3

[โ€“] aeronmelon@lemm.ee 1 points 1 year ago

Got it. Thanks!

I purposefully avoided upgrading to 17.0.3 because of an unrelated sleep bug that puts the phone into some kind of power coma where it cannot even self-monitor or write logs.

If it had fixed the scrolling bug, I would have risked it. But I'll wait for 17.1 since it fixes both issues.

[โ€“] Sentau@feddit.de 2 points 1 year ago (1 children)

Can't replicate this on Android

[โ€“] Hobbes@startrek.website 2 points 1 year ago (1 children)

Sorry just realized that this occurred when the post was in my feed, scrolling by. Not when viewing the actual post.

[โ€“] Sentau@feddit.de 2 points 1 year ago* (last edited 1 year ago)

Yeah I got that and that was what I was trying to replicate by going to !videos@lemmy.world but I couldn't replicate it. Must be an iOS specific issue