Path: utzoo!attcan!uunet!husc6!bloom-beacon!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Adding WM_CHILD (or xprop, xplaces, etc.)
Message-ID: <19880705124140.5.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 5 Jul 88 12:41:00 GMT
References: <8807020445.AA09888@EXPO.LCS.MIT.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 5

The current thinking in the window manager group is that the WM_STATE
property (described in the R2 ICCCM) is sufficient.  Window managers
should place a WM_STATE property on the application window.  Clients
like xprop should look down the tree for a window with WM_STATE, and
fall back to using the top-level window if no window has WM_STATE.