aboutsummaryrefslogtreecommitdiff
path: root/docs/wiki/FAQ.md
diff options
context:
space:
mode:
authorIvan Molodetskikh <yalterz@gmail.com>2025-08-27 14:20:22 +0300
committerIvan Molodetskikh <yalterz@gmail.com>2025-08-29 11:54:25 +0300
commitbf472970c6b84b02d51a195b322dfd741c586e9e (patch)
treeffe25c012a7d842d27ad0e593b1f2b3039af8b65 /docs/wiki/FAQ.md
parent082d0581b76e280b3d26f2f01695a291f6f55f39 (diff)
downloadniri-bf472970c6b84b02d51a195b322dfd741c586e9e.tar.gz
niri-bf472970c6b84b02d51a195b322dfd741c586e9e.tar.bz2
niri-bf472970c6b84b02d51a195b322dfd741c586e9e.zip
wiki: Update Xwayland-related info
Diffstat (limited to 'docs/wiki/FAQ.md')
-rw-r--r--docs/wiki/FAQ.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/wiki/FAQ.md b/docs/wiki/FAQ.md
index 4a9c9181..40bacfa4 100644
--- a/docs/wiki/FAQ.md
+++ b/docs/wiki/FAQ.md
@@ -60,9 +60,9 @@ A combination of factors:
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.
+<sup>Since: next release</sup> niri has seamless built-in xwayland-satellite integration that by and large works as well as built-in Xwayland in other compositors, solving the hurdle 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.
+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?