On Sat, Aug 25, 2018 at 11:20:37AM +0200, Stefan Blachmann wrote: > On 8/24/18, hw <[email protected]> wrote: > > > But that doesn??t work either, the windows are placed on top of each > > other again. With !UsePPosition alone, I get the windows placed as I > > want it, but it means Firefox is moving them rather than that fvwm > > places them. > > Yes, FF creates its windows with the size given in sessionrestore.js, > *then* moves, retitles and paints them. ^^^^^^^^
If that is the case, styles may not match the newly created windows. Could you provide some list of events that are generated in relation to the output of bugopts explainwindowplacement ? Maybe we could "preview" events that rename a window that is just being created. But I'd need some kind of test case for that. Ideally just a simple application that does the same thing that Firefox does in a reliable way. > On 8/25/18, Dominik Vogt <[email protected]> wrote: > > It actually is possible. Sort of. If the application claims that > > a requested position is "user specified" instead of "program > > specified", the window manager has no way of knowing that the user > > did not ask for it. Nowadays many programs abuse this hint to > > override the window manager - in clear violation of the > > communication rules set in the ICCCM2 standard. > > Well, Firefox is correct if it says "user specified" position, as > *you* probably were the one who originally specified it by moving the > window. No. The windows may have been placed automatically by the window manager, and still the application claims the position is "user specified". It's just a lame excuse that I've read many times. Unless the user explicitly selected an option "restore window position" or similar, the position is program specified. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
