Snapping Picture-In-Picture videos to the left/right/top with the mouse displays thick white bars on the video's sides
Categories
(Toolkit :: Video/Audio Controls, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox71 | --- | verified |
People
(Reporter: itiel_yn8, Assigned: mconley)
References
Details
Attachments
(5 files)
STR:
- Use Windows
- Open any video in Picture-In-Picture mode
- Press Win key+left/right/up arrow keys
AR:
a. Snapping the video to the top once adds 2 big white bars to the video (one above the video and another on its bottom) covering half of the screen
b. Snapping the video to the right/left adds 2 white bars to the video (one on its right and another on its left). Also the video gets ~2x bigger
c. Snapping the video to the top twice makes the video look the same as in #b, but on the upper part of the screen
d. Snapping the video to the top thrice makes it go fullscreen, and adds a white bar to the video's bottom part
ER:
No white bars, and potentially no 2x bigger videos (?)
You'll need to open the third attachment here in a new tab to see the white bar at the bottom.
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Comment 4•6 years ago
|
||
It seems we can disable Windows Aero snap for the PiP windows when it's of type "dialog".
Patch coming up.
Assignee | ||
Comment 5•6 years ago
|
||
This also seems to make the player window buttons work more reliably with touchscreens.
![]() |
||
Comment 8•6 years ago
|
||
bugherder |
I'm on the latest Nightly and this doesn't seem to be fixed, but bug 1543031 and bug 1536011 are fixed here, so this patch should be included in my Nightly.. I'm on Windows 10.
mconley, what info do you need to debug this?
Comment 10•6 years ago
|
||
Can confirm what Itiel said, this is still reproducible on latest Nightly 71.0a1 (2019-09-16) (64-bit).
Mike, should we re-open this one or submit a new bug?
Comment 11•6 years ago
|
||
Assignee | ||
Comment 12•6 years ago
|
||
Gah, when I was testing this, I was snapping with the mouse and not the keyboard. :(
Yes, I'll get a new bug on file.
Updated•6 years ago
|
Comment 13•6 years ago
|
||
Confirmed issue with 68.0a1 (2019-04-09).
Verified fix with 71.0b5.
Description
•