Sway and client side decorations January 27, 2018 on Drew DeVault's blog

You may have recently seen an article from GNOME on the subject of client side decorations (CSD) titled Introducing the CSD Initiative. It states some invalid assumptions which I want to clarify, and I want to tell you Sway’s stance on the subject. I also speak for the rest of the projects involved in wlroots on this matter, including Way Cooler, waymonad, and bspwc.

The subject of which party is responsible for window decorations on Wayland (the client or the server) has been a subject of much debate. I want to clarify that though GNOME may imply that a consensus has been reached, this is not the case. CSD have real problems that have long been waved away by its supporters:

We are willing to cooperate on a compromise, but GNOME does not want to entertain the discussion and would rather push disingenuous propaganda for their cause. The topic of the #wayland channel on Freenode includes the statement “Please do not argue about server-side vs. client-side decorations. It’s settled and won’t change.” I have been banned from this channel for over a year because I persistently called for compromise.

GNOME’s statement that “[server-side decorations] do not (and will never) work on Wayland” is false. KDE and Sway have long agreed on the importance of these problems and have worked together on a solution. We have developed and implemented a Wayland protocol extension which allows the compositor and client to negotiate what kind of decorations each wishes to use. KDE, Sway, Way Cooler, waymonad, and bspwc are all committed to supporting server-side decorations on our compositors.


See also: Martin Flöser of KDE responds to GNOME’s article

Have a comment on one of my posts? Start a discussion in my public inbox by sending an email to ~sircmpwn/public-inbox@lists.sr.ht [mailing list etiquette]

Articles from blogs I read Generated by openring

Share your feedback about developing with Go

Help shape the future of Go by sharing your thoughts via the Go Developer Survey

via The Go Blog January 18, 2023

Status update, January 2023

Hi all! This month’s status update will be lighter than usual: I’ve been on leave for a while at the end of December. To make up for this, I have some big news: we’ve released Sway 1.8! This brings a whole lot of improvements from wlroots 0.16, as well as som…

via emersion January 16, 2023

SourceHut will (not) blacklist the Go module mirror

Update 2023-01-31: Russ Cox of the Go team reached out to us to address this problem. After some discussion, an acceptable plan was worked out. The Go team is working on deploying an update to the “go” tool to add a -reuse flag, which should substantially re…

via Blogs on Sourcehut January 9, 2023