8 posts tagged with "Announcement"

We said it was coming in the last post, and it's here. 9.0.1 is a direct response to issue #411 and everything we admitted needed fixing there: permissions requested too early, missing opt-outs, and a couple of things that were working as intended but never explained anywhere.

TMS 9 has now reached everyone on the Chrome Web Store's normal rollout schedule. Good news, mostly. But an update this size doesn't land quietly, and a few things landed in our inbox that deserve a direct answer instead of a buried reply in a GitHub thread.

Five weeks ago we opened this series with a new look for a new era. Google just cleared v9.0.0 for review, and starting Monday morning, August 3rd, the rollout to the Chrome Web Store begins. This is the last stop on the road.

It's also pushing about 40°C outside as we write this, summer in full swing, and yes, 40°C in Italy is exactly as absurd as it sounds. Wherever you are, we hope you get a good stretch of vacation out of it. We won't really be taking one ourselves, but we'll admit to easing off the throttle a little.

When Chrome 149 introduced a regression that silently discarded suspended tabs inside tab groups on every browser restart, TMS shipped a workaround in version 8.1.4. When the same regression reached Microsoft Edge, we addressed that too. We knew from the start that these were stopgap measures, the right fix had to come from the browser itself.

It is now here. Chrome 150.0.7871.47 ships the browser-side patch for crbug.com/522338670. Tab groups restore correctly without any intervention from TMS. We have verified this with a clean restart session and multiple group configurations, and everything behaves as expected.

Here is what that means for TMS, and what we decided to do with the workaround code.

TMS has been quietly getting better for years, new bugfixes, compatibility patches, a full Manifest V3 migration, but the extension's visual identity never kept up. The settings pages still looked like a relic of 2018. The popup was fine, but only barely. Nothing matched the Marvellous Codeworks website.

That changes with TMS 9.

This is the first in a series of posts we're calling Road to TMS 9, a chance to show you what's being built on the feature branches before it ships, explain the decisions behind the changes, and hear from you before things are set in stone. Think of it as development in the open.

Today: the visual redesign.

If you are using Microsoft Edge and noticed that your suspended tabs inside tab groups disappear or turn into blank New Tab pages after a browser restart, you are running into the same Chromium-level regression that first appeared in Chrome 149, and it is now reaching Edge users too.

If you are using Chrome 149 and noticed that your suspended tabs inside tab groups turn into blank New Tab pages after a browser restart, you are not alone, and it is not your fault.

The Marvellous Suspender has been a fork since day one, born in 2021 out of The Great Suspender, at a time when that project had been pulled from the Chrome Web Store and flagged as malware. TMS cleaned up what needed cleaning and gave orphaned users somewhere to go. Fair enough, that's exactly what a fork is for.

But five years later, TMS isn't a patched-up copy of someone else's abandoned code anymore. It's had a full Manifest V3 rewrite, a proper visual redesign, its own contributors, and, as of a few months ago, a home under the Marvellous Codeworks name. The GitHub fork relationship, though, hadn't changed: technically, gioxx/MarvellousSuspender was still listed as a fork of the original repository, tied to its network, its issues, its history.