Didier Verna <verna(a)inf.enst.fr&gt; writes: IconicState - The client's top-level window is iconic (whatever that means for this window manager). The client can assume that its top-level window is not viewable, its icon_window (if any) will be viewable and, failing that, its icon_pixmap (if any) or its WM_ICON_NAME will be displayed. Note "what ever that means", seems like the windowmanager is fairly free. "if any", icon window does not need to exist. (I think it does in window maker). The problem is more in the "can assume [limited set of options] is viewable/displayed" part. However I think that can safely be ignored given the fact that this text is followed by In fact, the window manager may implement states with semantics other than those described above. For example, a window manager might implement a concept of an "inactive" state in which an infrequently used client's window would be represented as a string in a menu. But this state is invisible to the client, which would see itself merely as being in the Iconic state. I think the "only title bar visible" state is more or less what the ICCCM describes here with as "inactive". So I still think it would be better if window maker implemented this as "iconic". Jan