[Bug] unexpected behaviour tapping edge of screen in open external
gingerbeardman opened this issue · comments
Describe the Bug
Tapping edge of screen in an open/loaded external website results in options from the previous screen opening
To Reproduce
- Set up multiple externals
- Remember the vertical position of an external
- Open a different external
- Tap on the left edge of the screen at the position you remembered
Expected Behaviour
The tap should operate the current external
Actual Behaviour
The tap operates the previous screen, the externals list view
Screenshots
Screen recording available on request
Versions
6.0.0 iOS
Thanks for the bug report (and screen recording), I was able to duplicate the issue and attached a generic video without any personal host details.
An upstream package issue has been logged before (flutter/flutter#76692), I have commented with the video.
RPReplay_Final1645022861.mp4
Thanks!
Upstream bug closed in favour of a different 4-years-old issue flutter/flutter#14720
It's wild that this is still a problem for Flutter. Every single time I use LunaSea it catches me out.
Have you thought about porting away form Flutter? It seems abandoned to me. Currently there are 5000+ issues in their GitHub repo and the rate of new ones are appearing is higher than the rate at which old ones are being fixed.
Another example: scrolling with one finger scrolls at 100% speed, with 2 fingers scrolls at 200% speed, and scrolling with 3 fingers scrolls at 300% speed. I mean, it's just ridiculous.
There isn't really any path to port away from Flutter, it would need to be completely rewritten and I don't know Swift or Kotlin so that isn't happening anytime soon.
Flutter definitely isn't abandoned, the large issue count comes from many users making new issues for user-caused problems and not actual framework issues.
But don't let that come across as me excusing the issue relevant to this problem, it has been open for years with no updates in sight which is definitely frustrating.
No worries. I see your points.
There was recently a workaround posted for this:
flutter/flutter#14720 (comment)
Sadly, I can no longer post in the flutter issue thread, they didn't appreciate my enthusiasm for the issue to be resolved - they blocked me from the repo.