The PIP window will only resize to smaller size in Linux / Wayland
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: danibodea, Assigned: stransky)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [fidefe-MR1-2022])
Attachments
(3 files)
Note
- When the user opens the browser with wayland window protocol, loads a youtube video and clicks the "Watch in Picture-in-Picture" button and then grabs the vertical or horizontal margins (not the corners) and attempts to enlarge it, he will notice that the PIP window won't resize.
Affected versions
- Nightly v96.0a1
Affected platforms
- Ubuntu 21 + wayland
Steps to reproduce
- Launch browser with wayland window manager:
a. Go into the nightly folder.
b. Right-click and "Open in Terminal".
c. MOZ_ENABLE_WAYLAND=1
d. ./firefox - Load https://www.youtube.com/watch?v=SXr8Rb97nIk
- Click the "Watch in Picture-in-Picture" button.
- Grab a vertical or horizontal margin and enlarge the PIP window.
Expected result
- The PIP frame is resized correctly.
Actual result
- The PIP video is not being resized as expected.
Regression range
- unknown.
Additional notes
- This issue occurs with "wayland" Window Protocol and not with "xwayland".
Assignee | ||
Comment 1•3 years ago
|
||
Yes, I can reproduce it. We may rework the PIP on Wayland a bit. The PIP is missing shadows and can be only downsized. To enlarge you need to use corners.
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•2 years ago
|
||
This is still reproductible. Martin, it looks like the Atlassian ticket is inaccessible to me, can you share if there has been updates there?
Assignee | ||
Comment 5•2 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #4)
This is still reproductible. Martin, it looks like the Atlassian ticket is inaccessible to me, can you share if there has been updates there?
I don't have access to it. Tested latest nightly and the PIP window can be resized by sides, not just corners.
Assignee | ||
Updated•2 years ago
|
Comment 6•2 years ago
|
||
I do repro the issue on my ubuntu system.
Updated•2 years ago
|
Comment 8•2 years ago
|
||
This bug is not restricted to snap.
It is possible to increase the size a few pixels at a time by alternating between the horizontal and vertical edges, it stops when the other dimension needs to grow. Single-edge resizing worked before the aspect ratio lock (Bug 1583737) but it just added letterboxing instead of making the other dimension grow.
Comment 10•1 year ago
|
||
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Comment 11•11 months ago
|
||
Looks like ratio factor setting is broken on Gtk/Wayland. It calls gdk_window_constrain_size() directly from xdg_surface configure without info if window is upsized or downsized. gdk_window_constrain_size() jas internally hard coded increment to 1,1 so it always downsizes the width/height accordingly to scale ratio.
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Comment 12•11 months ago
|
||
Updated•11 months ago
|
Assignee | ||
Comment 13•11 months ago
|
||
- Create corner resizers larger to perform corner resize more comfortable
- Don't allow to grip West/North edges for resize on Wayland & windows with fixed aspect ratio. We can't resize such windows this way.
Depends on D191757
Comment 14•10 months ago
|
||
Pushed by stransky@redhat.com: https://hg.mozilla.org/integration/autoland/rev/8a99d177d36d [Wayland] Emulate gdk_window_begin_resize_drag() for edge resize r=emilio https://hg.mozilla.org/integration/autoland/rev/78ec252ec764 [Linux] Create wider corner resizers for nsWindow::CheckResizerEdge() and restrict edge resize on Wayland r=emilio
Comment 15•10 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8a99d177d36d
https://hg.mozilla.org/mozilla-central/rev/78ec252ec764
Updated•10 months ago
|
Reporter | ||
Comment 16•9 months ago
|
||
I can't seem to be able to force-open the browser with wayland window protocol using the following method:
- Open the folder of the firefox build on Ubuntu 22.
- Right-click / Open in Terminal
- type in terminal:
export MOZ_ENABLE_WAYLAND=1
and press ENTER - Type in:
./firefox
Expected: Firefox is launched using wayland window protocol.
Actual: Firefox is launched using x11 window protocol.
This being said, I cannot verify this fix because I do not have a working method to open the browser with wayland.
Martin, can you help me by showing me a method to force-open the browser with wayland window protocol?
Thank you!
Assignee | ||
Comment 17•9 months ago
•
|
||
(In reply to Daniel Bodea [:danibodea] from comment #16)
I can't seem to be able to force-open the browser with wayland window protocol using the following method:
- Open the folder of the firefox build on Ubuntu 22.
- Right-click / Open in Terminal
- type in terminal:
export MOZ_ENABLE_WAYLAND=1
and press ENTER- Type in:
./firefox
Expected: Firefox is launched using wayland window protocol.
Actual: Firefox is launched using x11 window protocol.This being said, I cannot verify this fix because I do not have a working method to open the browser with wayland.
Martin, can you help me by showing me a method to force-open the browser with wayland window protocol?
Thank you!
You're perhaps missing Wayland environment. Check if you have Wayland enabled, type on terminal:
env | grep WAYLAND
and you should get something like:
WAYLAND_DISPLAY=wayland-0
Reporter | ||
Comment 18•9 months ago
|
||
Thank you for the information!
I have managed to launch Firefox with Wayland window protocol.
The following behavior can be observed in Nightly v122.0a1 and Beta v121.0 (RC): The bottom and right margins can be grabbed to resize the PiP, but the top and left margins still can't as the cursor does not even change into "its resize form".
Furthermore, the corner-grabbing area may be a little too large because if the user resizes PiP to its smallest size, he will not be able to grab the small margin, only the corners.
As a conclusion, this issue appears to be partially fixed. Martin, what course of action do you recommend for advancing our consideration of this issue?
Thank you!
Assignee | ||
Comment 19•9 months ago
|
||
(In reply to Daniel Bodea [:danibodea] from comment #18)
As a conclusion, this issue appears to be partially fixed. Martin, what course of action do you recommend for advancing our consideration of this issue?
We don't have any other fix available.
Reporter | ||
Comment 20•9 months ago
|
||
Do you suggest we reopen this bug or close it and log another? Thanks!
Assignee | ||
Comment 21•9 months ago
|
||
(In reply to Daniel Bodea [:danibodea] from comment #20)
Do you suggest we reopen this bug or close it and log another? Thanks!
Please file a new one.
Reporter | ||
Updated•8 months ago
|
Reporter | ||
Comment 22•8 months ago
|
||
I have logged the remaining issues from this report into bug 1873220. This one will be closed. Thank you.
Description
•