6 ms·

I think the Window Controls Overlay[1] approach that Microsoft is proposing for Progressive Web Apps on windows seems like an interesting compromise to solve so

I think the Window Controls Overlay[1] approach that Microsoft is proposing for Progressive Web Apps on windows seems like an interesting compromise to solve some of the issues you raise. Specifically that the client code is allowed to customize _most_ of the headerbar, with the exception of an area reserved for the window controls (minimize, maximize, close, etc). It seems like this approach would still support alternate or tiling window managers as they could omit or provide custom window controls. [1] https://blogs.windows.com/msedgedev/2022/09/27/closing-pixel-gap-native-web-window-controls-overlay/ https://blogs.windows.com/msedgedev/2022/09/27/closing-pixel...

chrismorgan 4y ago
Very nice! I hadn’t heard of that. I’m amused at how exactly it matches my mullings of how I’d do it in a web tech stack (manifest field, env() variables, navigator property with events, CSS property to indicate draggable area), with only a couple of missing pieces: the ability to match the appearance of the native controls and native conventions (e.g. `background: env(titlebar-area-background); color: env(titlebar-area-color); text-align: env(titlebar-area-align)`, though for best results you’d still need a little more here and there). I’ve thought of trying to design something like this for Wayland server-side decorations or at least making a better replacement for libdecor, but it wouldn’t help me personally and it’s clear that GNOME isn’t having a bar of the entire approach, so I sadly just don’t think it’s worth the effort.