Navigating back in a custom tab closes a video in picture-in-picture mode
Categories
(Focus :: General, defect)
Tracking
(firefox153 wontfix, firefox154 wontfix, firefox155 fixed)
People
(Reporter: jonalmeida, Assigned: jonalmeida)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file, 1 external file)
|
5.87 MB,
video/mp4
|
Details |
Prerequisite
- Make Focus your default browser.
Steps to reproduce
- Navigate to youtube.com.
- Start playing a video, make it fullscreen and press the home button, in order to put the video into PIP mode.
- Go into another app that opens links in a custom tab (e.g. Gmail).
- Click a link there.
- When the page starts loading (or finishes loading), navigate back.
- Observe the PIP window.
Expected results
- The PIP video should continue playing.
Actual results
- The PIP window is closed.
Additional information
- See attached video.
- Reproduced on Pixel 8a, Android 16.
- This is reproducible on 153 and 155 (nightly).
| Assignee | ||
Comment 1•2 months ago
|
||
This is an S2 because it leads to data loss without any recoverable options or workarounds.
| Assignee | ||
Comment 2•2 months ago
|
||
From a mozregression:
Newest known good nightly: 2024-08-20
Oldest known bad nightly: 2024-08-21
| Assignee | ||
Comment 3•2 months ago
|
||
Found the regressor.
The commenting out the one-liner fixes this bug and interesting also doesn't reproduce the original bug that the patch was solving, so something else in the system has changed to cover this case.
| Assignee | ||
Comment 4•2 months ago
|
||
The regressor bug's STR do not seem to reproduce the bug anymore, so its
possible that another part of the system covers this case. In any case,
we can fix our bug by providing the tabId for the session we want to
exit instead of using default that closes the custom tab and the
selected tab at the same time.
Comment 5•2 months ago
|
||
Set release status flags based on info from the regressing bug 1892407
Updated•2 months ago
|
Comment 7•2 months ago
|
||
| bugherder | ||
Comment 8•2 months ago
|
||
The patch landed in nightly and beta is affected.
:jonalmeida, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox154towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 9•2 months ago
|
||
The bug has existed for almost a year, at this point, we can allow it to ride the trains.
Updated•2 months ago
|
Description
•