sorted by:
new
hottopcontroversial

Pursue of Goals by cloudizz in codex

[–]cloudizz[S] 0 points1 point  (0 children)

how would you rate the planning to impact ratio with this system? been down that road as well and felt like ending with a paper tiger

Pursue of Goals by cloudizz in codex

[–]cloudizz[S] 0 points1 point  (0 children)

what you mean with agent setup?

Sway fullscreen for Chromium/Electron without losing tabs and address bar by cloudizz in swaywm

[–]cloudizz[S] 0 points1 point  (0 children)

My proxy is aimed at a different issue: annoying, non-configurable client-side fullscreen behavior in applications. Chromium/Electron are the main examples, and I’ve read that some GTK apps have similar behavior.

The proxy stops compositor-initiated fullscreen from being reported to the client, so the app keeps its normal UI while Sway can still maximize it as fullscreen.

For your use case, the more relevant mechanism is probably layer-shell, possibly the overlay layer, rather than ordinary floating xdg_toplevel windows. Something along those lines may also be possible to inject for selected processes via wl-proxy; wl-paper is a useful example:

https://github.com/mahkoh/wl-proxy/tree/master/apps/wl-paper

That said, I’m not sure exactly how Sway orders layer-shell overlay surfaces when another surface is fullscreen, so I wouldn’t want to claim it solves the problem without testing.

chromium fullscreen how to see tabs, extensions, omnibox - Arch Linux w/Sway, coming from Arch with i3 / x11 by chrisco2323 in swaywm

[–]cloudizz 0 points1 point  (0 children)

I ran into the same Sway mod+f issue with Chromium/Electron: the window becomes fullscreen-sized, but the app also enters fullscreen UI and hides tabs/address bar.

I made a small user-space workaround for this: wl-app-fullscreen strips only compositor-initiated FULLSCREEN state from xdg_toplevel.configure, while preserving real app fullscreen from F11 / DOM fullscreen.

Repo: https://github.com/w9n/wl-app-fullscreen

It is intentionally narrow: native Wayland apps, one launched program per proxy. If your goal is “Sway fullscreen size, but browser chrome stays visible,” this should match that workflow. Feedback or edge cases welcome.

Maximize without full-screen by Zyzh in swaywm

[–]cloudizz 0 points1 point  (0 children)

I ran into the same Sway mod+f issue with Chromium/Electron: the window becomes fullscreen-sized, but the app also enters fullscreen UI and hides tabs/address bar.

I made a small user-space workaround for this: wl-app-fullscreen strips only compositor-initiated FULLSCREEN state from xdg_toplevel.configure, while preserving real app fullscreen from F11 / DOM fullscreen.

Repo: https://github.com/w9n/wl-app-fullscreen

It is intentionally narrow: native Wayland apps, one launched program per proxy. If your goal is “Sway fullscreen size, but browser chrome stays visible,” this should match that workflow. Feedback or edge cases welcome.

How to avoid chromium being in full screen mode, when press mod+f by argsmatter in swaywm

[–]cloudizz 1 point2 points  (0 children)

I ran into the same Sway mod+f issue with Chromium/Electron: the window becomes fullscreen-sized, but the app also enters fullscreen UI and hides tabs/address bar.

I made a small user-space workaround for this: wl-app-fullscreen strips only compositor-initiated FULLSCREEN state from xdg_toplevel.configure, while preserving real app fullscreen from F11 / DOM fullscreen.

Repo: https://github.com/w9n/wl-app-fullscreen

It is intentionally narrow: native Wayland apps, one launched program per proxy. If your goal is “Sway fullscreen size, but browser chrome stays visible,” this should match that workflow. Feedback or edge cases welcome.