(With FF's removal of version numbering...)
Make it more apparent things have changed:
Code: Select all
install.rdf
<em:name>NoScript 5.1.9rc1+HACK</em:name>
[
AHHHHH!!!
I wonder if things [taskbar icon ordering] are not broken in SeaMonkey 2.53 [with NoScript 5]?]
[
AHHHHH!!!
!AHHHHH!!!
I wonder if things [taskbar icon ordering] are not broken in SeaMonkey 2.53 [alone]?]
[AHHHHH!!!
I wonder if things [taskbar icon ordering] are not broken in SeaMonkey 2.53 [alone]?]
Yes.
But it takes, or so it seems, a VERY rapid sequence of browser open, close, open, close...
As in, all is correct the first time. And the second. And the third... Possibly forever.
But, if you open, & then an instant later, while things are still opening, hit Ctrl+Q (Quit) + Return, there exists the possibility that on next browser open, taskbar icons will be out of order. (As in the open/close sequence is too quick for the sessionrestore.json to be correctly written back to disk... or some such, causing taskbar icon order issues on the next restart.)
(As far as I can tell, I've not been able to duplicate the same in SeaMonkey 2.49. [And all of this is without NoScript, with a new, clean Profile, separate profiles for each browser version.)
(Window sizing may also come into play, or may make the situation easier to duplicate. With a new Profile, the initial window opens up, windowed, about half-screen. I like, try to keep [though it rarely remains for long] my windows full-screen. half-screen, or at least not resizing from what it the initial window opened up at, then simply opening 3 more windows, same size, makes it harder to duplicate. Maximizing all those windows, seems to make the issue easier to duplicate.
Oh... probably ought to note, that I had, oh 4 different browsers open of late, & one of them had consumed ~8 GB RAM, which is a mighty high amount for me, & when switching to other browsers, I noted that they had [partially] paged out, so their response was less then optimal. [I've since closed that 8 GB session.] Similar my computer has not been restarted since 11/27/2018 (19 days, at this point) so maybe those item are exacerbating what I'm seeing.)