Fix issue #1030 #1031
No reviewers
Labels
No labels
android: closed alpha
android: open beta
app-parity
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
creator
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
product review
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-android#1031
Loading…
Reference in a new issue
No description provided.
Delete branch "fix_issue_1030"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Dismiss all active dialog fragment when entering PiP mode
So that PiP window contain the video only
PR Checklist
Please check all that apply to this PR using "x":
PR Type
What kind of change does this PR introduce?
Fixes
Issue Number: 1030
What is the current behavior?
Support/Repost dialogs interfere with video displayed in PiP mode
What is the new behavior?
When entering PiP mode - any unfinished dialogs are dismissed,
leaving the PiP clean of any unrelated artifacts
Other information
In order to plan ahead and close any current and future dialogs that can be opened
from fileViewFragment - I'm scanning the fragment manager of the main activity - looking for instances of DialogFragment.
If I find any - I dismiss them.
Alternatively, I could have gone with implementing PIPModeListener in RepostClaimDialogFragment and CreateSupportDialogFragment - dismissing themselves on PiP enter , and doing nothing on return from PiP,
While registering/deregistering them on OnStart and OnStop
I don't think this solution scale well , and it will lead to code duplication.