v28 Windows taskbar button order Topic is solved

[Moonchild]

I'm disappointed that I don't even get an answer, let alone that this problem will be resolved.

I'm sorry but we've all been very busy with more important things that affect everyone.
Also, you stated you had mostly migrated to Firefox, further lowering the importance/priority of this.

As for the cause: stab in the dark educated guess would be because sessionstore was made completely asynchronous by Mozilla between our fork points for 27 and 28, which makes this kind of "retained ordering of opening and closing" impossible unless explicitly tracked.

[Cmdr_Data]

Also, you stated you had mostly migrated to Firefox, further lowering the importance/priority of this.

You're right, but I use Firefox enforcedly, rather I'd use Palemoon, I've used it for years before version 28.

As for the cause: stab in the dark educated guess would be because sessionstore was made completely asynchronous by Mozilla between our fork points for 27 and 28, which makes this kind of "retained ordering of opening and closing" impossible unless explicitly tracked.

I don't understand anything... But I'll not lose my hope that someday this problem would be solved...

[Moonchild]

I'll try to translate.

Tasks that are "asynchronous" are not executed in order, but rather, the different parts of the task are all issued at once, and then processed in whatever order completes first. So if there is a list of windows that are closed "asynchronously", then whichever window closes the fastest will be recorded as "first", unrelated to the order in which they were originally opened.