This is a long story... sessionrestore.js some day years ago got a regression and no longer did check for out-of-bounds coordinates indicating windows being placed on other virtual screens, i.e. it placed windows way off-screen, at crazy coordinates like -40000, 30000 etc.
I reported this to Mozilla and asked this to be fixed. This resulted in the "fix" that all coordinates were clipped to the current virtual screen size, piling the restored FF windows in the current virtual screen. I was annoyed and looked into that. session[re]store.js is a *horrible* mess of code, and to understand its workings, I just disabled the screen bounds check where sessionrestore creates the windows from the data in the sessionrestore.js file and wrote a script that just corrects the coordinates in the sessionrestore.js file, so that Firefox restores as it should. So I could just run the firepox script, after that run FF, it should restore the windows where they originally were. The script might be outdated for new FF versions, as the sessionrestore code was changed again in the meantime, introducing again random placement of restored windows. But reading it might give you some insight of the workings in the sessionrestore.js files. It is on github together with a small intro, here: https://github.com/kernschmelze/firepox On 8/23/18, hw <h...@adminart.net> wrote: > Hi! > > Fvwms manpage says: > > > Placement policy options and window stacking > !UsePPosition instructs fvwm to ignore the program > specified position (PPosition hint) when adding new > windows. Using PPosition is required for some > applications, but if you do not have one of those it's a > real headache. Many programs set PPosition to something > obnoxious like 0,0 (upper left corner). Note: > !UsePPosition is equivalent to the deprecated option > !UsePPosition > > > Is "!UsePPosition" deprecated? > > I'm trying to figure out how to make it so that when Firefox opens three > windows when it's restoring the last session when it's started, these > windows are not put on top of each other (at the top left side of the > display) but placed according to the placement policy. > > Some years ago, I had found out that I need to use "FixedPPosition" for > Seamonkey to prevent it from creating windows at unreachable places, > i. e. way off screen on desktop pages that didn't even exist. So I´m > using this option for Firefox now. > > What option(s) can I use to prevent windows being created by Firestorm > at unreachable places and yet have them placed according to the > placement policy? > >
