thunder-app
Feed menu soft-lock
Bug Description
Opening and closing the menu behind the Feed tab's "+" FAB in a single swipe breaks the FAB, leaving it and the menu inaccessible.
Expected Behaviour
The menu to close again, returning to the state before it was opened.
Steps to Reproduce
- Open the Feed tab
- In one tap:
- press and hold the + button
- swipe up, revealing the menu
- swipe down, closing it again
Result:
- menu is dismissed, but screen remains faded out
- tapping the screen fades the feed back in,
- FAB and menu are missing until the app is relaunched
Additional Context
No response
App Version
0.6.1
Device
OnePlus Nord CE
OS
Android 13
Thanks for the report! I was able to reproduce this, but it might not necessarily be a bug in the usual sense.
For some additional context, there's a somewhat hidden feature where you can hide the FAB from the screen by swiping down on the FAB. You can then bring the FAB back up by swiping in the area where the FAB usually sits.
https://github.com/user-attachments/assets/389f9579-e731-4f01-9224-f374508995b2
When you perform the single action (swiping up on the FAB and then back down), this triggers both actions to occur:
- Swiping up expands the FAB
- Swiping down hides the FAB
Admittedly, I'm not entirely sure how many people use this feature for temporarily hiding the FAB, so a solution to this could be to remove this functionality.
Aha, so it does! And indeed swiping up does bring it back, even after doing a combined swipe that triggers both actions, so you can ignore the soft-lock part of this issue. 🙂 (I thought I'd tried getting it back that way before, though probably swiped in the wrong place!) There's just the minor UI quirk of the screen remaining faded out if you do trigger both actions at once.
For context, I tend to do my scrolling from the bottom-right corner (as the easiest place to reach one-handed), so often accidentally bring up the menu instead of scrolling down. I've got fast enough at dismissing the menu now that I've started doing it without letting go, which leads to this issue. Now that I know dismissing it is a feature, that could be useful for avoiding this... except that the swipe to reveal the button again is in the same spot, so instead I just reveal the button again.
Perhaps having the menu open from a left swipe of the FAB would be less of a clash with scrolling, though it's then competing with gestures instead if they're enabled (and messes with the muscle memory of existing users if it's changed). I've got the "combine FAB and navigation buttons" option enabled for comments, which keeps the corner free while keeping the reply button fairly accessible; something similar for the main feed could also work.