Open Bug 2078254 Opened 2 days ago Updated 12 hours ago

[Wayland][KDE-PIP] PiP windows cannot be moved after being double clicked

Categories

(Core :: Widget: Gtk, defect)

Firefox 157
defect

Tracking

()

UNCONFIRMED

People

(Reporter: LingM, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:157.0) Gecko/20100101 Firefox/157.0

Steps to reproduce

Tested in a Plasma 6.7 Wayland session.
0. Set KWIN_WAYLAND_SUPPORT_XX_PIP_V1=1 in /etc/environment to enable the xx-pip-v1 protocol.

  1. Start a video and open it in PiP mode.
  2. Double click the PiP window.

Actual results

The PiP window can no longer be moved around.

Expected results

Usually double clicking the PiP window is supposed to turn on fullscreen mode. In a sense that appears to be exactly what happens. However, instead of filling the entire screen the window just refuses to be moved.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

This is KDE specific Wayland extension.

Blocks: wayland-kde
Summary: [Wayland] PiP windows cannot be moved after being double clicked → [Wayland][KDE-PIP] PiP windows cannot be moved after being double clicked
Flags: needinfo?(stransky)

Looks nsWindow::MakeFullScreen() it not even called for the xx-pip window.

Hm, so

nsWindow::MakeFullScreen aFullScreen 1
OnWindowStateEvent()
Fullscreen
AppWindow::FullscreenChanged(1) state 1

so it's called and Gtk tells us we're in fullscreen but we actually are not (at least for the PIP).

Perhaps the best solution may be to just disable the fullscreen for xx-pip for now as we'd need to plumb xdg-toplevel events to gtk events.

Flags: needinfo?(stransky)
Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.