https://bugs.kde.org/show_bug.cgi?id=452780
--- Comment #2 from Alberto Salvia Novella <es204904...@gmail.com> ---
They are independent. `NET_WM_BYPASS_COMPOSITOR` (aka the hint) is what the
window requests, and `blocksCompositing` (aka the property) is what kwin is
currently doing with it.
The hint is inmutable, where the property is mutable. Changing the property
doesn't affect the hint, and reading the property doesn't tell what the hint
could be.
Furthermore the hint has three settings (unset, true, false), where the
property has only two (true, false).
This is relevant because through the kwin api you can't really tell what the
windows actually requests. You can only guess, for example, by storing the
initial status of composition for a window. But even then it has corner cases
where you can't really guess.
The rest of properties are unrelated. They are either signals or refer to
different objects. For example for Firefox I get:
resourceClass = firefox
blocksCompositing = false
isBlockingCompositing = undefined
setBlockingCompositing = undefined
blockingCompositingChanged = function() { [native code] }
--
You are receiving this mail because:
You are watching all bug changes.
