Close and UnPiP buttons are supposed to work in different ways that account for specific use cases each of them has (get rid of the video vs return to it). Currently, we have a problem with Scenario #3 on this list: **Scenario 1 (close button + Firefox is in focus)** 1. Launch PiP window 2. Navigate away from the origin video tab, but stay in Firefox. 3. Click on the close button in the PiP window. Expected result: PiP window closes, video in the origin tab is paused. The origin video tab is not put in focus. Actual result: as expected **Scenario 2 (close button + Firefox is out of focus)** 1. Launch PiP window 2. Navigate away from the origin video tab and put another application into the focus. 3. Click on the close button in the PiP window. Expected result: PiP window closes, video in the origin tab is paused. Firefox does not return in focus. Actual result: Firefox returns in focus and opens the origin video tab. At least one user reports the video doesn’t pause. **Scenario 3 (unpip button + Firefox is in focus)** 1. Launch PiP window 2. Navigate away from the origin video tab, but stay in Firefox. 3. Click on the unpip button in the PiP window. 4. PiP window closes, Firefox returns in focus and opens the origin video tab, the origin video is paused. Actual result: as expected **Scenario 4 (unpip button + firefox is out of focus)** 1. Launch PiP window 2. Navigate away from the origin video tab and put another application into the focus. 3. Click on the unpip button in the PiP window. 4. PiP window closes, Firefox returns in focus and opens the origin video tab, the origin video is paused. Actual result: as expected The problem with Scenario 3 might have been introduced as a part of this patch: https://bugzilla.mozilla.org/show_bug.cgi?id=1687808 (possibly due to the ambiguity of what "de-activate PiP" means).
Bug 1756001 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Close and UnPiP buttons are supposed to work in different ways that account for specific use cases each of them has (get rid of the video vs return to it). Currently, we have a problem with Scenario #3 on this list: **Scenario 1 (close button + Firefox is in focus)** 1. Launch PiP window 2. Navigate away from the origin video tab, but stay in Firefox. 3. Click on the close button in the PiP window. Expected result: PiP window closes, video in the origin tab is paused. The origin video tab is not put in focus. Actual result: as expected **Scenario 2 (close button + Firefox is out of focus)** 1. Launch PiP window 2. Navigate away from the origin video tab and put another application into the focus. 3. Click on the close button in the PiP window. Expected result: PiP window closes, video in the origin tab is paused. Firefox does not return in focus. Actual result: Firefox returns in focus and opens the origin video tab. At least one user reports the video doesn’t pause. **Scenario 3 (unpip button + Firefox is in focus)** 1. Launch PiP window 2. Navigate away from the origin video tab, but stay in Firefox. 3. Click on the unpip button in the PiP window. 4. PiP window closes, Firefox returns in focus and opens the origin video tab, the origin video is not paused. Actual result: as expected **Scenario 4 (unpip button + firefox is out of focus)** 1. Launch PiP window 2. Navigate away from the origin video tab and put another application into the focus. 3. Click on the unpip button in the PiP window. 4. PiP window closes, Firefox returns in focus and opens the origin video tab, the origin video is not paused. Actual result: as expected The problem with Scenario 3 might have been introduced as a part of this patch: https://bugzilla.mozilla.org/show_bug.cgi?id=1687808 (possibly due to the ambiguity of what "de-activate PiP" means).