https://bugs.kde.org/show_bug.cgi?id=512157
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM CC| |[email protected] Status|REPORTED |RESOLVED --- Comment #1 from Zamundaaa <[email protected]> --- (In reply to ctj9512 from comment #0) > A similar issue was reported on > https://issues.chromium.org/issues/446254087, however I believe this is more > likely to be a kwin bug, since the compositor is responsible for night light > colors, and is applied after any application's output is rendered. Our night light implementation is a bit more complicated than that. The short summary is that KWin 1. adjusts the white point on the output and 2. applies an additional transformation from that changed white point to the actual screen Step 2 always happens in the compositor, and specifically on the fully composited image for the display, so nothing app-specific. Step 1 however can be applied in either the compositor or in the app. If the app has a different white point, KWin transforms from that to the screen, but if it matches, it doesn't do anything. In Chrome's case, it adjusts colors to the changed white point itself, so KWin doesn't do anything with Chrome's window. Please report this to Google. -- You are receiving this mail because: You are watching all bug changes.
