[Implemented] Window Position

[MozillaUser233]

I'm stuck on PMx64 20.3.

Moonchild, is there any way you and your team would be able to reimplement into palemoon, what mozilla removed or have done?

Explanation:

Supposedly, Firefox22 and prior what ever version this would be in palemoon, closing palemoon @ what ever window position the browser was, then starting or restarting, palemoon 20.3 starts up where it left off, as in window position.

The latest release of PM, and FF, this is no longer working. Latest PM,FF, starts up with a window position reset.

Any ideas or clues?

If any other explanation is needed, just ask, I will try to re explain the problem.

[Moonchild]

I'm not entirely sure what the problem would be - I use Pale Moon on a daily basis myself, and it perfectly remembers all my window positions (as it should). It remembers the exact window position and size I was using last time I used the browser, and I don't think this code has changed in the underlying Mozilla code base.

Please explain in detail what problem you are encountering?

[MozillaUser233]

I'm not entirely sure what the problem would be - I use Pale Moon on a daily basis myself, and it perfectly remembers all my window positions (as it should). It remembers the exact window position and size I was using last time I used the browser, and I don't think this code has changed in the underlying Mozilla code base.

Please explain in detail what problem you are encountering?

I use all-in-one sidebar addon, there is a sidebar switch. On 20.3, I leave PM, set slightly off screen, so when I move my mouse to the left of the screen, my mouse falls onto the sidebar switch and I can open the sidebar. The latest PM/FF, does a window position reset, so every time I start either one of the latest of PM or FF, I have to manually move the browser slightly off screen. 20.3 holds this in memory some how, the latest does not.

I am sure, I can make a video of it if you would like to see the different behaviors, if really needed.

Same as prior, if more detail is needed, will try and provide.

Tested with brand new profiles and old ones, same results as explained.

[Blacklab]

Is OP Pitroad's "AIOS issues" topic on mozillaZine describing the same problem?

In any case one of the mozillaZine replies isn't exactly good news for any AIOS related problems:

Don't expect any bugfixes: http://firefox.exxile.net/forum_new/vie ... 6&t=174408

[MozillaUser233]

Is OP Pitroad's "AIOS issues" topic on mozillaZine describing the same problem?

If so one of the mozillaZine replies isn't exactly good news:

Don't expect any bugfixes: http://firefox.exxile.net/forum_new/vie ... 6&t=174408

Nope, I disabled AIOS, move the latest PM/FF browser off screen just a little, close, open, gets pushed back "on screen" not a little bit off screen.

Here is another person having the same problem.

https://support.mozilla.org/en-US/questions/962982

[Moonchild]

Ah, okay, you left out quite an important piece of information in your original post.

It is normal behavior for an application to position itself in the visible area of the screen if a previously saved position is out of bounds. If you don't do this, then your entire application window may end up off-screen, and as a result completely invisible.

Just an example:
Say, you have a dual monitor setup, and extended your desktop area over both monitors. You move the browser to the second monitor, and close it there. You then disable or disconnect the second monitor and launch the browser. What would happen? It would open completely off-screen, with no way to access the application.

I'd say that the previous behavior (saving out of bounds window positions and restoring to them) was a bug that got fixed.

[MozillaUser233]

Ah, okay, you left out quite an important piece of information in your original post.

It is normal behavior for an application to position itself in the visible area of the screen if a previously saved position is out of bounds. If you don't do this, then your entire application window may end up off-screen, and as a result completely invisible.

Just an example:
Say, you have a dual monitor setup, and extended your desktop area over both monitors. You move the browser to the second monitor, and close it there. You then disable or disconnect the second monitor and launch the browser. What would happen? It would open completely off-screen, with no way to access the application.

I'd say that the previous behavior (saving out of bounds window positions and restoring to them) was a bug that got fixed.

Would you be able to confirm this was a bug that was fixed? I really hope it is not a bug that was fixed, but a feature removed or even a about:config setting. This is so important to have back. Would you be able to do some digging for me and find out exactly what is/was fixed or removed?

Thanks, Moonchild, I appreciate the help.

[Moonchild]

That would be bug #864107

[MozillaUser233]

That would be bug #864107

Ekk. That sucks .

Comment on attachment 740195 [details] [diff] [review]
constrain restored window dimensions to available screen area

