Revisiones de Tab Session Manager
Tab Session Manager por sienori
1,188 revisiones
- Se valoró con 1 de 5por Usuario de Firefox 12286457, el hace un añoJan-2025 This outfit used to have two extensions - a video downloader and this Tab Session Manager. The video downloader stopped working about a year ago and now the Tab Session Manager has stopped working too. For almost two years, I've allowed them to autodebit my Paypal - BUT NO MORE. When I wrote them about the video downloader not working I never got a response. Adios.
Win 7 Pro
Firefox 115.19.0esr (64-bit)
Dell Precision M6600 w/8GBy - Se valoró con 5 de 5por Timpy, el hace un año
- Se valoró con 4 de 5por chicken tikka masalla, el hace un año
- Se valoró con 3 de 5por Usuario de Firefox 14052838, el hace un añoSaturday 2025 / January / 04
Tab Session Manager: Version 7.0.1 updated on June 5, 2024
Firefox: Version 133.0.3 (64-bit)
Tor Browser: Version 14.0.3 (based on Mozilla Firefox 128.5.0esr)
Windows 10 Pro
In Tor Browser, Tab Session Manager does Auto Save all sessions.
In Firefox, Tab Session Manager does not Auto Save any session.
In Tor Browser, opening, or restoring, a saved session works.
In both Firefox and Tor Browser, Keyboard Shortcuts do not work.
.
===========================================================================
Monday 2025 / January / 06
Addition after the original review.
I shut down Firefox and then restarted Firefox a little before midnight on Saturday 2025 / January / 04 , about 27 hours ago. On Sunday 2025 / January / 05 between 02:00 and 02:45, I looked at my computer's Download folder and noticed a folder that I had not seen before. I saw that the Tab Session Manager Auto Save folder had been created at 23:57 on Saturday, about the time I shut down and restarted Firefox. I then looked at the creation dates and times of the files in the three folders contained in the Auto Save folder. All files were created between 23:57 and 23:59 on Saturday.
The first file in the file list was named 2025-01-03 03-07-31 - FoxyTab Options #regular - [61{Redacted}-{Redacted}9-4{Redacted}-9{Redacted}-{Redacted}f].json, and it had a Created date and time of Saturday January 4, 2025, 23:58:13. Notice that the first part of the name is a date and time, specifically the date and time when Tab Session Manager created an auto save session. Notice also that the file's Created date and time is about 45 hours after Tab Session Manager created the auto save session contained in that file. Tab Session Manager should have saved the auto save session into a file and placed that file in the appropriate Auto Save folder at the same time that it auto saved the session.
. - Se valoró con 5 de 5por Usuario de Firefox 13167139, el hace un año
- Se valoró con 1 de 5por V G, el hace un añoThe extension no longer stores any sessions. Its basic functionality is broken. The last update was almost 7 months ago. Has it been abandoned?
- Se valoró con 1 de 5por JustinM, el hace un añoHasn't been updated in almost 7 months and lots of outstanding bugs on their Github page. They just don't seem to care about this anymore. Look elsewhere.
- Se valoró con 5 de 5por Usuario de Firefox 18750317, el hace un año
- Se valoró con 4 de 5por Usuario de Firefox 15988820, el hace un año
- Se valoró con 5 de 5por YoloSwagginInABox, el hace un año
- Se valoró con 5 de 5por Usuario de Firefox 18611309, el hace un año
- Se valoró con 3 de 5por juan riccio, el hace un año
- Se valoró con 1 de 5por Maj, el hace un año
- Se valoró con 5 de 5por Usuario de Firefox 13453659, el hace un año
- Se valoró con 5 de 5por Howar31, el hace un año
- Se valoró con 4 de 5por Michael Rabinovsky, el hace un añoI've used this addon for many years and I honestly love it, but I found an issue that unfortunately I cannot overlook at work- it doesn't save history. If you don't need your history after closing the browser, then this is a 5-star addon. Previously, I gave it three stars because I couldn't use it at work, and rarely needed it at home. I updated it to four stars because I found a workaround. If you make sure every tab is loaded, and logged in, or gracefully logged out, and set it to not auto open the latest session, you can open every website, log in, then load your last session. Your tabs will load correctly, which usually means you don't need your history.
This is the explanation I previously wrote about my issues and the lower rating: The default Firefox session manager saves the history of every tab, which is incredibly important for me, but it also leaves me between a rock and a hard place. I have to use cloud software for work. It logs you out periodically. When you sign in, it will usually resume where you were; however, when you restart your browser, it resets the session, and after you log in, it lands you on the main page. If you have your tab history, you can navigate back to the page you were on; otherwise, you're stuck with 50 (to sometimes 200) useless tabs, and a mess trying to figure out what you were doing. On the other hand, the Firefox session manager can save only one session and is incredibly inconsistent; it's a coin flip whether it will work after a crash, and the only way to guarantee a session is saved is by killing Firefox from the task manager. If you sign out of your Windows account, restart, or your OS crashes, and you forget or are unable to kill Firefox from the task manager, you're completely screwed. - Se valoró con 1 de 5por Cronodoug, el hace un añoI just want the pinned tabs to remain open even without restoring the session. This does nothing more than create a more bureaucratic history, just like restoring the session.
- Se valoró con 5 de 5por Даниил, el hace un añoЭто хорошо. Отлично. В общем радует. Все звёздочки мира ваши
- Se valoró con 4 de 5por Diogo Correia, el hace un año
- Se valoró con 1 de 5por smow, el hace un añoIt's been broken for a few months now - and nothing actually works.
- Se valoró con 2 de 5por Usuario de Firefox 14520466, el hace un añoUnfortunately it looks like this is not maintained regularly. It caused all favicons to disappear. It took me a good 20 mins to find it out and there's no doubt it was this extension causing that. It took me another 20 minutes to report the bug with all details on github, but after 2 weeks, still no response.