Closed Bug 575071 Opened 14 years ago Closed 4 years ago

Wrong window placement after restart with multiple viewports / Desktops

Categories

(Firefox :: Shell Integration, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 372650

People

(Reporter: unauffaelligerfakename, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100627 Firefox/3.6.4
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100627 Firefox/3.6.4

After closing and reopening firefox, the windows from the previous session open all over the place: First when started, Firefox changes the Viewport / Desktop, then it opens all the windows in the wrong places. In my case, wrong viewport AND wrong horizontal position on viewport

In the previous Firefox Version, windows were opening in their old / saved position relative to the currently selected viewport most of the time (which means: in the right spot, if the same viewport was active when closing / savin and reopening / loading), so I guess the "switch viewport on start before restoring session" could be an explanation for the change.

Reproducible: Always

Steps to Reproduce:
1. Open some firefox window
2. Place firefox windows on different viewports in different positions
3. Close firefox
4. Start firefox
Actual Results:  
OMG ITS ALL OVER THE PLACE

Expected Results:  
Absolute (or at least relative as in older firefox versions) window position same as before closing firefox.

Using compiz 0.8.6 / desktop wall plugin as standalone WM... no window decorator, no strange plugins, no effects, no session manager, no gnome, nothing special that interferes with window placement.

I can confirm this bug with Firefox 66 on Windows 10. Every time I restart my computer the windows appear on Desktop 1 and they're not in the size they were when Firefox was closed.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.