Voyager

5578 readers

22 users here now

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

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 1 year ago

MODERATORS

[email protected]

unscrollable video fields on iOS 17.1 & Voyager 1.17.1 (lemm.ee)

submitted 1 year ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

When autoplaying video appears in the main feed it is not possible to scroll using the area of the screen occupied by the video.

If the video is portrait, and fills the screen, it is no longer possible to navigate the feed without finding a way back or force quitting the app.

This bug was reported here previously and it was said at the time that it was iOS' fault and that the beta of iOS 17.1 fixed the problem. The problem remains.

Voyager 1.17.1 running on iOS 17.1 using an iPhone SE (2nd Generation).

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 1 year ago (2 children)

Yeah, the beta did fix the problem, but it came back in the official release. I don't know why, maybe there was some issue they had to revert the fix. It's very frustrating for me too.

https://bugs.webkit.org/show_bug.cgi?id=261950

I have a workaround to allow to scroll over videos, for next release but it doesn't work perfectly.

small rant, I really hate major iOS updates. There's always bad Safari regressions.

[–] [email protected] 3 points 1 year ago

The very last pass on a beta before it becomes final code is power usage optimization. Beta testers always complain about hot phones and dead batteries and then the update gets released and everything is fine. It's possible there was something about the fix as-is that got flagged as unoptimized or bloating to the update so it got removed.

Looking at the bug report, the developer who patched it doesn't seem to be 100% sure it worked. So that could also be the reason it got excluded.

I agree, it's a little silly. Fingers crossed for 17.2.

And thank you for making a bandaid in the mean time.

[–] [email protected] 2 points 1 year ago

Im not at all familiar with the processes of WebKit, but the commit that was the result of the PR which is referenced in the linked bug, is not part of any release tag yet. So it's unlikely that this change is available in any stable software that is built with WebKit (I.e. safari)