You could test this with a call to xprop to set that property on the root window. Given the "just do one thing well" nature of 9wm, and that xprop in your .xsession could set the property, I think doing that is in keeping with the spirit of the thing.
xprop -root -f _NET_SUPPORTED 8s -set _NET_SUPPORTED '' On Fri, Jan 8, 2016 at 8:11 PM Jacob Adams <tookm...@gmail.com> wrote: > On 01/03/2016 10:38 PM, Neale Pickett wrote: > > 9wm is not an EWMH compliant window manager, sorry. > > Ok. I was just legitimately surprised at this because both chromium and > virt-manager handle full screen requests and just fill the space they > are given which is super nice. > > I don't actually expect the applications to go fullscreen but I was just > surprised that it completely broke these two. > > I've done some research into this Extended Window Manager Hints thing > and I understand not wanting to support it as it looks to be very > complicated and would require supporting window operations are against > the whole idea of 9wm. > > However, in the interest of not breaking applications, would sending a > blank _NET_SUPPORTED work? That might allow some of these applications > to try and fall back on other methods of going fullscreen and prevent > them from becoming unusable. This is just based on what I've read here > and may not reflect the reality of how this spec is used: > http://standards.freedesktop.org/wm-spec/wm-spec-latest.html > > -- > Jacob Adams > GPG Key: AF6B 1C26 E2D0 A988 432B 94F4 24C0 2B85 B59F E5A9 > >
