It’s the only thing that keeps me from using this as my go-to source for lemmy.
It’s dependent on Apple fixing it, so no:
Given that the bug was raised well over two years ago, it does not seem likely that Apple will fix it anytime soon.
Maybe it is one of the reasons that the Voyager developers are working on a native IOS version?
This conversation reminds me of my favorite Firefox bug/request https://bugzilla.mozilla.org/show_bug.cgi?id=77790
It only took 18 years to be addressed and closed. Hopefully this scrolling bug in WebKit fares better.
Any link to where the Dev has made these statements?
they are? that’s great news :)
Didn’t realize that was a big bug. I’ve noticed that if I drag up from the bottom of the screen a little, like I’m pulling up the list of running apps, but then drag back down without actually opening the list; just enough that the app STARTS to shrink, but before the apps display; it unfreezes.
That’s not necessary - just stop interacting with the device for approximately one second and it will “unfreeze”
I don’t want to have to keep doing that.
You don’t need to do that. Just stop interacting for a second and it will “unfreeze”
Just so we’re clear here, is this the official stance? You have no plans to resolve this and we’re just supposed to put up with it?
I would love to fix this, but it’s a browser bug. Feel free to complain here: https://bugs.webkit.org/show_bug.cgi?id=222654
Alright, thanks for all your hard work. I’ll be switching to something else that doesn’t rely on broken tools then until Apple resolves it, I suppose.
I know I’m being downvoted for seeming entitled or whatever, but as an end user, broken is broken. I get that it’s not your fault and I’ve never once complained that it was but why would you move forward with this project if such a massive problem affects such a large portion of your potential users? Clearly it’s your right to do so, but as someone who actively wants to keep using Voyager and just can’t justify it, I really don’t get it.
Good luck with your project. Sincerely.
For the record, I love Voyager and don’t understand why you’re being downvoted either. Even if it’s not the dev’s fault, something that ruins the usability of the app shouldn’t just be ok for them to ignore and not try to work around. You have a perfectly valid criticism.
what was the point of writing this? and have you failed to consider that android is the larger mobile platform where this bug doesn’t happen? apple is the one that deserves the whining, go direct it at them
I’m not now, nor was I ever whining. I asked a question to the developer to get clarification. When I started using wefwef before it was even Voyager it had many bugs including this one. Almost all of them have been fixed and many other improvements have been made, so I was under the assumption that some workaround or fix would be found to stop this one from happening. I simply asked if that was the case and when I found out that it wasn’t I thanked the developer for his time and explained why I wouldn’t be using his app in the future. There was no whining at any point in time.
Also, I never made an assumption about Android usage vs iOS or ever speculated what percentage of Voyager users are on iOS. I know it’s a fairly large amount because every time someone brings up the scrolling issue most of the comments usually get a couple dozen upvotes from people wanting to know when it’s going to be fixed. It doesn’t matter to me if it’s 10% of the users here or 90%. I am affected, and so are many other users. I fail to see what point you think you made by pointing out that android is a larger mobile platform.
If you want to go around asking people what the point of writing something was, maybe start with yourself.
What are you guys even talking about? I don’t think I’ve ever had this webapp freeze or stop working/crash a single time.
Oh, you haven’t? Well never mind then. If it’s never happened to you then I guess I shouldn’t worry about it happening to me all the time. Thanks!
deleted by creator
Exactly. They’re saying it’s an apple issue, but it ONLY happens using this web app and no other instances.
