Bug 514365 - [Feature request]: Auto-disable night color for full screen apps
Summary: [Feature request]: Auto-disable night color for full screen apps
Status: RESOLVED INTENTIONAL
Alias: None
Product: kwin
Classification: Plasma
Component: night color (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-09 11:09 UTC by Vivek
Modified: 2026-01-09 12:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vivek 2026-01-09 11:09:09 UTC
SUMMARY
Requesting a feature to auto-disable night colour when a fullscreen application is using the screen; such as movies, games, slideshows. Currently I have to manually suspend night colour and unsuspend after the fullscreen app has closed. 

F.lux had a similar feature to auto-disable whenever an application enters the full screen state, which was very convenient as these full screen apps are often colour sensitive and best viewed in their original intended form.

Such a feature would automate the manual switching routine and save users a small slice of time as well as many clicks over time.

STEPS TO REPRODUCE
1. Open an application in its full screen state, such as MPV video file or a video game

OBSERVED RESULT
Night colour correction/overlay persists.

EXPECTED RESULT
It would be helpful to have an option/toggle where night colour temporarily disables itself when a software is being displayed in fullscreen mode.

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora Linux 42
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.9.3
Comment 1 David Edmundson 2026-01-09 12:33:17 UTC
All these "when X do Y" options make life very difficult and don't scale very well. There's infinite possibilities and we just clutter our codebase and UX trying to support them all.  

Our best option is to ensure scripting is available and exposed for this sort of thing.