aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIvan Molodetskikh <yalterz@gmail.com>2025-08-18 09:48:54 +0300
committerIvan Molodetskikh <yalterz@gmail.com>2025-08-18 09:49:00 +0300
commit85d42db05d964644e3fa82e2f57172b8cae936ce (patch)
tree4861946b32109b66bfe1bb437f01a7c4eb55e4d0
parentd6db202a0391205532a68a6680c40849c6856a85 (diff)
downloadniri-85d42db05d964644e3fa82e2f57172b8cae936ce.tar.gz
niri-85d42db05d964644e3fa82e2f57172b8cae936ce.tar.bz2
niri-85d42db05d964644e3fa82e2f57172b8cae936ce.zip
wiki/FAQ: Mention blur
-rw-r--r--docs/wiki/FAQ.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/wiki/FAQ.md b/docs/wiki/FAQ.md
index 1d7b1de7..41924ec8 100644
--- a/docs/wiki/FAQ.md
+++ b/docs/wiki/FAQ.md
@@ -63,3 +63,10 @@ All in all, the situation works out in favor of avoiding Xwayland integration.
Also, in the next release niri will have seamless built-in xwayland-satellite integration, that will solve the big rough edge of having to set it up manually.
Besides, I wouldn't be too surprised if, down the road, xwayland-satellite becomes the standard way of integrating Xwayland into new compositors, since it takes on the bulk of the annoying work, and isolates the compositor from misbehaving clients.
+
+### Can I enable blur behind semitransparent windows?
+
+Not yet, follow/upvote [this issue](https://github.com/YaLTeR/niri/issues/54).
+
+There's also [a PR](https://github.com/YaLTeR/niri/pull/1634) adding blur to niri which you can build and run manually.
+Keep in mind that it's an experimental implementation that may have problems and performance concerns.