https://bugs.kde.org/show_bug.cgi?id=527752
Bug ID: 527752
Summary: PIP windows need to follow window rules
Classification: Plasma
Product: kwin
Version First git master
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Note: Bug #511384 from a year ago (Oct 2025) had a similar "follow window
rules" for xdg-pip request, that was "RESOLVED/INTENTIONAL" with Vlad's comment
that it was an experimental feature, and that system settings had an option to
control where it was placed. But a year later, it (xx-pip anyway) is
default-enabled now, and if the PIP options in system settings remain I can't
find them, so... keeping "above" and the other usually expected PIP defaults as
normal behavior but allowing window rules to override for people like me that
use PIP differently than expected would sure be nice! =:^)
Git master kwin/plasma/frameworks via the gentoo/kde overlay ebuilds for that
purpose, updated yesterday, so what I'm now running has October 21's commit
889db019b596040bf79ad06a3f1b548fe20ccb65 Enable pip by default.
The trouble is I don't use PIP in the usual way so its default settings are
broken for me, and based on the older bug and current behavior, the window
rules that could potentially fix that are deliberately disabled for PIP
windows.
My use-case: I'm multi-monitor (three 50-inch 4k TVs as monitors) and normally
want my firefox PIP window fullscreen resolution/position (but not in
fullscreen mode as I don't like firefox's PIP-window fullscreen mode behavior)
on a dedicated monitor, but with the PIP set to the BELOW layer so I can use
that monitor as an "overflow" monitor too and have any other windows I put
there on top of the full-screen PIP window -- think "fullscreen desktop video
player" with anything else going over top, which is where I got the original
concept, except as a window that can be resized from that default full-screen,
moved elsewhere, sometimes temporarily have the "below" turned off and possibly
"above" set...
And I actually had that working as desired via window rules until kwin broke it
by activating xx-pip-v1 with the above commit, because kwin apparently ignores
window rules for xx-pip.
Meanwhile, I'm not (yet) sure if the KWIN_WAYLAND_SUPPORT_XX_PIP_V1 I see
mentioned in several PIP bugs can still be used to turn it OFF now that it's
on-by-default, or if I need to try local hack-patching back to unbroken.
(While I'm not a coder and can't new-code, I've found I can quite often do
simple hack-patching of existing code, particularly when pointed directly at
the code in question by commit logs.)
Also, I've seen various similar environmental-var controlled settings mentioned
a number of times, but find I usually know nothing about them until I find them
mentioned in a bug or something. Is there a list (ideally a maintained list,
not just a snapshot in time) of such settings somewhere? Based on the mentions
I've happened across I'm sure I'd find others useful too if I knew where to
look for them.
--
You are receiving this mail because:
You are watching all bug changes.
