[macOS] PiP is fullscreen when launched from a full screen window
Categories
(Core :: Widget: Cocoa, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | wontfix |
firefox103 | + | fixed |
firefox104 | --- | disabled |
firefox105 | --- | disabled |
firefox127 | --- | wontfix |
firefox128 | --- | verified |
People
(Reporter: yoasif, Assigned: bradwerth)
References
(Regression)
Details
(Keywords: regression)
Attachments
(4 files)
9.01 MB,
video/quicktime
|
Details | |
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
dmeehan
:
approval-mozilla-release+
|
Details | Review |
9.15 MB,
video/mp4
|
Details | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Steps to reproduce:
- Navigate to https://www.youtube.com/watch?v=E31fNqvEWTk
- Click "full screen" button in Firefox window (green window decoration)
- Play video
- Click PiP button overlay in Firefox
What happens:
The PiP window opens in a new fullscreen window and doesn't act like a PiP window (doesn't overlay other windows if moved to a different screen, for example).
Expected result:
As prior to regression.
19:05.56 INFO: Narrowed inbound regression window from [430c8dbe, 8e63cdd5] (3 builds) to [430c8dbe, 709f48d5] (2 builds) (~1 steps left)
19:05.56 INFO: No more inbound revisions, bisection finished.
19:05.56 INFO: Last good revision: 430c8dbe41323dd546c10160706b52d118ef6361
19:05.56 INFO: First bad revision: 709f48d5b8373bf1547db9566f120fbddc5bddf4
19:05.56 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=430c8dbe41323dd546c10160706b52d118ef6361&tochange=709f48d5b8373bf1547db9566f120fbddc5bddf4
I tested this on macOS 10.15.7 (19H1922) - I have not tried other macOS versions, so the behavior may be different elsewhere.
![]() |
||
Comment 1•3 years ago
|
||
Bug 1781483 seems duplicated
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Set release status flags based on info from the regressing bug 1700674
Comment 3•3 years ago
|
||
:KrisWright, since you are the author of the regressor, bug 1700674, could you take a look?
For more information, please visit auto_nag documentation.
Reporter | ||
Comment 4•3 years ago
|
||
Someone is seeing this on macOS 11.6 as well: https://www.reddit.com/r/firefox/comments/w9lkua/picture_in_picture_mode_goes_into_full_screen/
Attaching a recording of behaviour that I believe to be linked to this issue. This was tested on MacOS 11.6 with a 2 screen setup, with the source video open in a fullscreen window (via green button). (Video was also cropped to reduce file size)
Updated•3 years ago
|
Comment 7•3 years ago
|
||
Tracking for 103 dot release potential - S2 severity.
Is backing out the regressor an option for release?
Comment 8•3 years ago
|
||
(In reply to Donal Meehan [:dmeehan] from comment #7)
Is backing out the regressor an option for release?
This seems like an option to me, but the best person to answer this question would be the author of bug 1700674, Kris.
Comment 9•3 years ago
|
||
The bug is marked as tracked for firefox103 (release). However, the bug still isn't assigned.
:gcp, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 10•3 years ago
|
||
Based on prior discussion it looks like the best fix until we know what's going on here is to back out bug 1700674.
Comment 11•3 years ago
|
||
Comment 12•3 years ago
|
||
Adding leave-open
since this backout doesn't address the underlying issue caused in bug 1700674.
Comment 14•3 years ago
|
||
Comment 15•3 years ago
•
|
||
Comment on attachment 9287977 [details]
Bug 1781830 - Backout bug 1700674. r?mhowell
Beta/Release Uplift Approval Request
- User impact if declined: Users will continue experiencing picture-in-picture issue
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce:
- Navigate to https://www.youtube.com/watch?v=E31fNqvEWTk
- Click "full screen" button in Firefox window (green window decoration)
- Play video
- Click PiP button overlay in Firefox
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This patch simply reverts the regressing patch to address regressions until we know what's going on.
- String changes made/needed:
- Is Android affected?: No
Comment 16•3 years ago
|
||
bugherder |
Comment 17•3 years ago
|
||
Comment on attachment 9287977 [details]
Bug 1781830 - Backout bug 1700674. r?mhowell
Approved for 104.0b5
Comment 18•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Comment 19•3 years ago
|
||
Comment on attachment 9287977 [details]
Bug 1781830 - Backout bug 1700674. r?mhowell
Approved for 103.0.2, thanks.
Comment 20•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Updated•3 years ago
|
Comment 22•3 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:KrisWright, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 23•2 years ago
|
||
The leave-open keyword is there and there is no activity for 6 months.
:KrisWright, maybe it's time to close this bug?
For more information, please visit BugBot documentation.
Comment 24•1 years ago
|
||
This issue seems to be back on Firefox Nightly 125.
Currently using 125.0a1 (2024-02-24) (64-bit) on a Macbook Pro 16" with the M1 Max running macOS Sonoma 14.3.1 (23D60).
Comment 25•1 year ago
|
||
(In reply to Celso from comment #24)
Created attachment 9382482 [details]
screen_recording.mp4
This is now happening on beta: 125.0b2 (64-bit)
Comment 26•1 year ago
|
||
(In reply to Celso from comment #24)
Created attachment 9382482 [details]
screen_recording.mp4This issue seems to be back on Firefox Nightly 125.
Currently using 125.0a1 (2024-02-24) (64-bit) on a Macbook Pro 16" with the M1 Max running macOS Sonoma 14.3.1 (23D60).
Now happening on 125.0...
Comment 27•1 year ago
•
|
||
(In reply to Celso from comment #26)
(In reply to Celso from comment #24)
Created attachment 9382482 [details]
screen_recording.mp4This issue seems to be back on Firefox Nightly 125.
Currently using 125.0a1 (2024-02-24) (64-bit) on a Macbook Pro 16" with the M1 Max running macOS Sonoma 14.3.1 (23D60).
Now happening on 125.0...
Thank you!
Confirming this. It seems that this issue came back after bug 1880558. Brad, can you please take a look?
Assignee | ||
Updated•1 year ago
|
Comment 29•1 year ago
|
||
Still present on 126.0b3 fyi.
Comment 30•1 year ago
|
||
Hey bradwerth,
We keep getting reports about this one on various channels... are you still working on this?
Assignee | ||
Comment 31•1 year ago
|
||
This is a weird one. The initial call to show the PiP window triggers a macOS internal codepath that eventually calls a private method _enterAutomaticFullScreen
, which we want to prevent. Since it's private, and the path to it is in code we can't inspect, then I'll have to experiment a bit to determine what conditions are involved. Whatever those conditions are, we'll probably want to shut them off for any alwaysOnTop windows, any dialogs or popups. None of those should begin life in fullscreen.
Assignee | ||
Updated•1 year ago
|
Comment 32•1 year ago
|
||
Would it be possible to swizzle _enterAutomaticFullScreen
and skip it for alwaysOnTop windows?
Assignee | ||
Comment 33•1 year ago
|
||
(In reply to Stephen A Pohl [:spohl] from comment #32)
Would it be possible to swizzle
_enterAutomaticFullScreen
and skip it for alwaysOnTop windows?
Swizzle meaning override it and supply our own no-op behavior? Maybe, but that makes us dependent on the naming of a private method, which feels fragile. Alternatively, we can just temporarily manipulate the collectionBehavior
which is what was affected by the changes in Bug 1880558. I've built a patch that does that and we'll see how reviewers feel about it.
Assignee | ||
Comment 34•1 year ago
|
||
I think we could also argue that opening new fullscreen windows from fullscreen windows is current behavior and shouldn't be special-cased for PiP windows. Once we "fix" this, I suspect we're going to get bug reports that the new PiP window doesn't appear in the same space as the fullscreen window, which is impossible given the way fullscreen spaces work in macOS.
Assignee | ||
Comment 35•1 year ago
|
||
Though this is standard behavior for other windows, we want to
special-case this for PiP windows, which users expect to open in
resizable popups. This patch also prevents other popups and
alerts/dialogs from opening in fullscreen mode, which would be a bad
user experience.
Assignee | ||
Updated•1 year ago
|
Comment 36•1 year ago
|
||
please fix this. Its been 2 years. Thanks.
Comment 38•1 year ago
|
||
Comment 39•1 year ago
|
||
bugherder |
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 40•1 year ago
|
||
Hello! I can confirm that the issue is fixed with firefox 128.0b1 on MacOS 12.6, I will update the status and the flags of this issue.
Have a nice day!
Description
•