Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox 63.0.3 not remembering screen position

  • 5 replies
  • 2 have this problem
  • 2 views
  • Last reply by jsamcr

jsamcr
jsamcr
more options

I am running Debian Jessie (i386) and Debian Stretch (amd64). I have Mozilla Firefox 63.0.3 installed on both systems and this is not a Firefox-ESR issue.

I have checked the values for screenX and screenY in the xulstore.json file and they seem to be saved correctly, corresponding to the Firefox window position. But when I close Firefox and re-open Firefox the window defaults to the top left of the screen. I have deleted the xulstore.json file, several times, but this does not seem to fix the problem. It would appear to me, that something is preventing Firefox from using the screenX and screenY position values. All other values and settings in xylstore.json appear to work as they should.

I copied the .mozilla folder to a new location and created a new profile. This did not fix the problem/ I have also tried resetting Firefox. This also did not fix the problem.

This is NOT a game changer and will not cause me stop using Firefox, but it would be nice to have a fix for this issue. As a side note, I also use Chrome, and it remembers the screen position as desired.

Feedback would be appreciated. And if additional information is needed please contact me.

Thanks for supporting a great product.

I am running Debian Jessie (i386) and Debian Stretch (amd64). I have Mozilla Firefox 63.0.3 installed on both systems and this is not a Firefox-ESR issue. I have checked the values for screenX and screenY in the xulstore.json file and they seem to be saved correctly, corresponding to the Firefox window position. But when I close Firefox and re-open Firefox the window defaults to the top left of the screen. I have deleted the xulstore.json file, several times, but this does not seem to fix the problem. It would appear to me, that something is preventing Firefox from using the screenX and screenY position values. All other values and settings in xylstore.json appear to work as they should. I copied the .mozilla folder to a new location and created a new profile. This did not fix the problem/ I have also tried resetting Firefox. This also did not fix the problem. This is NOT a game changer and will not cause me stop using Firefox, but it would be nice to have a fix for this issue. As a side note, I also use Chrome, and it remembers the screen position as desired. Feedback would be appreciated. And if additional information is needed please contact me. Thanks for supporting a great product.

All Replies (5)

jsamcr
jsamcr Question owner
more options

To anyone reading this post, please excuse my typing errors.

jsamcr
jsamcr Question owner
more options

I am beginning to think this is totally controlled by the Linux window manager. Unless there is some kind of Firefox command line option to control the x,y position on startup I am probably stuck with what I have. Still, it is interesting the the Chrome browser remembers its last position between sessions.

WestEnd
WestEnd
more options

So if this was a fresh install of firefox does it do it as well?

jsamcr
jsamcr Question owner
more options

WestEnd said

So if this was a fresh install of firefox does it do it as well?

I have done everything recommended in other post. I have deleted my profile, deleted the xulstore.json, have downloaded a new copy of Firefox, etc.

I am running Firefox from within my /home directory so it is NOT actually installed, per se.

The values for screenX and screenY, in xulstore.json, seem to coincide with the position of Firefox whenever I close Firefox. But they don't seem to be used the text time I open Firefox .

jsamcr
jsamcr Question owner
more options

Upon further investigation I find that Firefox-ESR performs in exactly the same way. Maybe I am expecting something it to work differently than in the default manner.