Reviews for Session Boss
Session Boss by William Wng
Review by Firefox user 12154843
Rated 3 out of 5
by Firefox user 12154843, 6 years agoFF v68.01 x64 - SB v2.11.2
This addon saves the current tabs periodically like the old Session Manager.
This version still has problems, as the restored tabs get messed up.
Luckly the pinned tabs still start unloaded, despite what the changelog says.
--
old reviews:
FF v67.0 x64 - SB v2.11.1
This version seemed to work correctly, but instead it has the old problem of some sessions restoring only a blank tab (expecially with multiple windows).
FF v60.6 ESR x64 - SB v2.2
This addon seems to work, but it restores tabs in a reversed order, which is quite annoying.
FF v66 x64 - SB v2.10
All seemed to work well, until a few minutes ago, when I lost all tabs.
The old correct sessions appear in SB, but if I restore them I only get an empty tab..
This addon saves the current tabs periodically like the old Session Manager.
This version still has problems, as the restored tabs get messed up.
Luckly the pinned tabs still start unloaded, despite what the changelog says.
--
old reviews:
FF v67.0 x64 - SB v2.11.1
This version seemed to work correctly, but instead it has the old problem of some sessions restoring only a blank tab (expecially with multiple windows).
FF v60.6 ESR x64 - SB v2.2
This addon seems to work, but it restores tabs in a reversed order, which is quite annoying.
FF v66 x64 - SB v2.10
All seemed to work well, until a few minutes ago, when I lost all tabs.
The old correct sessions appear in SB, but if I restore them I only get an empty tab..
Developer response
posted 6 years agoIs the restoring in reversed order with the Session Boss 2.2? Can you try it on the latest version 2.10? Thanks.
Edit: I believe the bug was caused by missing containers in the new browser. The session restore wasn't able to cope with undefined containers that its tabs were using. Please try out the new version 2.11. The new version fixes the bug and will ignore the missing container and restore the tabs in the default browser container.
Container migration across machines is a problem now because Firefox's container id is not portable across machines (across profiles). There's no API from Firefox to set the container id of a container; it's assigned sequentially by Firefox as a first come first set process. Containers need to be re-created manually and the tabs need to be assigned to the containers by hand in the new broswer. In future release, Session Boss will attempt to make container migration less painful with container restoration and batch tab assignment to containers.
Edit: I believe the bug was caused by missing containers in the new browser. The session restore wasn't able to cope with undefined containers that its tabs were using. Please try out the new version 2.11. The new version fixes the bug and will ignore the missing container and restore the tabs in the default browser container.
Container migration across machines is a problem now because Firefox's container id is not portable across machines (across profiles). There's no API from Firefox to set the container id of a container; it's assigned sequentially by Firefox as a first come first set process. Containers need to be re-created manually and the tabs need to be assigned to the containers by hand in the new broswer. In future release, Session Boss will attempt to make container migration less painful with container restoration and batch tab assignment to containers.