Bug 467974

Summary: Cant record PiP windows in Wayland
Product: [Applications] Spectacle Reporter: Henning <amanita+KDEBUGS>
Component: GeneralAssignee: Boudhayan Gupta <me>
Status: RESOLVED FIXED    
Severity: normal CC: kde, nate
Priority: NOR    
Version: 22.12.3   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In: 23.04

Description Henning 2023-03-30 14:32:48 UTC 
SUMMARY
***
Spectacle cant record PiP windows in Wayland. In general the PiP windows go in front of every other layer, even in front of the appmenu (another bug I already filed)


STEPS TO REPRODUCE
1. Open a PiP video in firefox or so
2. Try to screenshot something
3. try to open the appmenu if the pip covers that area

OBSERVED RESULT
PiP is in front of everything and also not captured by spectacle

EXPECTED RESULT
spectacle, taskbar, menu and more plasma things should be in the top layer

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Comment 1 Nate Graham 2023-04-04 18:22:31 UTC 
Is Firefox in native Wayland mode or XWayland mode? I ask because in native Wayland mode, its PIP window doesn't open as a PIP window; it just opens as a normal window and you're responsible for making it be on top. This is currently a Wayland limitation that's being worked on. SCreenshotting that window works for me on Wayland with the upcoming Spectacle 23.04.
Comment 2 Henning 2023-04-04 22:00:09 UTC 
Interesting. Firefoxes handling of Wayland is weird. Yes on wayland it stays in background.

But putting it in the foreground produces the same effect, that spectacle doesnt run at the top layer. Weirdly I can screenshow my taskbar, but I forgot the Wayland details, these are different layers.

So spectacle doesnt record the top layer, this is the problem and it occurs on xwayland and wayland.
Comment 3 Nate Graham 2023-04-05 14:32:29 UTC 
Ok, thanks. That means the issue has been fixed in the upcoming 23.04 release already!