You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hide the top (caption) and bottom (play controls) bars. (In the below video, I do this by waiting three seconds.)
Switch to another app within Android.
Switch back to Tusky.
Observed behavior: exactly ONE of the top and bottom bars will appear. If you tap, instead of dismissing as usual, it will toggle with each tap back and forth between exactly ONE of the top and bottom bars appearing, but it will switch back and forth. Once you are in this state the only way out is to either hit "back", or to wait three seconds for the bars to hide on their own.
This is clearly wrong, as well as frustrating.
This video is taken on Tusky 23.0 from the app store. However, I also see an identical problem on a self-built "develop" branch from today (with the exoplayer conversion).
Note: The video shows a screen recording of Tusky playing a video of a screen recording. This might be a little confusing.
screen-20231024-120849.mp4
The text was updated successfully, but these errors were encountered:
…ng leaves player/description UI in inconsistent state.
As part of implementing this, I: (1) standardized all hide queueing into the Play operation, removing two redundant hide queues (2) added logic so that if you suspend/resume after specifically requesting the player UI be shown, it doesn't hide itself.
Perform the following steps
Observed behavior: exactly ONE of the top and bottom bars will appear. If you tap, instead of dismissing as usual, it will toggle with each tap back and forth between exactly ONE of the top and bottom bars appearing, but it will switch back and forth. Once you are in this state the only way out is to either hit "back", or to wait three seconds for the bars to hide on their own.
This is clearly wrong, as well as frustrating.
This video is taken on Tusky 23.0 from the app store. However, I also see an identical problem on a self-built "develop" branch from today (with the exoplayer conversion).
Note: The video shows a screen recording of Tusky playing a video of a screen recording. This might be a little confusing.
screen-20231024-120849.mp4
The text was updated successfully, but these errors were encountered: