Closed
Bug 1666923
Opened 4 years ago
Closed 4 years ago
fission.sessionHistoryInParent set to true breaks Picture-in-Picture
Categories
(Core :: DOM: Navigation, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox83 | --- | fixed |
People
(Reporter: sdk, Assigned: smaug)
References
Details
(Keywords: nightly-community)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
- Set
fission.sessionHistoryInParent
totrue
- Restart the browser
- Go to youtube (e.g https://www.youtube.com/watch?v=JDUnSsx62j8)
- Toggle Picture-in-Picture (either with the button or the keyboard shortcut)
Actual results:
Picture-in-Picture shows an empty window. Also, trying to close the Picture-in-Picture window doesn't work with the keyboard shortcut. The flickering of the window happens when you trigger the shortcut. You have to click on the close button of the PiP window.
Expected results:
The video should be moved to the PiP window and you should still be able to close the PiP window with the keyboard shortcut.
Reporter | ||
Updated•4 years ago
|
Blocks: fission-dogfooding
Keywords: nightly-community
Assignee | ||
Updated•4 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
That wip patch isn't correct one, but might make sense anyhow (and perhaps should land if the real fix for this takes a bit time).
Assignee: nobody → bugs
Updated•4 years ago
|
Severity: -- → S1
Status: NEW → ASSIGNED
Fission Milestone: --- → M6b
Priority: -- → P1
Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Blocks: fission-history-m6b
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/81f66369d5a7
fission.sessionHistoryInParent set to true breaks Picture-in-Picture r=mconley
Comment 6•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox83:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•