[10] Taskbar Icons r Reordered on open from Session Restore

Bug reports and enhancement requests
User avatar
therube
Ambassador
Posts: 7924
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: [10] Taskbar Icons r Reordered on open from Session Restore

Post by therube »

That is ridiculous & irrelevant.
You close your browser & you expect it to open back up as it was - including windows & tabs & their respective locations along the (OS) taskbar.

There is nothing in the good book that says you have to wait xx number of seconds before you can reopen.
If it's an issue with the browser not writing out its' session timely, then fix it!

Quantum (like Win10) is nothing more then a cesspool of bugs, bound to fail from the outset.
Aren't we glad that we have a browser (OS) that we can no longer depend upon.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.5
User avatar
therube
Ambassador
Posts: 7924
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: [10] Taskbar Icons r Reordered on open from Session Restore

Post by therube »

(With a quick look) Chromium does not appear to be affected by this - neither natively, nor in conjuction with NoScript.

Nor does (individual) closure of multiple Windows result in unexpected windows reopening upon opening from "session restore".


(BTW, I can open/close/open/close... Chrome, lickety split [actually before the GUI fully draws]. Actually surprised that it kept up. [It did ramp up CPU during these rapid fire open/closes.])

(Not quite sure how "restore closed window/tab works", but after one of my individual closure of multiple windows, followed by browser close & reopen, I did get a [one time] restore previously closed window [or something to that effect - 'Reopen closed window', it is] that restored a window I was not expecting - as in it was not one of my "individual closure of multiple windows" windows. Yep something definitely wrong in that regard.)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36
User avatar
therube
Ambassador
Posts: 7924
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: [10] Taskbar Icons r Reordered on open from Session Restore

Post by therube »

FF Quantum (67) is inherently broken (so whether NoScript affects things or not, at this point is moot).
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 SeaMonkey/2.49.5
User avatar
therube
Ambassador
Posts: 7924
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: [10] Taskbar Icons r Reordered on open from Session Restore

Post by therube »

therube wrote: Sat Feb 02, 2019 12:14 am
I closed the windows one after the other. When I started Firefox again, three windows were restored in both cases. That was a surprise to me. This happened with and without NoScript.
Yep.
Been that way at least since 64.
(Don't recall when it actually hit, but it was certainly before 65. When I first saw it, & that would have been at the particular release time, I looked but didn't see a Bug filed. And I haven't seen it mentioned - at all, in Mozillazine, but it certainly is a bug.)

Yep.
That did come with 64, https://mozilla.logbot.info/firefox/20181211#c15707695.
This might be fixed with FF 67. I'll have to check more thoroughly when I get some time.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 SeaMonkey/2.49.5
User avatar
therube
Ambassador
Posts: 7924
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: [10] Taskbar Icons r Reordered on open from Session Restore

Post by therube »

Oh, going out on a limb - where is that piece of wood; knock, knock...

FF 69, 20190603160429, looks to be better behaved - both on its own, & also in conjunction with NoScript.

It will still mess up - but less like to do so.

Was on 67 before, & that screwed up - immediately.

69 is more consistent - though still not "right".

Now, you're more apt to see something like:

1-2-3-4
1-2-3-4
1-2-3-4
1-2-3-4
1-2-3-4
1-2-3-4
1-2-3-4
1-2-4-3 -> broke
1-2-4-3
1-2-4-3
1-2-4-3 ... & then it remains consistent like that - for a period of time... until it changes again.

Now this is with a very simple, very basic test; just 4 windows, either 0 or 1 extension (NoScript).

Much improved - compared to FF 67 - for whatever reason.
But still not "right", still not to where things should be - as in always working correctly - period.
https://bugzilla.mozilla.org/show_bug.c ... 235231#c37
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.5
Post Reply