[Ubuntu] PiP gets smaller if you navigate back and forth between videos with different formats
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox74 | --- | wontfix |
firefox75 | --- | wontfix |
firefox76 | --- | wontfix |
firefox77 | --- | fix-optional |
firefox78 | --- | fix-optional |
People
(Reporter: obotisan, Assigned: stransky)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
(Keywords: regression)
Attachments
(2 files)
Note
- This bug happens when the videos have different formats.
- Please look at the attached gif.
Affected versions
- Firefox 74.0b6
- Firefox 75.0a1
Affected platforms
- Ubuntu 18 x64
Steps to reproduce
- Go to a video on youtube (e.g: https://www.youtube.com/watch?v=R7A1mIdiheE)
- Click on the Picture-in-Picture button.
- From the video controls click on the next song.
- From the browser controls click on the "Go back page" button.
Expected result
- The video has the same dimensions as in step 2.
Actual result
- The video gets smaller.
Regression range
- If it's a regression I will try to find it as soon as possible.
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Hey Mark,
I seem to recall us considering this scenario when you were working on the window resizing bits for PiP... was this case not covered somehow?
Comment 2•5 years ago
|
||
So I poked around at this on linux a little, added some dump calls with the expected size and position combinations and the math seems to add up correctly, but sometimes the window will end up moving/shrinking. Seems like the size/position isn't ending up as what PictureInPicture.jsm is requesting, I tried moving the window away from the edge of the screen to see if it was moving off the screen and being recalculated but that didn't seem to fix it. This still happens intermittently.
We have tests for this, but they were originally disabled on linux [1] since the resizing wasn't implemented, they weren't enabled again when the resizing patch landed. I tried running the tests on linux but they all fail since it can't decode the video file for some reason.
We should look at enabling that test file on linux, I'm guessing it would have intermittent failures right now though.
Comment 3•5 years ago
|
||
Poked a little more and it looks like the win.moveTo(left, top)
call [1] is basically being ignored. We're calculating the new expected window size and position then calling win.resizeTo(width, height);
immediately followed by win.moveTo(left, top)
. I wrapped the win.moveTo()
call in win.setTimeout(() => win.moveTo(...), 100)
and it started working. Adding 500ms timeouts to the tests made them pass.
@stransky is there some other way we should be resizing and moving this window at the same time or do you have any idea why the win.moveTo()
call is being ignored?
Assignee | ||
Comment 4•5 years ago
|
||
Yes, Linux/Gtk uses async resize. I'll look at it.
Assignee | ||
Updated•5 years ago
|
Comment 5•5 years ago
|
||
The product::component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.
Comment 6•5 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Martin, could you please set the priority flag? Is it still P3?
Assignee | ||
Comment 8•5 years ago
|
||
I can reproduce that on Fedora 32/X11 too. Works ok on Wayland.
Assignee | ||
Comment 9•5 years ago
|
||
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•5 years ago
|
Comment 12•5 years ago
|
||
Hello,
This issue is still reproducible on Firefox 76.0a1 (2020-04-02).
Here is a screenrecording with the issue: https://drive.google.com/file/d/1gh8Zugbs89vWbPV-kfhoYKrb5OGJ1N3c/view?usp=sharing
Assignee | ||
Comment 13•5 years ago
|
||
(In reply to Maria Berlinger [:maria_berlinger], Release Desktop QA from comment #12)
Hello,
This issue is still reproducible on Firefox 76.0a1 (2020-04-02).
Here is a screenrecording with the issue: https://drive.google.com/file/d/1gh8Zugbs89vWbPV-kfhoYKrb5OGJ1N3c/view?usp=sharing
And which distro/DE do you run?
Comment 14•5 years ago
|
||
Sorry that I forgot to mention, Ubuntu 18.04x64.
Assignee | ||
Comment 15•5 years ago
|
||
(In reply to Maria Berlinger [:maria_berlinger], Release Desktop QA from comment #14)
Sorry that I forgot to mention, Ubuntu 18.04x64.
Can you set "widget.use-aspect-ratio" to false and retest please?
Thanks.
Comment 16•5 years ago
|
||
By creating the "widget.use-aspect-ratio" and set it to false, the issue is no more reproducible.
Updated•5 years ago
|
Comment 17•5 years ago
|
||
Hello
Martin, do you think is worth filling another bug or to reopen this one, because the “widget.use-aspect-ratio" pref is not set by default on false and the issue still reproduces.
Assignee | ||
Comment 18•5 years ago
|
||
(In reply to Maria Berlinger [:maria_berlinger], Release Desktop QA from comment #17)
Hello
Martin, do you think is worth filling another bug or to reopen this one, because the “widget.use-aspect-ratio" pref is not set by default on false and the issue still reproduces.
That's really up to you, I don't have a strong opinion here.
When widget.use-aspect-ratio is set, keeping window aspect radio is disabled so the window is more difficult to resize by mouse cursor - you need to keep the aspect manually.
But it also fixes this bug and we can revert Bug 1624921 (PIP mode is switched back to system decorations) which fixes Bug 1622203.
Comment 19•5 years ago
|
||
Based on the fact that "widget.use-aspect-ratio" = false pref isn't by default in Firefox (you should add it manually) this issue is still reproducible and the user will be hit by this problem, so in my humble opinion we should reopen this bug based on this assessment.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 20•4 years ago
|
||
I wonder if a patch from Bug 1683075 can help here.
Updated•2 years ago
|
Comment 21•2 years ago
•
|
||
This issue no longer occurs, when using the steps in comment 0, however, the PiP has suffered a redesign in the meantime and other similar issues still reproduce today. (ex. bug 1759537)
This being considered, I will close this report as worksforme.
Description
•