.png)
It has been a while since our last update to Tabox, so we made sure this one will be a MAJOR one!
Today we are happy to announce that Tabox 3.5.3 has been released.
This version brings you one of the most requested feature by Tabox users - auto updating collections!
Please note that this feature is in BETA .
Only use it with the understanding that things can go wrong.
Though we do not expect major problems, some possible issues include collections data could be deleted or altered in a way you were not expecting.
With that in mind, if you are willing to try out this feature, we would love to hear your feedback, good or bad! You can contact us, post on the forum or create an issue on GitHub.
The update has been sent to the Chrome and Edge stores and is pending their review process. It should be made available to everyone within the next few days.
v3.5.3 in now available on the Chrome Web Store and will be automatically updated for all users within the next few days.
The version is pending review on the Edge store and will be made available within the next few days.
Here is the full list of changes for v3.5.3:
Auto updating collections (beta) - You can now enable this option in Tabox's settings menu. When enabled, if you click to open a collection, Tabox will keep track of any changes to the window where the collection is open. Each time something changes (like if you close or open a tab, create or edit a tab group etc.) Tabox will update the collection in the background. You also have the option to choose if you want to automatically start tracking new collections as you add them. This will activate auto updating tracking the moment you add a new collection, updating it with any changes you make.
UI updates - We made the interface nicer (at least we think), the dark mode theme is now darker and the light mode theme is... lighter.
Change to how enabling sync works: Tabox always keep a "last modified" timestamp locally even if you do not use sync. If you enable sync, Tabox will compare the timestamp for your local changes against what it has (if any) on the remote side. If the local is newer, it will update the remote to be what you have locally. If the remote is newer, it will replace what you have locally with what's available in the remote. To avoid a situation where you enable sync and want your local collections overwritten - make sure to make a small change (move, update, add or delete a collection) BEFORE enabling sync.
Slightly reduce the amount of memory Tabox uses. This is something we are still working on and will continue to improve with future versions. Chrome is a RAM eating monster, but we try to make Tabox slightly less monstrous. More like one of those cure monsters from "Monster's Inc".
Bug fix - scroll was not working in beta versions of Chrome (Chrome Canary) so we fixed that. Scrolling is important - just ask Instagram and Facebook.
Bug fix - users who enabled sync, would some times open Tabox and sync would be off. We thought people likes login in over and over again to help them remember their passwords. We were wrong.
When you disable sync (i.e logout) and then at a later time re-enable sync, we will try to have your Google account stay signed in so you won't need to enter your email and password again. But we can't 100% guarantee this will be the case, that is up to that big G up in the cloud (no, not God, Google).
Officially dropping support for Tabox v2 - It has been almost 2 years people, time to move on.
Dropping support for browsers based on Chrome version < 89 - We use some APIs that only exist in newer versions of Chrome, like tab groups. So bye bye older Chrome versions, it's not you, it's us. But mostly you.
Comments