Application blur is automatically off when fullscreen, BUT only in Wayland

[FelixFourcolor]

In X11, it makes no difference to application blur when the app goes fullscreen.
Screencast from 2024-07-15 15-31-25.webm

(This applies to all apps when you're in an X11 session, or XWayland apps when you're in Wayland).

In Wayland, application blur is automatically off when the app goes fullscreen.
Screencast from 2024-07-15 15-32-00.webm

I don't know whether this is intended -- I don't see it documented anywhere -- but it's a genius feature! I love it when coding or watching videos or reading documents, going fullscreen is like turning on focus mode.

If this is not intended, please don't fix it, I love it very much. And I'd love it if you implemented it for X11 apps as well.

[aunetx]

Hello, does this still happen with https://extensions.gnome.org/extension/1873/disable-unredirect-fullscreen-windows/ enabled? If not, then it is not intended! I implemented "opaque focused window" for a similar behaviour recently (so that every focused window is opaque, which helps focusing on it a lot); maybe I can extend that have "opaque maximized window" too!

[FelixFourcolor]

That extension makes no difference.

maybe I can extend that have "opaque maximized window" too!

Nice, thanks in advance! (I'd prefer "opaque fullscreen window" though, just like how it currently works in Wayland. But either is fine.)

[aunetx]

I tried working on this in #640, but to be honest you should not use it because it is only half-baked, does not work correctly and has no advantage in terms of performances (blur is not deactivated, but only hidden).

I will try to implement it in a real way later, but first I need to change some things internally (it will probably be done at the same time as the rewrite of #325, so not too soon). Sorry about that

[FelixFourcolor]

Don't worry about it. I open this issue mostly so that you won't discover this behavior yourself and "fix" it, because my workflow really depends on it. It would be nice if it worked in X11 as well, but it's not a big deal.

[Aunali321]

@aunetx I used your gnome 48 fork of the extension and the bug was fixed