Oh, it's Picture-in-Picture, not Python's Pip.
post
Does the Wayland PiP work with any application window? Oh the linked issue https://invent.kde.org/plasma/kwin/-/merge_requests/10175 talks about Firefox. Is this only about Firefox? I'm confused.
After extended testing, KWin’s support for the Wayland picture-in-picture (PiP) protocol has been deemed stable enough, and turned on by default! (Vlad Zahorodnii, kwin MR #10175)
Yeeeeeeessssssssss
Edit:
In-progress downloads in Firefox that produce a nice native Plasma notification via Plasma Browser Integration can now be paused and resumed from that notification. (Simon Hürlimann, plasma-browser-integration MR #207)
Yeeeeeeeeeeeeeeeessssssssssss
This release of plasma (6.8 and 6.8.1) has been buggy for me. I hope it’s not because they went hard on vibe-coding. Use AI, guys, but please not blindly. I’m having random freezing, issues with suspending the pc, memory issues and many others that for the first time in like 5 years, I’ve considered moving to gnome or something. This is how bad it has gotten.
I’m in the process of constructing several bug reports for them. They’re going to hate me. lol
Does the Wayland PiP work with any application window? Oh the linked issue https://invent.kde.org/plasma/kwin/-/merge_requests/10175 talks about Firefox. Is this only about Firefox? I’m confused.
Firefox has a PiP mode for videos, not any generic window
I know. My question was, is this new PiP mode in Plasma a generic Wayland feature, or is it about the Firefox's own PiP mode.
is this new PiP mode in Plasma a generic Wayland feature
"the Wayland picture-in-picture (PiP) protocol" So yes, of course.
That's what I assumed too. But the linked issue talks just about Firefox.
I understood it as blacklisting support for the protocol because Firefox's implementation was too buggy.
Oh now I understand! Firefox was the blocker to finally release a generic Wayland implementation! Man sometimes I have the feeling I can't think. Thanks for your patience.
all 2 comments