> The "specification" isn't entirely explicit on this point. On the one
> hand, it says "The Window Manager MUST set _NET_FRAME_EXTENTS" (at
> https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472552416
> ) but then the _NET_REQUEST_FRAME_EXTENTS action "To retrieve such an
> estimate [about an unmapped window], the Client MUST send a
> _NET_REQUEST_FRAME_EXTENTS message to the root window. The Window
> Manager MUST respond by estimating the prospective frame extents and
> setting the window's _NET_FRAME_EXTENTS property accordingly. "
> (https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472648576)
> is rather superfluous...
I think setting it unconditionally is good enough here: we basically
"answer" regardless if the client asks the question, and we may even
answer before it asks the question.
But I'm not really familiar how this "setting values used as an indirect
way to send messages" is usually handled in the wm-spec, so maybe my
assumptions of what is "clear from context" are wrong.
> Maybe they mean that _NET_FRAME_EXTENTS is meant to be set only *after*
> a window is mapped,
No, I think it's clear that it needs to be set before the window is
mapped because it's for the case where the application wants to know
those things before the window is mapped.
> But then they might have mentioned that a bit more clearly.
Prose, you know...
Stefan
