Bug 504639

Summary:	Add a window rule filter for fullscreen windows
Product:	[Applications] systemsettings	Reporter:	internetenjoyer
Component:	kcm_kwinrules	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	isma.af, kdedev, nate, plasma-bugs-null
Priority:	NOR
Version First Reported In:	6.3.5
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description internetenjoyer 2025-05-21 21:51:45 UTC

SUMMARY:
when creating a window rule (eg. with alt+f3, "more options" -> "configure special window settings"), i would appreciate a option to filter for fullscreen windows so a rule can apply to only fullscreen or non fullscreen versions of a window.

My usecase is probably very specific, but in order to archive a uniform look with my kvantum theme (which has transparency+blur), i have a transparency rule for my webbrowser and use darkreader to force my colorscheme on websites. however for movies/videos (which are usually viewed in fullscreen) the transparency is kinda ugly, so if my window rule would only make the browser transparent if not in fullscreen i would be very happy.


STEPS TO REPRODUCE
1. configure a window rule

OBSERVED RESULT
there is no way to target fullscreen windows :(

WISHED RESULT
an option to target only windows in fullscreen/not fullscreen

KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
sorry if this is not the place for this request, i thought with severity:wishlist i could file this report maybe

Comment 1 TraceyC 2025-05-22 22:17:59 UTC

I think this is worth considering.

Comment 2 internetenjoyer 2025-05-22 22:26:41 UTC

Here is an idea that expands the proposal (i have no idea if this is viable and i do understand that devs do this in their freetime feel free to reject it), but the dropdown for window types seems to target window types (suprise) and not window states (like fullscreen). Maybe a second list of window properties (just like those that can be configured) could be implemented, except for filtering purposes? This seems like a general solution that maybe could reuse some existing code and is not hyper-my-problem-specific? Again i do not have an estimate on how much work this would take and it is no dealbreaker at all but i would appreciate it very much.