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

Firefox v14.0.1, WinXP, changes window order on FF restart

  • 6 replies
  • 3 have this problem
  • 2 views
  • Last reply by belboz

more options

A similar question was asked about 4 months ago, with no confirmed answer: after a FF 14.0.1 restart (say, after a crash or when the Firefox task is terminated from Task Manager), the ORDER of the restored windows is different than it was at shutdown.

In some cases it appears the first window (the one at the bottom of the Windows taskbar display for FF windows) at restart is that which was the active window when Firefox stopped. Otherwise, the order can sometimes seem unpredictable.

(Let's say I have 5 FF windows open, each with a list of specific tabs, and assume they are shown as the taskbar in a popup as:

       5
       4
       3
       2
       1

What I want is for FF to behave as it used to following a crash or restart, and PRESERVE this order, instead of transforming it to, say,

       5
       4
       2
       1
       3)

Surely this should be the default behavior? If not, how I can I remedy this?

Thanks in advance.

A similar question was asked about 4 months ago, with no confirmed answer: after a FF 14.0.1 restart (say, after a crash or when the Firefox task is terminated from Task Manager), the ORDER of the restored windows is different than it was at shutdown. In some cases it appears the first window (the one at the bottom of the Windows taskbar display for FF windows) at restart is that which was the active window when Firefox stopped. Otherwise, the order can sometimes seem unpredictable. (Let's say I have 5 FF windows open, each with a list of specific tabs, and assume they are shown as the taskbar in a popup as: 5 4 3 2 1 What I want is for FF to behave as it used to following a crash or restart, and PRESERVE this order, instead of transforming it to, say, 5 4 2 1 3) Surely this should be the default behavior? If not, how I can I remedy this? Thanks in advance.

Chosen solution

May be related. Discussion in Bugzilla; do not post in Bugzilla unless you can supply code example to solve the problem. Appears related to MRU (most recently used) order. Seems to only affect Firefox after version 8.

Extension claiming to fix the problem


If this reply solves your problem, please click "Solved It" next to this reply when signed-in to the forum.

Read this answer in context 👍 1

All Replies (6)

more options

Hi,

The session information is by default saved every 15 seconds. The active window is saved as selectedWindow in sessionstore.js. If for ex. we change the active window but Firefox is force closed before the next 15 secs the information may not be updated. Please note that this is not a technical explanation, just a thought :) One way you could check is by reducing the time of browser.sessionstore.interval, change to a new Window, wait for the time to elapse and force close Firefox.

Session Restore

Session Restore

more options

This is very interesting information, thank you very much. I can see changes in sessionrestore.js over time, but -- so far -- nothing which appears to control the window order display. The list of windows and tabs in this file (starts at the beginning of the file with [{"windows":[{"tabs":[{"entries":[{"url) is, at least at the moment, in the order of the window display.

I will check those entries after the next forced restart to see if the window order there has been modified somehow; but I'm still very interested to know why such a thing would ever occur.

Thank again, though, for the pointers.

more options
more options

Chosen Solution

May be related. Discussion in Bugzilla; do not post in Bugzilla unless you can supply code example to solve the problem. Appears related to MRU (most recently used) order. Seems to only affect Firefox after version 8.

Extension claiming to fix the problem


If this reply solves your problem, please click "Solved It" next to this reply when signed-in to the forum.

Modified by SafeBrowser

more options

Again, interesting, thanks for the tip. I am still evaluating the code fragment in that post to ensure it provides only a display of the windows/tabs rather than a modification of the active .js file, but so far it seems to be a nice p.d. tool.

more options

Everything in your post, the problem description (712763) and thread in bugzilla, and the bypass-fix, match exactly the symptoms I see.

Thanks very much!

W.

Modified by belboz