[Approval Request Comment]
Bug caused by (feature/regressing bug #): Longstanding bug, but the introduction of hi-dpi support for Windows will mean more users experience it.

User impact if declined: Restored windows may not fit on screen.

Testing completed (on m-c, etc.): In Nightly; also confirmed to fix bug 852371 using Aurora tryserver build (see comment 8).

Risk to taking this patch (and alternatives if risky): Low risk - code change is simple and well understood.

If there are users who have *deliberately* placed windows partly/fully off-screen, and expect Session Restore to maintain that position, this will change that behavior, and so could be seen as a regression - but it seems unlikely that is a widely-desired feature.

String or IDL/UUID changes made by this patch: None

I believe it is a widely desired feature. Belief is far from facts though.

It would be awesome if they can implement this as a feature in about:config settings.

[Moonchild]

I believe it is a widely desired feature. Belief is far from facts though.

I think your belief may not be shared by the majority of users. Not many people purposefully place an application partially off-screen and expect it to be restored like that in their next session.

It would be awesome if they can implement this as a feature in about:config settings.

Mozilla will not, but it should be easy enough to add a hidden pref in Pale Moon to exactly position the window where it was, of course to be used at your own risk.

[MozillaUser233]

I believe it is a widely desired feature. Belief is far from facts though.

I think your belief may not be shared by the majority of users. Not many people purposefully place an application partially off-screen and expect it to be restored like that in their next session.

It would be awesome if they can implement this as a feature in about:config settings.

Mozilla will not, but it should be easy enough to add a hidden pref in Pale Moon to exactly position the window where it was, of course to be used at your own risk.

Yes. Yes. Yes. Please do so if you and your team can. It would be wicked and even further make Palemoon Unique. Dood you're awesome.

[Moonchild]

All right. Tell you what: the next point release of Pale Moon will have a hidden Bool pref called browser.sessionstore.exactPos and if set to true will restore the exact window position. This will probably take me very little time to add, anyway.

(hidden pref means you have to manually add it in about:config with New -> Boolean)

[MozillaUser233]

All right. Tell you what: the next point release of Pale Moon will have a hidden Bool pref called browser.sessionstore.exactPos and if set to true will restore the exact window position. This will probably take me very little time to add, anyway.

(hidden pref means you have to manually add it in about:config with New -> Boolean)

Fantastic! Again, Thank you so much. I'm right excited.

[MozillaUser233]

Wicked!

Thanks for the update and the newly added feature .

[MozillaUser233]

All right. Tell you what: the next point release of Pale Moon will have a hidden Bool pref called browser.sessionstore.exactPos and if set to true will restore the exact window position. This will probably take me very little time to add, anyway.

(hidden pref means you have to manually add it in about:config with New -> Boolean)

Moonchild, can confirm from your side this is no longer working with a brand new profile of latest stable version 25.7.0 (x64) palemooon?

I move my web browser off the screen half way, close palemoon, open it and it does not any longer stay off screen.

[x-15a2]

Moonchild, can confirm from your side this is no longer working with a brand new profile of latest stable version 25.7.0 (x64) palemooon?
I move my web browser off the screen half way, close palemoon, open it and it does not any longer stay off screen.

I just tested this with 25.7.0 x64 and 26.0.0b1with both existing and new user profiles and it worked as expected. Previous to this testing I had not used this setting so I needed to get into about:config to configure it, but once that was done is worked as designed, even when I closed the window on a secondary display.

[MozillaUser233]

Ok ty. Ita something on my end. I'll trouble shoot.

[MozillaUser233]

On my old default profile browser.sessionstore.exactpos works.

On a new profile it doesn't work.

I uninstalled pm several times n cleaned out the peofiles.

I juat went to 1080p with a 24inch monitor, I wonder if that is the problem.

[x-15a2]

Since it works in the old profile and not in the new, the difference has to be in the profile since both are using the same PM code and the same hardware. Since it's a new profile, I have to assume that you don't have any extensions or plugins in that profile so that really only leaves browser.sessionstore.exactPos , which by default is disabled and needs to be enabled by the user in each profile.

[New Tobin Paradigm]

Doesn't "Restore windows and tabs" or whatever have to be enabled for session to be restored thus the window position?