<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Marvellous Codeworks Blog</title>
        <link>https://kb.marvellouscode.works/blog</link>
        <description>Marvellous Codeworks Blog</description>
        <lastBuildDate>Thu, 05 Nov 2026 21:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[OAuth Proxy for Google: the piece behind Drive backups on Brave and Vivaldi is now a project]]></title>
            <link>https://kb.marvellouscode.works/blog/oauth-proxy-for-google</link>
            <guid>https://kb.marvellouscode.works/blog/oauth-proxy-for-google</guid>
            <pubDate>Thu, 05 Nov 2026 21:00:00 GMT</pubDate>
            <description><![CDATA[OAuth Proxy for Google, the small Cloudflare Worker that keeps Drive backups connected on Brave and Vivaldi, is now a Marvellous Codeworks project: AGPL-3.0, version 1.0.0, with its own documentation and page.]]></description>
            <content:encoded><![CDATA[<p>The small Cloudflare Worker that keeps <a class="" href="https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token">TMS Drive backups connected on Brave and Vivaldi</a> now has a name, a license and a home of its own. It's called <strong>OAuth Proxy for Google</strong>, it's at version 1.0.0, and you can use it for your own browser extension.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>TL;DR</div><div class="admonitionContent_BuS1"><ul>
<li class=""><strong>Nothing changes for TMS users</strong>: there's nothing to install or configure.</li>
<li class=""><strong>What it is</strong>: a Cloudflare Worker that adds an OAuth client secret to Google token exchanges, so that secret never ships inside an extension.</li>
<li class=""><strong>Open source</strong>: <a href="https://github.com/Marvellous-Codeworks/tms-oauth-proxy" target="_blank" rel="noopener noreferrer" class="">AGPL-3.0 on GitHub</a>, with a <a href="https://github.com/Marvellous-Codeworks/tms-oauth-proxy/releases/tag/v1.0.0" target="_blank" rel="noopener noreferrer" class="">1.0.0 release</a>.</li>
<li class=""><strong>Docs</strong>: <a class="" href="https://kb.marvellouscode.works/docs/tms-oauth-proxy/overview">overview</a>, <a class="" href="https://kb.marvellouscode.works/docs/tms-oauth-proxy/self-hosting">self-hosting</a> and <a class="" href="https://kb.marvellouscode.works/docs/tms-oauth-proxy/faq">FAQ</a>.</li>
</ul></div></div>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-it-exists">Why it exists<a href="https://kb.marvellouscode.works/blog/oauth-proxy-for-google#why-it-exists" class="hash-link" aria-label="Direct link to Why it exists" title="Direct link to Why it exists" translate="no">​</a></h2>
<p>Chrome's <code>chrome.identity.getAuthToken()</code> doesn't work on browsers such as Brave and Vivaldi, so TMS has to use an <code>authorization_code</code> + PKCE flow there. The OAuth client type that flow needs is expected to keep its secret confidential, and a public extension package can't keep anything confidential.</p>
<p>The Worker solves that at the root. The secret lives in a Cloudflare secret, the extension talks to the Worker, and the Worker adds the secret and forwards the request to Google. The full reasoning is in the <a class="" href="https://kb.marvellouscode.works/docs/tms-oauth-proxy/overview#why-it-exists">overview</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-it-means-for-your-data">What it means for your data<a href="https://kb.marvellouscode.works/blog/oauth-proxy-for-google#what-it-means-for-your-data" class="hash-link" aria-label="Direct link to What it means for your data" title="Direct link to What it means for your data" translate="no">​</a></h2>
<p>If you use TMS on Chrome with the standard sign-in, or you don't use Drive backups, TMS never contacts the Worker.</p>
<p>On Brave and Vivaldi, with Drive connected, the authorization code and the tokens do pass through it while an exchange is in flight. The Worker has no storage attached and its code doesn't log request or response bodies. Your Drive files and backups never pass through it, and neither does your Google password. We've detailed <a class="" href="https://kb.marvellouscode.works/docs/tms-oauth-proxy/overview#what-passes-through-the-worker">what passes through the Worker</a>, and updated the <a href="https://www.marvellouscode.works/tms/privacy" target="_blank" rel="noopener noreferrer" class="">TMS privacy policy</a> to match.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="use-it-for-your-own-extension">Use it for your own extension<a href="https://kb.marvellouscode.works/blog/oauth-proxy-for-google#use-it-for-your-own-extension" class="hash-link" aria-label="Direct link to Use it for your own extension" title="Direct link to Use it for your own extension" translate="no">​</a></h2>
<p>Our instance only holds the TMS client secret and only accepts the TMS extension's origin, so it isn't a shared service. Nothing in the code is TMS-specific beyond its configuration, though: if your extension has the same problem, <a class="" href="https://kb.marvellouscode.works/docs/tms-oauth-proxy/self-hosting">deploy your own</a>.</p>
<p>You'll find the project on <a href="https://www.marvellouscode.works/tms-oauth-proxy" target="_blank" rel="noopener noreferrer" class="">its page</a> and on <a href="https://github.com/Marvellous-Codeworks/tms-oauth-proxy" target="_blank" rel="noopener noreferrer" class="">GitHub</a>, where issues and pull requests are welcome.</p>]]></content:encoded>
            <category>Announcement</category>
            <category>The Marvellous Suspender</category>
            <category>OAuth Proxy for Google</category>
        </item>
        <item>
            <title><![CDATA[The Marvellous Suspender 9.1.0 is live - tab groups, real screenshots and a calmer startup]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-release-9-1-0</link>
            <guid>https://kb.marvellouscode.works/blog/tms-release-9-1-0</guid>
            <pubDate>Wed, 04 Nov 2026 08:45:00 GMT</pubDate>
            <description><![CDATA[9.1.0 is live on the Chrome Web Store: per-group and grouped-tab protections, native screenshots for tab previews with SnapDOM as the new page renderer, a startup that no longer reloads every suspended tab at once, Ukrainian, three security fixes and a long list of bug fixes.]]></description>
            <content:encoded><![CDATA[<p>TMS 9.1.0 is <a href="https://chromewebstore.google.com/detail/the-marvellous-suspender/noogafoofpebimajpfpamcfhoaifemoa" target="_blank" rel="noopener noreferrer" class="">live on the Chrome Web Store</a> as of today. If you installed TMS from the Store, there's nothing to do: Chrome updates it by itself. To check, open <code>chrome://extensions</code> and look at The Marvellous Suspender's version.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>TL;DR</div><div class="admonitionContent_BuS1"><ul>
<li class=""><strong>9.1.0 is out</strong>, on the <a href="https://chromewebstore.google.com/detail/the-marvellous-suspender/noogafoofpebimajpfpamcfhoaifemoa" target="_blank" rel="noopener noreferrer" class="">Chrome Web Store</a> and on <a href="https://github.com/gioxx/MarvellousSuspender/releases/tag/v9.1.0" target="_blank" rel="noopener noreferrer" class="">GitHub</a>.</li>
<li class=""><strong>New</strong>: tab group protections, native screenshots for previews, a setting for startup checks, Ukrainian.</li>
<li class=""><strong>Fixed</strong>: browser freezes after a restart with lots of suspended tabs, and a long list of smaller bugs.</li>
<li class=""><strong>Security</strong>: three advisories closed, <a class="" href="https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories">explained here</a>. 9.0.3 and earlier are affected, so make sure you're updated.</li>
<li class=""><strong>On a test build?</strong> Please <a class="" href="https://kb.marvellouscode.works/docs/TMS/troubleshooting/help-test-a-fix">switch back to the Store version</a>.</li>
</ul></div></div>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-new">What's new<a href="https://kb.marvellouscode.works/blog/tms-release-9-1-0#whats-new" class="hash-link" aria-label="Direct link to What's new" title="Direct link to What's new" translate="no">​</a></h2>
<p>The <a class="" href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way">preview post</a> goes through all of this in detail, and <a class="" href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted">the numbers post</a> shows how much work went into it. In short:</p>
<ul>
<li class=""><strong>Tab groups</strong>: <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#never-suspend-tabs-in-the-following-tab-groups">never suspend a named group</a>, <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#never-suspend-tabs-in-a-tab-group">never suspend any tab in a group</a>, and suspend or unsuspend all the tabs <em>not</em> in a group, from the context menus or two bindable <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/keyboard-shortcuts">keyboard shortcuts</a>.</li>
<li class=""><strong>Tab previews</strong>: the tab you're looking at is captured with a real browser screenshot, so YouTube, GitHub and other pages that came out blank now get a proper preview. Choose how with <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#capture-method">Capture method</a>. SnapDOM replaces html2canvas as the page renderer.</li>
<li class=""><strong><a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#keep-a-recent-screenshot-of-tabs-as-i-use-them">Keep a recent screenshot of tabs as I use them</a></strong>: opt-in and off by default. It gives real previews to tabs suspended later in the background.</li>
<li class=""><strong>Startup</strong>: restored suspended tabs are checked a few at a time, and <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#suspended-tabs-checked-at-a-time-when-the-browser-starts">how many</a> is now a setting, from 1 to 8, default 3.</li>
<li class=""><strong>Ukrainian</strong> joins the supported languages, and Ukrainian and Sinhala now actually load when the language follows the browser. The <a class="" href="https://kb.marvellouscode.works/blog/tms-tooltips-translators">help tooltips</a> are easier to translate and can be reached from the keyboard.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-fixed">What's fixed<a href="https://kb.marvellouscode.works/blog/tms-release-9-1-0#whats-fixed" class="hash-link" aria-label="Direct link to What's fixed" title="Direct link to What's fixed" translate="no">​</a></h2>
<p>The biggest fix is for browsers freezing, or TMS crashing, after a restart with lots of suspended tabs (<a href="https://github.com/gioxx/MarvellousSuspender/issues/523" target="_blank" rel="noopener noreferrer" class="">#523</a>). Also fixed: <code>file://</code> pages that couldn't be suspended from the popup, a context menu that could disappear, Drive auto-backups that didn't retry after a temporary failure, Tab Health false positives on grouped tabs, and a paused toolbar icon that was hard to tell from the active one. Discarded tabs are also no longer reloaded just to take a screenshot.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="security">Security<a href="https://kb.marvellouscode.works/blog/tms-release-9-1-0#security" class="hash-link" aria-label="Direct link to Security" title="Direct link to Security" translate="no">​</a></h2>
<p>9.1.0 closes three security advisories, all reported privately and now public:</p>
<ul>
<li class=""><a href="https://github.com/gioxx/MarvellousSuspender/security/advisories/GHSA-qv22-cq95-fcqr" target="_blank" rel="noopener noreferrer" class="">GHSA-qv22-cq95-fcqr</a>: HTML injection on the History page through a crafted backup filename.</li>
<li class=""><a href="https://github.com/gioxx/MarvellousSuspender/security/advisories/GHSA-wxv6-36j4-qw5f" target="_blank" rel="noopener noreferrer" class="">GHSA-wxv6-36j4-qw5f</a>: HTML injection on the suspended page and through locale strings.</li>
<li class=""><a href="https://github.com/gioxx/MarvellousSuspender/security/advisories/GHSA-wh6f-63h6-wvq6" target="_blank" rel="noopener noreferrer" class="">GHSA-wh6f-63h6-wvq6</a>: other extensions could suspend tabs while skipping your protections.</li>
</ul>
<p><a class="" href="https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories">The dedicated post</a> explains what they were, who found them, and what you should do.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="permissions">Permissions<a href="https://kb.marvellouscode.works/blog/tms-release-9-1-0#permissions" class="hash-link" aria-label="Direct link to Permissions" title="Direct link to Permissions" translate="no">​</a></h2>
<p>The update adds no new install warning. <code>activeTab</code> is used for the native screenshot of the tab being suspended, and access to all sites is requested only if you turn on "Keep a recent screenshot of tabs as I use them". The <a class="" href="https://kb.marvellouscode.works/docs/TMS/permissions">Permissions page</a> has the details.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="if-youre-on-a-test-build">If you're on a test build<a href="https://kb.marvellouscode.works/blog/tms-release-9-1-0#if-youre-on-a-test-build" class="hash-link" aria-label="Direct link to If you're on a test build" title="Direct link to If you're on a test build" translate="no">​</a></h2>
<p>If you installed <code>v9.1.0-test.523</code> or <code>v9.1.0-test.551</code>, it won't update by itself. Thank you for testing, and please <a class="" href="https://kb.marvellouscode.works/docs/TMS/troubleshooting/help-test-a-fix">go back to the Store version</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-documentation-is-now-stable">The documentation is now stable<a href="https://kb.marvellouscode.works/blog/tms-release-9-1-0#the-documentation-is-now-stable" class="hash-link" aria-label="Direct link to The documentation is now stable" title="Direct link to The documentation is now stable" translate="no">​</a></h2>
<p>As announced, what was the <strong>Next</strong> documentation is now the <a class="" href="https://kb.marvellouscode.works/docs/TMS/overview">stable TMS documentation</a>, and it describes 9.1.0. Next stays online for what comes after this release.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-next">What's next<a href="https://kb.marvellouscode.works/blog/tms-release-9-1-0#whats-next" class="hash-link" aria-label="Direct link to What's next" title="Direct link to What's next" translate="no">​</a></h2>
<p>The <a href="https://github.com/gioxx/MarvellousSuspender/milestone/14" target="_blank" rel="noopener noreferrer" class="">9.1.1 milestone</a> collects the follow-up fixes and the <a href="https://github.com/gioxx/MarvellousSuspender/issues/295" target="_blank" rel="noopener noreferrer" class="">Edge Add-ons Store</a> publication, while <a href="https://github.com/gioxx/MarvellousSuspender/issues/358" target="_blank" rel="noopener noreferrer" class="">Group Policy support</a> moved to 9.2.0.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="thanks">Thanks<a href="https://kb.marvellouscode.works/blog/tms-release-9-1-0#thanks" class="hash-link" aria-label="Direct link to Thanks" title="Direct link to Thanks" translate="no">​</a></h2>
<p>This release belongs to the people who built it: <strong><a href="https://github.com/jadshaker" target="_blank" rel="noopener noreferrer" class="">@jadshaker</a></strong>, <strong><a href="https://github.com/ctsstc" target="_blank" rel="noopener noreferrer" class="">@ctsstc</a></strong>, <strong><a href="https://github.com/amargiovanni" target="_blank" rel="noopener noreferrer" class="">@amargiovanni</a></strong> and <strong><a href="https://github.com/hospotho" target="_blank" rel="noopener noreferrer" class="">@hospotho</a></strong>, <strong><a href="https://github.com/squeeze440" target="_blank" rel="noopener noreferrer" class="">@squeeze440</a></strong> for a very good security report, the Crowdin translators, and everyone who opened an issue, tested a pre-release build or sent a debug report. Thank you.</p>
<p>I wish you all the best on your journey.</p>
<p><em>Giovanni</em></p>
<hr>
<p><em>GitHub release, with the package and its checksum: <a href="https://github.com/gioxx/MarvellousSuspender/releases/tag/v9.1.0" target="_blank" rel="noopener noreferrer" class="">v9.1.0</a>. Full changelog: <a href="https://github.com/gioxx/MarvellousSuspender/blob/master/CHANGELOG.md#910--2026-11-04" target="_blank" rel="noopener noreferrer" class="">CHANGELOG.md</a></em></p>]]></content:encoded>
            <category>Announcement</category>
            <category>Release</category>
            <category>The Marvellous Suspender</category>
        </item>
        <item>
            <title><![CDATA[Three security fixes in The Marvellous Suspender 9.1.0, and the people who found them]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories</link>
            <guid>https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories</guid>
            <pubDate>Wed, 04 Nov 2026 08:30:00 GMT</pubDate>
            <description><![CDATA[9.1.0 closes three security advisories: HTML injection on the History page through a crafted backup file, HTML injection on the suspended page and through locale strings, and other extensions bypassing your suspension protections. What they were, who found them, what changed, and what you should do.]]></description>
            <content:encoded><![CDATA[<p>TMS 9.1.0 is now on the <a href="https://chromewebstore.google.com/detail/the-marvellous-suspender/noogafoofpebimajpfpamcfhoaifemoa" target="_blank" rel="noopener noreferrer" class="">Chrome Web Store</a>, and with it we are publishing three security advisories that it closes. All three were reported privately, through the process described in our <a href="https://github.com/gioxx/MarvellousSuspender/security/policy" target="_blank" rel="noopener noreferrer" class="">security policy</a>, and kept private until the fixed version was available to everyone. This post explains what they were, credits the people who found them, and describes what changed.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>TL;DR</div><div class="admonitionContent_BuS1"><ul>
<li class=""><strong>Update to 9.1.0.</strong> Chrome does this automatically. You can check your version under <code>chrome://extensions</code>. 9.0.3 and earlier are affected.</li>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/security/advisories/GHSA-qv22-cq95-fcqr" target="_blank" rel="noopener noreferrer" class="">GHSA-qv22-cq95-fcqr</a></strong> (moderate): a backup file with HTML in its filename could inject markup into the History page. Reported by <strong><a href="https://github.com/squeeze440" target="_blank" rel="noopener noreferrer" class="">@squeeze440</a></strong>.</li>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/security/advisories/GHSA-wxv6-36j4-qw5f" target="_blank" rel="noopener noreferrer" class="">GHSA-wxv6-36j4-qw5f</a></strong> (moderate): any web page could inject markup into the suspended-tab page, and a malicious translation could do the same on any extension page. Reported and fixed by <strong><a href="https://github.com/amargiovanni" target="_blank" rel="noopener noreferrer" class="">@amargiovanni</a></strong>.</li>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/security/advisories/GHSA-wh6f-63h6-wvq6" target="_blank" rel="noopener noreferrer" class="">GHSA-wh6f-63h6-wvq6</a></strong> (low): any other installed extension could suspend your tabs while skipping the protections you set, losing unsaved form input. Reported by <strong>@amargiovanni</strong>.</li>
<li class="">None of these allowed running code: the extension's Content Security Policy blocks scripts on its pages. The risk was believable fake content (links, forms) shown on a page that looks like, and runs as, TMS.</li>
</ul></div></div>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-no-code-execution-still-matters">Why "no code execution" still matters<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories#why-no-code-execution-still-matters" class="hash-link" aria-label="Direct link to Why &quot;no code execution&quot; still matters" title="Direct link to Why &quot;no code execution&quot; still matters" translate="no">​</a></h2>
<p>The first two advisories are the same kind of bug: data the extension does not control (a filename, a URL, a translated string) was written into a page as HTML instead of as text. On a normal website that is often enough to run JavaScript. On TMS's own pages it is not, because Chrome enforces the extension's Content Security Policy (<code>script-src 'self'</code>), and that blocked every script we and the reporters tried.</p>
<p>What it does not block is markup. An attacker could still place links, buttons and forms on a page served from the extension's own address, styled like TMS. That is a convincing place for a fake "restore your tabs" prompt or a login form that sends your credentials elsewhere. So we treated these as real vulnerabilities, not as theoretical ones.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="ghsa-qv22-cq95-fcqr-a-backup-filename-that-became-html-on-the-history-page">GHSA-qv22-cq95-fcqr: a backup filename that became HTML on the History page<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories#ghsa-qv22-cq95-fcqr-a-backup-filename-that-became-html-on-the-history-page" class="hash-link" aria-label="Direct link to GHSA-qv22-cq95-fcqr: a backup filename that became HTML on the History page" title="Direct link to GHSA-qv22-cq95-fcqr: a backup filename that became HTML on the History page" translate="no">​</a></h2>
<p><strong>Reported by <a href="https://github.com/squeeze440" target="_blank" rel="noopener noreferrer" class="">@squeeze440</a>. Severity: moderate.</strong></p>
<p>When you restore a backup from a local file (Options → Backup &amp; Restore → "Restore from local file"), TMS names the restored session after the file. The History page then showed that name using raw HTML. A file called, for example, <code>&lt;img src=x&gt;.json</code>, containing a valid backup, became a saved session whose name rendered as a live element every time you opened the History page, and it stayed there until you deleted that session.</p>
<p>It needed you to import a file someone gave you, but sharing session backups is a feature TMS advertises, so that is a plausible request.</p>
<p><strong>The fix:</strong> saved session names are now always shown as text. This also covers names you type yourself when saving a session.</p>
<p>@squeeze440's report was a model of what a security report should be: the exact source path from the filename to the page, a proof of concept, a careful CVSS rating explaining why the CSP lowered the impact, and a suggested fix. Thank you.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="ghsa-wxv6-36j4-qw5f-markup-on-the-suspended-page-and-in-translations">GHSA-wxv6-36j4-qw5f: markup on the suspended page and in translations<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories#ghsa-wxv6-36j4-qw5f-markup-on-the-suspended-page-and-in-translations" class="hash-link" aria-label="Direct link to GHSA-wxv6-36j4-qw5f: markup on the suspended page and in translations" title="Direct link to GHSA-wxv6-36j4-qw5f: markup on the suspended page and in translations" translate="no">​</a></h2>
<p><strong>Reported and fixed by <a href="https://github.com/amargiovanni" target="_blank" rel="noopener noreferrer" class="">@amargiovanni</a>. Severity: moderate.</strong></p>
<p>This one had two paths.</p>
<ol>
<li class=""><strong>The suspended-tab page, from any web page.</strong> <code>suspended.html</code>, the page a suspended tab shows, can be opened by any website (it has to be, for suspended tabs to work). It accepted an older <code>url=</code> parameter in its address and wrote the decoded value into the top bar as HTML. A website could link to a crafted placeholder address and have links and form controls appear on a page under the extension's name.</li>
<li class=""><strong>Translations.</strong> Translated strings were also inserted as HTML on every extension page. Translations come from the community through Crowdin and are reviewed before they're merged, so this needed a malicious translation to get through review, but if one did, it could place markup on any TMS page.</li>
</ol>
<p>While fixing it, two more places of the same kind turned up and were fixed too: saved session names on the History page (the same sink as the advisory above, reached from another direction) and the tab table on the debug page (tab group titles and favicon addresses).</p>
<p><strong>The fix:</strong> the suspended page now shows the original address and title as text. Translations are rendered through a small allow-list that keeps the few tags our strings actually use (<code>b</code>, <code>br</code>, <code>em</code>, <code>i</code>, <code>strong</code>, without attributes) and shows anything else as plain text. The debug page and the popup's status links are built as elements instead of HTML strings. New end-to-end tests run the original proof-of-concept address and a translation containing a link, and check that neither creates an element.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="ghsa-wh6f-63h6-wvq6-other-extensions-could-skip-your-protections">GHSA-wh6f-63h6-wvq6: other extensions could skip your protections<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories#ghsa-wh6f-63h6-wvq6-other-extensions-could-skip-your-protections" class="hash-link" aria-label="Direct link to GHSA-wh6f-63h6-wvq6: other extensions could skip your protections" title="Direct link to GHSA-wh6f-63h6-wvq6: other extensions could skip your protections" translate="no">​</a></h2>
<p><strong>Reported by <a href="https://github.com/amargiovanni" target="_blank" rel="noopener noreferrer" class="">@amargiovanni</a>. Severity: low.</strong></p>
<p>TMS inherited from The Great Suspender a way for other extensions to ask it to suspend or unsuspend a tab. Any installed extension could use it, with no permissions of its own, and the request ran at a level that skipped the protections you set: the whitelist, pinned tabs, tabs playing audio, the active tab, protected tab groups, and the check for unsaved form input. An extension could suspend a tab with text you had typed but not submitted, then unsuspend it, and that text was gone.</p>
<p>It needs a hostile or compromised extension already installed in your browser, and it does not let that extension read anything, which is why it is rated low.</p>
<p><strong>The fix:</strong> requests from other extensions now run at the same level as automatic suspension, so every protection you set applies to them too. Integrations that use this interface keep working; they just can't override you anymore. A test now pins that level so it can't silently regress.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-you-should-do">What you should do<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories#what-you-should-do" class="hash-link" aria-label="Direct link to What you should do" title="Direct link to What you should do" translate="no">​</a></h2>
<ul>
<li class=""><strong>Make sure you're on 9.1.0.</strong> Chrome updates extensions automatically. If you want to check, open <code>chrome://extensions</code> and look at The Marvellous Suspender's version.</li>
<li class=""><strong>Only restore backup files you made yourself, or that come from someone you trust.</strong> That's good practice in general, not just for this bug.</li>
<li class=""><strong>If you see a saved session with a strange name on the History page</strong>, delete it. With 9.1.0 it can no longer render as anything but text, but there's no reason to keep it.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="thanks">Thanks<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-security-advisories#thanks" class="hash-link" aria-label="Direct link to Thanks" title="Direct link to Thanks" translate="no">​</a></h2>
<p>Security reports take time and care, and getting them in private, with enough detail to fix the problem properly, is the best thing that can happen to a project like this. Thank you to <strong><a href="https://github.com/squeeze440" target="_blank" rel="noopener noreferrer" class="">@squeeze440</a></strong> for GHSA-qv22-cq95-fcqr, and to <strong><a href="https://github.com/amargiovanni" target="_blank" rel="noopener noreferrer" class="">@amargiovanni</a></strong> for finding GHSA-wxv6-36j4-qw5f and GHSA-wh6f-63h6-wvq6, writing most of the fixes, and testing the release branch before it shipped.</p>
<p>If you find something that looks like a security problem in TMS, please don't open a public issue: follow the <a href="https://github.com/gioxx/MarvellousSuspender/security/policy" target="_blank" rel="noopener noreferrer" class="">security policy</a> and report it privately.</p>
<p><em>Giovanni</em></p>
<hr>
<p><em>Full changelog on GitHub: <a href="https://github.com/gioxx/MarvellousSuspender/blob/master/CHANGELOG.md" target="_blank" rel="noopener noreferrer" class="">CHANGELOG.md</a></em></p>]]></content:encoded>
            <category>Security</category>
            <category>Release</category>
            <category>The Marvellous Suspender</category>
        </item>
        <item>
            <title><![CDATA[The Marvellous Suspender 9.1.0, by the numbers: submitted to the Chrome Web Store]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-9-1-0-submitted</link>
            <guid>https://kb.marvellouscode.works/blog/tms-9-1-0-submitted</guid>
            <pubDate>Tue, 03 Nov 2026 11:00:00 GMT</pubDate>
            <description><![CDATA[9.1.0 has been submitted to Google for review. Before it reaches everyone as an automatic update, a look at how much went into it: 400 commits, 54 pull requests, 44 closed issues, five people writing code, and a test suite that didn't exist two months ago.]]></description>
            <content:encoded><![CDATA[<p>TMS 9.1.0 is done, and as of today it is in Google's hands: the package has been submitted to the <a href="https://chromewebstore.google.com/detail/the-marvellous-suspender/noogafoofpebimajpfpamcfhoaifemoa" target="_blank" rel="noopener noreferrer" class="">Chrome Web Store</a> for review. Once it is approved, it will reach everyone who installed TMS from the Store as an automatic update, with nothing to do on your side.</p>
<p><a class="" href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way">The 9.1.0 preview post</a> already covers what's new. This one is about something else: how much work went into it, in numbers.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>TL;DR</div><div class="admonitionContent_BuS1"><ul>
<li class=""><strong>Submitted to Google today.</strong> It arrives as an automatic update once the Store review is done, usually within a few days.</li>
<li class=""><strong>401 commits, 54 pull requests, 44 closed issues</strong> since 9.0.3.</li>
<li class=""><strong>Five people wrote code</strong> for this release, and more than half of the commits that weren't translations came from contributors and maintainers.</li>
<li class=""><strong>From zero to 29 test files</strong>: around 290 unit tests and 19 end-to-end tests now run on every pull request.</li>
<li class=""><strong>18 languages, 446 strings each</strong>, after a full retranslation and a tooltip rewrite that cut 36 strings per language.</li>
</ul></div></div>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-numbers">The numbers<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted#the-numbers" class="hash-link" aria-label="Direct link to The numbers" title="Direct link to The numbers" translate="no">​</a></h2>
<p>Counted on the repository, from the 9.0.3 tag to the 9.1.0 release branch:</p>
<table><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>Commits</td><td><strong>401</strong>, plus 47 merges</td></tr><tr><td>Pull requests merged</td><td><strong>54</strong></td></tr><tr><td>Issues closed</td><td><strong>44</strong></td></tr><tr><td>Files changed</td><td><strong>116</strong></td></tr><tr><td>Lines added / removed</td><td><strong>~19,000</strong> / <strong>~7,800</strong></td></tr><tr><td>Changelog entries</td><td><strong>50</strong>, of which 22 are fixes</td></tr></tbody></table>
<p>Of those 401 commits, 184 are translation syncs from <a href="https://crowdin.com/project/tms" target="_blank" rel="noopener noreferrer" class="">Crowdin</a>: every time a volunteer translates or fixes a string, it lands in the repository as a commit. That's a lot of small contributions from people who never open a pull request, and it's why 9.1.0 ships with Ukrainian as a new language and a full retranslation of every other one.</p>
<p>The other 217 are code, tests and documentation. Of those, 117 came from contributors and maintainers.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="who-wrote-it">Who wrote it<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted#who-wrote-it" class="hash-link" aria-label="Direct link to Who wrote it" title="Direct link to Who wrote it" translate="no">​</a></h2>
<p>For the first time, most of a TMS release wasn't written by me:</p>
<ul>
<li class=""><strong><a href="https://github.com/jadshaker" target="_blank" rel="noopener noreferrer" class="">@jadshaker</a></strong>, 54 commits: the whole tab groups feature set, the paused toolbar icon and a long trail of fixes around them.</li>
<li class=""><strong><a href="https://github.com/amargiovanni" target="_blank" rel="noopener noreferrer" class="">@amargiovanni</a></strong>, 34 commits: the startup setting, the test harness, end-to-end tests in CI and the contributor guidelines.</li>
<li class=""><strong><a href="https://github.com/hospotho" target="_blank" rel="noopener noreferrer" class="">@hospotho</a></strong>, 19 commits: much less repeated storage and database work when suspending or restoring many tabs at once.</li>
<li class=""><strong><a href="https://github.com/ctsstc" target="_blank" rel="noopener noreferrer" class="">@ctsstc</a></strong>, 10 commits: the rebuilt screen capture stack, with native screenshots and SnapDOM.</li>
</ul>
<p>Commit counts don't measure effort, though: some of these commits are a one-line fix, others are a feature that went through a dozen review rounds. They're here to show that this was a shared effort, not to rank anyone.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="tests-finally">Tests, finally<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted#tests-finally" class="hash-link" aria-label="Direct link to Tests, finally" title="Direct link to Tests, finally" translate="no">​</a></h2>
<p>TMS 9.0.3 had no automated tests. 9.1.0 has 29 test files: about 290 unit tests and 19 end-to-end tests that load the packaged extension in a real browser and check it the way you use it. They run on every pull request, along with the linter and a check that every locale has every string.</p>
<p>You won't see any of this, but it's the reason a release this large could come together without breaking what already worked, and it's what will let future releases move faster.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="ai-assisted-development-with-rules">AI-assisted development, with rules<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted#ai-assisted-development-with-rules" class="hash-link" aria-label="Direct link to AI-assisted development, with rules" title="Direct link to AI-assisted development, with rules" translate="no">​</a></h2>
<p>9.1.0 is also the first release where we openly accepted AI-assisted contributions. Not as a free-for-all: the rules are written down in the repository, and they apply to every pull request, whoever or whatever wrote the code.</p>
<ul>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/blob/master/AGENTS.md" target="_blank" rel="noopener noreferrer" class="">AGENTS.md</a></strong> is the policy for anyone changing the code, human or coding agent: what "done" means (tests pass, lint passes, the extension loaded and tried by hand), what is mandatory (a test with every fix and feature, no new dependencies or permissions without a maintainer's yes, no page or locale data written as HTML) and what is off limits. Its <a href="https://github.com/gioxx/MarvellousSuspender/blob/master/AGENTS.md#working-with-ai-tools" target="_blank" rel="noopener noreferrer" class="">Working with AI tools</a> section is short: AI-assisted code is welcome only if the person opening the pull request has read every line, run the tests and the extension, and can answer questions about it. The pull request says which parts were AI-assisted. One whose author can't explain it is closed without review.</li>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/blob/master/CONTRIBUTING.md" target="_blank" rel="noopener noreferrer" class="">CONTRIBUTING.md</a></strong> covers the process around it: issues first for any feature, branches, review, and <a href="https://github.com/gioxx/MarvellousSuspender/blob/master/CONTRIBUTING.md#using-ai-tools" target="_blank" rel="noopener noreferrer" class="">using AI tools</a>.</li>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/blob/master/MAINTAINERS.md" target="_blank" rel="noopener noreferrer" class="">MAINTAINERS.md</a></strong> says who reviews and who decides. Releases and the Chrome Web Store listing stay with the maintainers.</li>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/blob/master/.github/PULL_REQUEST_TEMPLATE.md" target="_blank" rel="noopener noreferrer" class="">The pull request template</a></strong> turns part of AGENTS.md into a checklist each pull request has to fill in.</li>
</ul>
<p>We don't regret this choice. Every change still goes through review, the test suite above, and hands-on testing in a real browser before it ships, and we'll keep following the extension's development as closely as we always have. A tool doesn't change who answers for the code: we do.</p>
<p>If, for you, any AI involvement makes a project "slop", that's a legitimate position, and there are other suspenders out there that may suit your daily work better. No hard feelings at all.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="translations">Translations<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted#translations" class="hash-link" aria-label="Direct link to Translations" title="Direct link to Translations" translate="no">​</a></h2>
<ul>
<li class=""><strong>18 languages</strong>, each with <strong>446 strings</strong>.</li>
<li class=""><strong>25 help tooltips</strong>, now stored as 30 full paragraphs instead of 66 fragments cut by hand, which is why every language went from 482 to 446 strings. The <a class="" href="https://kb.marvellouscode.works/blog/tms-tooltips-translators">tooltips post</a> has the details.</li>
<li class=""><strong>Ukrainian</strong> added, and Ukrainian and Sinhala now actually load when the language is set to "auto".</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-happens-now">What happens now<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted#what-happens-now" class="hash-link" aria-label="Direct link to What happens now" title="Direct link to What happens now" translate="no">​</a></h2>
<p>Google reviews every new version before it is published. When the review is done, Chrome installs 9.1.0 by itself, usually within a few hours of the release going live. If you want to check, open <code>chrome://extensions</code> and look at The Marvellous Suspender's version.</p>
<p>If you installed TMS from source or from a test build, you can <a class="" href="https://kb.marvellouscode.works/docs/TMS/next/tms-install-from-source">update it yourself</a> as soon as the release is tagged on GitHub.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-documentation-becomes-stable">The documentation becomes stable<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted#the-documentation-becomes-stable" class="hash-link" aria-label="Direct link to The documentation becomes stable" title="Direct link to The documentation becomes stable" translate="no">​</a></h2>
<p>The documentation for 9.1.0 is already written, and today it lives under the <strong>Next</strong> version of the docs: <a class="" href="https://kb.marvellouscode.works/docs/TMS/next/overview">docs/TMS/next</a>. As soon as 9.1.0 is live on the Chrome Web Store, Next becomes the stable documentation: it will be what you get from the Docs menu and the TMS links on this site, and it will replace the 9.0.3 docs, since we only keep the stable version and Next online.</p>
<p>I'll post again when it is live on the Store.</p>
<p>Thanks to everyone who contributed code, translations, bug reports and test sessions. A release this size only happens because many people chose to spend some of their time on it.</p>
<p>I wish you all the best on your journey.</p>
<p><em>Giovanni</em></p>]]></content:encoded>
            <category>Release</category>
            <category>The Marvellous Suspender</category>
        </item>
        <item>
            <title><![CDATA[Help tooltips in TMS 9.1.0: easier to translate, easier to reach]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-tooltips-translators</link>
            <guid>https://kb.marvellouscode.works/blog/tms-tooltips-translators</guid>
            <pubDate>Tue, 03 Nov 2026 10:00:00 GMT</pubDate>
            <description><![CDATA[TMS 9.1.0, now in review on the Chrome Web Store, rewrites how the help tooltips on the Settings and Backup pages are stored and shown. Translators get one string per paragraph instead of hand-cut fragments, keyboard and screen reader users can reach every tooltip, and we are looking for a native Sinhala speaker to review a few sentences.]]></description>
            <content:encoded><![CDATA[<p>The small ⓘ icons next to many options on the Settings and Backup pages are one of the less visible parts of TMS, and one of the most translated: 25 tooltips, available in 18 languages. <a class="" href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way">TMS 9.1.0</a>, <a class="" href="https://kb.marvellouscode.works/blog/tms-9-1-0-submitted">submitted to Google for review today</a> and on its way to everyone as an automatic update, changes how their text is stored and how they are shown. Nothing is gone from them; what changes is the work it takes to translate them, and who can read them.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>TL;DR</div><div class="admonitionContent_BuS1"><ul>
<li class=""><strong>Part of 9.1.0, now in review on the Chrome Web Store.</strong> On Crowdin the new strings are already live, so translators can work on them today.</li>
<li class=""><strong>For translators:</strong> each tooltip paragraph is now a single string. No more sentences cut into 70-character pieces, no line breaks to place by hand. The number of strings per language went from 482 to 446.</li>
<li class=""><strong>For everyone:</strong> tooltips wrap by themselves, open above their option instead of running off the edge of the page, and can be reached with the Tab key. Screen readers read their text.</li>
<li class=""><strong>Can you read Sinhala?</strong> A few Sinhala tooltip sentences need a native speaker's eye. Details <a class="" href="https://kb.marvellouscode.works/blog/tms-tooltips-translators#a-request-for-sinhala-speakers">below</a>.</li>
</ul></div></div>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-translators-had-to-deal-with">What translators had to deal with<a href="https://kb.marvellouscode.works/blog/tms-tooltips-translators#what-translators-had-to-deal-with" class="hash-link" aria-label="Direct link to What translators had to deal with" title="Direct link to What translators had to deal with" translate="no">​</a></h2>
<p>Until 9.0.3, a tooltip could not wrap its own text: every line was shown exactly as written. To keep tooltips at a readable width, the English text was split by hand into fragments of about 70 characters, each stored as its own string (<code>…_line1a</code>, <code>…_line1b</code>, <code>…_line1c</code>, and so on).</p>
<p>That meant translators on <a href="https://crowdin.com/project/tms" target="_blank" rel="noopener noreferrer" class="">Crowdin</a> received half sentences with no indication of where the rest was. A fragment like "If enabled, it will force a tab to suspend instead" makes little sense alone, and the translation had to be cut at the same points as the English one, even when the grammar of the language puts the words in a completely different order. Some languages coped by stuffing the whole sentence into the first fragment and leaving the others nearly empty; others ended up with sentences that only read correctly if you knew how they had been split.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="one-string-per-paragraph">One string per paragraph<a href="https://kb.marvellouscode.works/blog/tms-tooltips-translators#one-string-per-paragraph" class="hash-link" aria-label="Direct link to One string per paragraph" title="Direct link to One string per paragraph" translate="no">​</a></h2>
<p>In 9.1.0 the tooltip wraps its own text within a maximum width, so the hand splitting is no longer needed. Each paragraph is now one string: the 66 old fragments became 30 complete paragraphs, and every language went from 482 to 446 strings.</p>
<p>We did not throw away any existing work. The translations already on Crowdin were joined back together, with a space between pieces (or without one, for Japanese and Chinese), and loaded onto the new strings, so every language kept its tooltips from day one. Two of those joins needed fixing by hand, and they have been.</p>
<p>The breaks between paragraphs live in the page itself, not in the strings, so <strong>no translator ever has to add a <code>\n</code> or any other special character</strong>. On Crowdin each of the 30 strings carries a short note saying exactly that: the text wraps by itself, write it as one paragraph.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="easier-to-reach">Easier to reach<a href="https://kb.marvellouscode.works/blog/tms-tooltips-translators#easier-to-reach" class="hash-link" aria-label="Direct link to Easier to reach" title="Direct link to Easier to reach" translate="no">​</a></h2>
<p>The same change fixed how tooltips behave on the page:</p>
<ul>
<li class=""><strong>They stay on screen.</strong> A tooltip now opens above its option, starting from the left edge of the row, instead of centred on the small icon. Long tooltips used to run off the edge of the page, and in German and Japanese an invisible one even added a horizontal scrollbar.</li>
<li class=""><strong>They work from the keyboard.</strong> Each ⓘ icon can now be reached with the Tab key, and the tooltip opens when it gets focus, not only on mouse hover.</li>
<li class=""><strong>Screen readers read them.</strong> The icon is labelled with the tooltip's text, so a screen reader announces the explanation instead of an unnamed image.</li>
</ul>
<p>None of this needs anything from you: Chrome installs 9.1.0 by itself when it is out, and the next time you open the Settings page the tooltips are there, in your language.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-request-for-sinhala-speakers">A request for Sinhala speakers<a href="https://kb.marvellouscode.works/blog/tms-tooltips-translators#a-request-for-sinhala-speakers" class="hash-link" aria-label="Direct link to A request for Sinhala speakers" title="Direct link to A request for Sinhala speakers" translate="no">​</a></h2>
<p>The automatic joining works well when the pieces of a sentence were translated in the same order as the English. For Sinhala that was not always true: in a few tooltips, the joined sentence has its parts in an order that does not read naturally. One example is the help text of "Add The Marvellous Suspender to right-click context menu", whose two halves ended up swapped around the verb.</p>
<p>We do not speak Sinhala, and we would rather not guess. If you do, you can help in a few minutes:</p>
<ol>
<li class="">Open the <a href="https://crowdin.com/project/tms" target="_blank" rel="noopener noreferrer" class="">TMS project on Crowdin</a> and join it (a free Crowdin account is enough).</li>
<li class="">Choose <strong>Sinhala</strong> and look for the strings whose identifier contains <code>tooltip</code>.</li>
<li class="">Fix any sentence that does not read well. Each one is a full paragraph now, so you can rewrite it freely.</li>
</ol>
<p>Your corrections reach TMS through the next Crowdin sync, with no further step on your side. The same goes for any other language: if a tooltip reads oddly in yours, Crowdin is the place to fix it, and now a single paragraph at a time.</p>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Feature</category>
            <category>News</category>
        </item>
        <item>
            <title><![CDATA[A small request about the new character]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-suspendy-fan-mail</link>
            <guid>https://kb.marvellouscode.works/blog/tms-suspendy-fan-mail</guid>
            <pubDate>Thu, 29 Oct 2026 11:00:00 GMT</pubDate>
            <description><![CDATA[After weeks of feedback against TMS 9's new mascot, an email from a user in Japan asked for the opposite: please keep Suspendy Guy around. Good news, nobody is going anywhere.]]></description>
            <content:encoded><![CDATA[<img src="https://kb.marvellouscode.works/img/suspendy-guy.webp" alt="Suspendy Guy" style="float:right;margin:0 0 1rem 1.5rem;width:180px">
<p>Since TMS 9 shipped, most of what reached us about the new mascot pointed in one direction. <a class="" href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#the-generative-image-backlash">The 9.0.2 post</a> collected some of it, and 9.0.2 itself answered with <a class="" href="https://kb.marvellouscode.works/blog/tms-classic-tgs-artwork">a checkbox that brings back the classic The Great Suspender artwork</a>. Fair feedback, taken seriously.</p>
<p>Then, a few weeks ago, an email with a subject line I didn't expect: <em>"A small request about the new character"</em>.</p>
<!-- -->
<p>It came from a user in Japan, with two screenshots of TMS attached, and it went the other way:</p>
<blockquote>
<p>I'm not quite sure why, but this character really struck a chord with me, much more than I expected. I've grown surprisingly attached to them, and seeing them has become one of the little things I enjoy about using the app.</p>
<p>So, if possible, I would be very happy if this character could remain available in future updates as well.</p>
<p>I know this may be an unusual request, but I wanted to let you know how much I like the character.</p>
</blockquote>
<p>It made me smile, and I'll admit it made my day too. After a long run of "please remove it", someone wrote in just to say "please keep it", and apologized in advance for asking.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="nobody-is-going-anywhere">Nobody is going anywhere<a href="https://kb.marvellouscode.works/blog/tms-suspendy-fan-mail#nobody-is-going-anywhere" class="hash-link" aria-label="Direct link to Nobody is going anywhere" title="Direct link to Nobody is going anywhere" translate="no">​</a></h2>
<p>What I replied there is worth repeating here, for anyone who feels the same way (or the opposite one):</p>
<ul>
<li class=""><strong>Suspendy Guy stays.</strong> There is no plan to remove the current mascot.</li>
<li class=""><strong>The classic artwork stays too.</strong> Given how many people asked for it, the old The Great Suspender look is one checkbox away in <strong>Options → General</strong>, and that isn't changing.</li>
<li class=""><strong>If a new character ever arrives</strong>, it gets added to the list, it doesn't replace anything. You'll keep being able to pick between every character TMS has used, old and new.</li>
</ul>
<p>Whichever side of the mascot debate you're on, you get to keep the one you like.</p>
<p>So, to our friend in Japan: thank you. Not for the request, which turned out not to need granting, but for taking the time to tell us that a small drawing on a suspended tab had become one of the little things you enjoy. That kind of email is rare, and it's the kind I keep.</p>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>News</category>
        </item>
        <item>
            <title><![CDATA[The Marvellous Suspender 9.1.0 is on its way - tab groups, real screenshots and a calmer startup]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way</link>
            <guid>https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way</guid>
            <pubDate>Wed, 28 Oct 2026 11:00:00 GMT</pubDate>
            <description><![CDATA[9.1.0 is wrapping up and heading to the Chrome Web Store: per-group and grouped-tab protections, native screenshots for tab previews with SnapDOM as the new page renderer, a startup that no longer reloads every suspended tab at once, Ukrainian, and a long list of fixes.]]></description>
            <content:encoded><![CDATA[<p>TMS 9.1.0 is in its final stretch and will be on its way to the <a href="https://chromewebstore.google.com/detail/the-marvellous-suspender/noogafoofpebimajpfpamcfhoaifemoa" target="_blank" rel="noopener noreferrer" class="">Chrome Web Store</a> shortly. It is the biggest release since 9.0, and for the first time most of it was not written by me: tab groups, screen capturing, startup recovery and a good chunk of the fixes came from contributors. So before it lands, here is what's coming, and who to thank for it.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>TL;DR</div><div class="admonitionContent_BuS1"><ul>
<li class=""><strong>Tab groups</strong>: never suspend a specific named group, or every tab in any group, plus suspend/unsuspend all the tabs <em>not</em> in a group.</li>
<li class=""><strong>Tab previews</strong>: the active tab is now captured with a real browser screenshot, and the page renderer moved from html2canvas to SnapDOM. Discarded tabs are no longer reloaded just to take a screenshot.</li>
<li class=""><strong>Startup</strong>: restoring a browser with lots of suspended tabs no longer reloads them all at once. How many are checked at a time is now a setting.</li>
<li class=""><strong>Ukrainian</strong> is a supported language, and Ukrainian and Sinhala now actually load when the language is set to "auto".</li>
<li class=""><strong>Fixes</strong>: <code>file://</code> tabs, a context menu that could vanish, Drive auto-backup retries, Tab Health false positives on grouped tabs, a clearer paused toolbar icon, and more.</li>
</ul></div></div>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-new">What's new<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way#whats-new" class="hash-link" aria-label="Direct link to What's new" title="Direct link to What's new" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="tab-groups-properly">Tab groups, properly<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way#tab-groups-properly" class="hash-link" aria-label="Direct link to Tab groups, properly" title="Direct link to Tab groups, properly" translate="no">​</a></h3>
<p>The <a href="https://github.com/gioxx/MarvellousSuspender/issues/133" target="_blank" rel="noopener noreferrer" class="">tab-groups feature set</a> that started with "suspend/unsuspend every tab in this group" in 9.0.3 is complete in 9.1.0, almost entirely thanks to <strong><a href="https://github.com/jadshaker" target="_blank" rel="noopener noreferrer" class="">@jadshaker</a></strong>:</p>
<ul>
<li class=""><strong><a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#never-suspend-tabs-in-the-following-tab-groups">Never suspend this tab group</a></strong>: right-click a page or a tab and pick "Never suspend this group". The exemption is persistent and works on named groups, matched by name and colour (Chrome's own group ids change across restarts). Rename the group and the exemption follows it. Options lists every exempt group, with how many open groups each one matches, so you can undo it from there too.</li>
<li class=""><strong><a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#never-suspend-tabs-in-a-tab-group">Never suspend tabs in a tab group</a></strong>: a new checkbox next to the pinned, audio and app-window protections. Off by default, so nothing changes unless you turn it on.</li>
<li class=""><strong>Suspend/unsuspend all tabs not in a group</strong>: the counterpart to the group actions, for the loose tabs left outside every group. Available from both context menus and as two bindable <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/keyboard-shortcuts">keyboard shortcuts</a>.</li>
</ul>
<p>The popup now tells you when a tab is protected by its group. None of these protections is absolute, though, and that's now spelled out too: a help tooltip on each "Never suspend…" option says what can still override it: suspending the tab yourself or with a "Force suspend" action, or a URL on the "Always suspend" list.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="tab-previews-that-actually-look-like-the-page">Tab previews that actually look like the page<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way#tab-previews-that-actually-look-like-the-page" class="hash-link" aria-label="Direct link to Tab previews that actually look like the page" title="Direct link to Tab previews that actually look like the page" translate="no">​</a></h3>
<p>If you use screen capturing, this is the change you'll notice first. Thanks to <strong><a href="https://github.com/ctsstc" target="_blank" rel="noopener noreferrer" class="">@ctsstc</a></strong>, who rebuilt the whole capture stack:</p>
<ul>
<li class=""><strong><a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#capture-method">Capture method</a></strong>: on "Automatic (recommended)", the default, the tab you're looking at is captured with a native browser screenshot. It takes a few milliseconds and works on sites the old renderer simply couldn't draw: YouTube, GitHub, anything built with modern CSS colours. Background tabs still go through the page renderer, since no browser API can screenshot a tab that isn't on screen. If one method fails, the other takes over.</li>
<li class=""><strong>SnapDOM replaces html2canvas</strong> as the page renderer. html2canvas threw on modern CSS (including our own homepage) and choked on cross-origin images. SnapDOM handles both, with a hard render deadline so a stubborn page can't hold a suspension hostage.</li>
<li class=""><strong><a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#keep-a-recent-screenshot-of-tabs-as-i-use-them">Keep a recent screenshot of tabs as I use them</a></strong>: opt-in, off by default. TMS keeps a recent native screenshot of the tabs you use, so tabs suspended later in the background get a real preview too. Only the latest screenshot of each open tab is kept, it never leaves your computer, and it is deleted when the tab closes. It needs access to all sites, requested only when you turn it on and removed when you turn it off, and it never captures incognito tabs or whitelisted sites.</li>
<li class=""><strong>No more reload just to take a screenshot</strong>: a tab Chrome's Memory Saver had already discarded used to be reloaded from the network so TMS could capture it. Not anymore.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-calmer-startup-with-lots-of-suspended-tabs">A calmer startup with lots of suspended tabs<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way#a-calmer-startup-with-lots-of-suspended-tabs" class="hash-link" aria-label="Direct link to A calmer startup with lots of suspended tabs" title="Direct link to A calmer startup with lots of suspended tabs" translate="no">​</a></h3>
<p>Restoring a browser session with dozens of suspended tabs used to trigger a burst of reloads, enough to freeze the browser or crash TMS on some setups (<a href="https://github.com/gioxx/MarvellousSuspender/issues/523" target="_blank" rel="noopener noreferrer" class="">#523</a>). 9.1.0 checks restored tabs a few at a time, active tabs first, leaves the background ones asleep, and gives up cleanly on a tab that doesn't answer instead of retrying forever.</p>
<p>Thanks to <strong><a href="https://github.com/amargiovanni" target="_blank" rel="noopener noreferrer" class="">@amargiovanni</a></strong>, the number of tabs checked at once is now a setting: <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#suspended-tabs-checked-at-a-time-when-the-browser-starts">Suspended tabs checked at a time when the browser starts</a>, from 1 to 8, default 3. If your browser still struggles after a restart, lower it. The <a class="" href="https://kb.marvellouscode.works/docs/TMS/faq#my-browser-froze-or-tms-crashed-after-a-restart-with-many-suspended-tabs-what-can-i-do">FAQ</a> has the details.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="ukrainian-and-languages-that-actually-load">Ukrainian, and languages that actually load<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way#ukrainian-and-languages-that-actually-load" class="hash-link" aria-label="Direct link to Ukrainian, and languages that actually load" title="Direct link to Ukrainian, and languages that actually load" translate="no">​</a></h3>
<p>Ukrainian joins the supported languages, fully translated thanks to a community volunteer on Crowdin. Along the way we found that Ukrainian and Sinhala had never loaded on "auto": their folders used codes Chrome doesn't recognise, so Chrome quietly fell back to English. Fixed, and if you had picked one of them by hand, your choice is kept. Every other language also got a full retranslation, with context in mind rather than string by string.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-fixed">What's fixed<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way#whats-fixed" class="hash-link" aria-label="Direct link to What's fixed" title="Direct link to What's fixed" translate="no">​</a></h2>
<ul>
<li class=""><strong><code>file://</code> tabs</strong> still couldn't be suspended from the popup even with "Allow access to file URLs" on: that browser toggle only lets TMS <em>ask</em> for the permission. The <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/system-pages">system pages</a> now walk you through the second step.</li>
<li class=""><strong>The right-click menu could vanish</strong> on some browsers (reported on Opera GX) and not come back until the next update. It is now rebuilt whenever needed, and on Chrome 147 and older, which refuse the tab-strip menu, the page menu stays in place.</li>
<li class=""><strong>Drive auto-backup</strong>: a one-off upload failure (a network blip, a server hiccup) now retries a few minutes later, instead of silently waiting for the next scheduled backup, up to a day away.</li>
<li class=""><strong>Tab Health</strong> flagged healthy grouped tabs as broken on Chrome 150+, hiding the favicon restore step.</li>
<li class=""><strong>The paused toolbar icon</strong> was hard to tell from the active one at 16px. It now carries an orange pause badge (thanks @jadshaker). The classic artwork keeps its grey icon.</li>
<li class=""><strong>Settings sync</strong>: two quick changes to the same setting could end on the older value, and turning a group exemption on or off could overwrite a change synced from another device.</li>
<li class=""><strong>Smaller fixes</strong>: favicons found through the root hostname (the YouTube case) were never cached, the Screen capturing help tooltip never showed up on the Settings page, a tab could be suspended twice if its status changed mid-suspension, and duplicate rows could pile up in the previews and favicon stores.</li>
</ul>
<p>There's also work you won't see but will benefit from: <strong><a href="https://github.com/hospotho" target="_blank" rel="noopener noreferrer" class="">@hospotho</a></strong> cut a lot of repeated storage and database work when suspending or restoring many tabs at once, and @amargiovanni added a test harness, end-to-end tests on the packaged extension running in CI, and contributor guidelines for the project.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="thanks">Thanks<a href="https://kb.marvellouscode.works/blog/tms-9-1-0-on-its-way#thanks" class="hash-link" aria-label="Direct link to Thanks" title="Direct link to Thanks" translate="no">​</a></h2>
<p>This release belongs to the people who built it: @jadshaker, @ctsstc, @amargiovanni and @hospotho, the Crowdin translators, and everyone who opened an issue, tested a pre-release build or sent a debug report. Thank you.</p>
<p>The <a class="" href="https://kb.marvellouscode.works/docs/TMS/overview">docs</a> are already updated for 9.1.0, and from now on they always describe the latest version. 9.1.0 will show up as an automatic update once the Store review is done, and I'll post again when it's live.</p>
<p>I wish you all the best on your journey.</p>
<p><em>Giovanni</em></p>
<hr>
<p><em>Full changelog on GitHub: <a href="https://github.com/gioxx/MarvellousSuspender/blob/master/CHANGELOG.md" target="_blank" rel="noopener noreferrer" class="">CHANGELOG.md</a></em></p>]]></content:encoded>
            <category>Release</category>
            <category>The Marvellous Suspender</category>
        </item>
        <item>
            <title><![CDATA[logdrop 1.4: login links that work once]]></title>
            <link>https://kb.marvellouscode.works/blog/logdrop-1-4-single-use-login</link>
            <guid>https://kb.marvellouscode.works/blog/logdrop-1-4-single-use-login</guid>
            <pubDate>Thu, 15 Oct 2026 16:00:00 GMT</pubDate>
            <description><![CDATA[logdrop 1.4.0 reworks admin sign-in: single-use magic links, a confirmation step that survives mail scanners, sessions bound to one browser for at most 8 hours, and a real sign out. Plus a Deploy with Vercel button.]]></description>
            <content:encoded><![CDATA[<p>logdrop has no passwords: maintainers sign in with a link emailed to an allow-listed address. Until today that link had a problem I didn't like. It was valid for 15 minutes, and during those 15 minutes <strong>anyone who had it could use it, as many times as they wanted, from as many browsers as they wanted</strong>, and every use opened its own 7-day session. A login link should be a key you use once, not a pass that works for a quarter of an hour. logdrop <strong>1.4.0</strong> fixes that, and rethinks sessions along the way.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="login-links-now-work-once">Login links now work once<a href="https://kb.marvellouscode.works/blog/logdrop-1-4-single-use-login#login-links-now-work-once" class="hash-link" aria-label="Direct link to Login links now work once" title="Direct link to Login links now work once" translate="no">​</a></h2>
<ul>
<li class="">A link works <strong>once</strong>, within 15 minutes of being requested. Use it a second time, from any browser, and you get <em>"That link expired or was already used"</em>.</li>
<li class="">Requesting a new link cancels the previous one.</li>
<li class="">The link no longer carries your email address, just a random token. The instance stores only a hash of it, so neither the token nor your address sits in storage.</li>
</ul>
<p>There's a catch with single-use links: many mail systems, Microsoft Defender Safe Links for one, open every link in advance to scan it. If opening the link were enough to sign in, the scanner would burn it before you ever clicked. So opening the link now only shows a <strong>Sign in</strong> button, and the link is used when you press it. One extra click, and it works behind corporate mail filters too.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="sessions-live-in-one-browser">Sessions live in one browser<a href="https://kb.marvellouscode.works/blog/logdrop-1-4-single-use-login#sessions-live-in-one-browser" class="hash-link" aria-label="Direct link to Sessions live in one browser" title="Direct link to Sessions live in one browser" translate="no">​</a></h2>
<ul>
<li class="">The session cookie has no expiry date, so it ends with your browser session. Another browser or device needs a new link.</li>
<li class="">Whatever the browser does with that cookie (some browsers restore session cookies when you reopen them), the server ends every session <strong>8 hours</strong> after sign-in. Enough for a day of triage, not a week of open door.</li>
<li class=""><strong>One session per admin</strong>: signing in on a second browser or device signs you out of the first. If someone ever signs in with your link, you'll notice, because you get kicked out.</li>
<li class="">There's finally a <strong>Sign out</strong> button, at the top right of every admin page. It ends the session on the server too, so a copied cookie stops working.</li>
</ul>
<p>Agent tokens aren't touched by any of this. They don't depend on your session and keep working until you regenerate or revoke them.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-bug-that-only-a-real-test-could-find">A bug that only a real test could find<a href="https://kb.marvellouscode.works/blog/logdrop-1-4-single-use-login#a-bug-that-only-a-real-test-could-find" class="hash-link" aria-label="Direct link to A bug that only a real test could find" title="Direct link to A bug that only a real test could find" translate="no">​</a></h2>
<p>"Works once" has to hold even when two requests arrive at the same moment. logdrop keeps everything in Vercel Blob, with no database, so the link is consumed with a conditional write: only the request that sees the link still unused can mark it as used. Unit tests passed. Then I fired ten parallel requests with the same link at a preview deployment, and <strong>two of them got in</strong>.</p>
<p>The cause: Vercel Blob's ETag (the version identifier the conditional write checks) is the MD5 of the content. The link record and its "used" marker had the same content, so the version never changed and every racing request passed the check. A unique "used" marker fixed it: ten parallel requests, exactly one sign-in, every time. The test suite now models ETags the way Vercel computes them, so this can't come back unnoticed.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="deploy-your-own-with-one-click">Deploy your own, with one click<a href="https://kb.marvellouscode.works/blog/logdrop-1-4-single-use-login#deploy-your-own-with-one-click" class="hash-link" aria-label="Direct link to Deploy your own, with one click" title="Direct link to Deploy your own, with one click" translate="no">​</a></h2>
<p>The <a href="https://github.com/Marvellous-Codeworks/logdrop" target="_blank" rel="noopener noreferrer" class="">logdrop README</a> now has a <strong>Deploy with Vercel</strong> button. It forks the repository, creates the Vercel project and its Blob store, and asks for every environment variable in one form. The optional Edge Config store and your domain are still manual steps; the <a class="" href="https://kb.marvellouscode.works/docs/logdrop/self-hosting">self-hosting guide</a> walks through what to prepare before clicking.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="upgrading">Upgrading<a href="https://kb.marvellouscode.works/blog/logdrop-1-4-single-use-login#upgrading" class="hash-link" aria-label="Direct link to Upgrading" title="Direct link to Upgrading" translate="no">​</a></h2>
<p>If you run your own instance:</p>
<ul>
<li class=""><strong>Every admin signs in once more after you deploy</strong>: sessions from earlier versions are no longer accepted.</li>
<li class="">No new environment variables.</li>
<li class="">To sign in on Preview deployments, set <code>SITE_URL</code> in the Preview environment to the preview's address, since login links are built from it.</li>
</ul>
<p>The details are in the <a href="https://github.com/Marvellous-Codeworks/logdrop/releases/tag/v1.4.0" target="_blank" rel="noopener noreferrer" class="">release notes</a> and in the updated <a class="" href="https://kb.marvellouscode.works/docs/logdrop/admin-login">Admin sign-in</a> page. As always, <a href="https://github.com/Marvellous-Codeworks/logdrop" target="_blank" rel="noopener noreferrer" class="">issues and pull requests</a> are welcome.</p>
<p><em>Giovanni</em></p>]]></content:encoded>
            <category>Release</category>
            <category>logdrop</category>
        </item>
        <item>
            <title><![CDATA[Introducing logdrop: a private way to share debug reports]]></title>
            <link>https://kb.marvellouscode.works/blog/introducing-logdrop</link>
            <guid>https://kb.marvellouscode.works/blog/introducing-logdrop</guid>
            <pubDate>Thu, 24 Sep 2026 13:30:00 GMT</pubDate>
            <description><![CDATA[logdrop is a small, self-hosted, PrivateBin-style drop-off for TMS diagnostic reports: no account to upload, auth-gated reads, auto-expiring. Use it instead of pasting a captureLogs report into a public GitHub issue.]]></description>
            <content:encoded><![CDATA[<p>Diagnosing a tricky TMS bug often means asking for a <code>captureLogs</code>/<code>debug.html</code> report from the <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/diagnostic-page">Diagnostic page</a>. Those reports are genuinely useful, they bundle your TMS version, browser details, and recent logs into one shareable block, but they're also a dump of real browser state: open tab titles and URLs, timestamps, sometimes local file paths. Pasting that directly into a GitHub issue makes it <strong>public and permanent</strong>, sitting in a thread that has nothing to do with the data itself.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-logdrop-does">What logdrop does<a href="https://kb.marvellouscode.works/blog/introducing-logdrop#what-logdrop-does" class="hash-link" aria-label="Direct link to What logdrop does" title="Direct link to What logdrop does" translate="no">​</a></h2>
<p><a href="https://github.com/Marvellous-Codeworks/logdrop" target="_blank" rel="noopener noreferrer" class="">logdrop</a> is a small, self-hosted, <a href="https://github.com/PrivateBin/PrivateBin" target="_blank" rel="noopener noreferrer" class="">PrivateBin</a>-style drop-off, live now at <a href="https://logdrop.marvellouscode.works/" target="_blank" rel="noopener noreferrer" class="">logdrop.marvellouscode.works</a>:</p>
<ul>
<li class=""><strong>No account needed to upload.</strong> Paste or drop your report, get a link back.</li>
<li class=""><strong>Reading a capture requires maintainer auth.</strong> Even if the link ends up pasted somewhere public, it's useless to anyone but me.</li>
<li class=""><strong>Uploads auto-expire on their own</strong>, no cleanup needed on either side. If you lose track of your own link, just capture and upload again, it's cheap to redo.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="privacy-and-security-notes">Privacy and security notes<a href="https://kb.marvellouscode.works/blog/introducing-logdrop#privacy-and-security-notes" class="hash-link" aria-label="Direct link to Privacy and security notes" title="Direct link to Privacy and security notes" translate="no">​</a></h2>
<p>A few things worth being explicit about, since this exists specifically to handle data you'd rather not have sitting in public:</p>
<ul>
<li class=""><strong>The upload itself travels over HTTPS</strong> and lands on the same hosting as the rest of <code>marvellouscode.works</code>, not a third-party paste service.</li>
<li class=""><strong>Only an authenticated maintainer session can read a capture.</strong> The upload link alone isn't a secret you have to protect, if it leaks, there's nothing to read behind it.</li>
<li class=""><strong>Auto-expiry is enforced on the storage side</strong>, not by a cleanup job that could fail silently. Once a capture's TTL is up, it's gone, there's no "soft delete" or backup copy sitting around afterward.</li>
<li class=""><strong>This isn't end-to-end encrypted like PrivateBin itself is.</strong> Since reads already require maintainer auth, we skipped client-side encryption for now to keep the tool simple, it's still a listed open question for later, not a settled no.</li>
<li class="">A capture only ever contains what your browser already showed you in <code>debug.html</code>, TMS doesn't collect or transmit anything beyond that on its own, logdrop is just a safer place to <em>put</em> it than a public issue thread.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-to-use-it-for-a-tms-bug-report">How to use it for a TMS bug report<a href="https://kb.marvellouscode.works/blog/introducing-logdrop#how-to-use-it-for-a-tms-bug-report" class="hash-link" aria-label="Direct link to How to use it for a TMS bug report" title="Direct link to How to use it for a TMS bug report" translate="no">​</a></h2>
<p>Instead of pasting a <code>captureLogs</code>/<code>debug.html</code> report straight into a GitHub issue or comment:</p>
<ol>
<li class="">Open the <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/diagnostic-page">Diagnostic page</a>, enable <strong>captureLogs</strong>, reproduce the issue, then <strong>Copy report</strong> or <strong>Download report</strong>.</li>
<li class="">Upload it to <a href="https://logdrop.marvellouscode.works/" target="_blank" rel="noopener noreferrer" class="">logdrop.marvellouscode.works</a>.</li>
<li class="">Paste the link it gives you into the issue instead of the raw report.</li>
</ol>
<p>The bug report template, the <a class="" href="https://kb.marvellouscode.works/docs/TMS/faq">FAQ</a>, the <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/diagnostic-page">Diagnostic page</a> guide, the <a class="" href="https://kb.marvellouscode.works/docs/TMS/troubleshooting/help-test-a-fix">test-build troubleshooting page</a>, and the <a href="https://marvellouscode.works/tms/report" target="_blank" rel="noopener noreferrer" class="">report form</a> on the site all point here now.</p>
<p>Tab Health scan reports (favicon/tab-group repair results) aren't affected, they're counts and status labels, not tab content, so pasting those directly into an issue is still fine.</p>
<p>This came out of <a href="https://github.com/gioxx/MarvellousSuspender/issues/518" target="_blank" rel="noopener noreferrer" class="">#518</a>. A few things are still open for later: uploading straight from TMS's own diagnostic UI instead of copy/paste, rate-limiting on the public upload endpoint, and whether client-side encryption is worth the added complexity given reads are already auth-gated.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="its-not-just-for-us">It's not just for us<a href="https://kb.marvellouscode.works/blog/introducing-logdrop#its-not-just-for-us" class="hash-link" aria-label="Direct link to It's not just for us" title="Direct link to It's not just for us" translate="no">​</a></h2>
<p>The <a href="https://github.com/Marvellous-Codeworks/logdrop" target="_blank" rel="noopener noreferrer" class="">logdrop repo</a> is public and open source, this isn't a TMS-only tool bolted onto our infrastructure. If you run your own project and want the same "reporters upload freely, only you can read it, it expires on its own" flow for your own bug reports or support requests, deploy your own instance, it's designed to be self-hosted by anyone. The one at <a href="https://logdrop.marvellouscode.works/" target="_blank" rel="noopener noreferrer" class="">logdrop.marvellouscode.works</a> is simply the instance we run and keep available for TMS users specifically, it's not a shared public service for unrelated projects.</p>
<p>We're wide open to questions, suggestions, and contributions from outside on the project itself, <a href="https://github.com/Marvellous-Codeworks/logdrop" target="_blank" rel="noopener noreferrer" class="">issues and pull requests</a> are welcome if you want to help make logdrop better.</p>
<p><em>Giovanni</em></p>]]></content:encoded>
            <category>Announcement</category>
            <category>The Marvellous Suspender</category>
            <category>logdrop</category>
        </item>
        <item>
            <title><![CDATA[The Marvellous Suspender 9.0.3 - battery-aware suspend, tab-group actions, favicon and Drive fixes]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-release-9-0-3</link>
            <guid>https://kb.marvellouscode.works/blog/tms-release-9-0-3</guid>
            <pubDate>Thu, 17 Sep 2026 11:03:00 GMT</pubDate>
            <description><![CDATA[9.0.3 ships a battery-power auto-suspend timeout, tab-group and app-window suspend controls, a real fix for suspended-tab favicons on Brave/Vivaldi/Dia, and a proper Drive backup fix for Brave and Vivaldi. Live now on the Chrome Web Store.]]></description>
            <content:encoded><![CDATA[<p>TMS 9.0.3 is <a href="https://chromewebstore.google.com/detail/the-marvellous-suspender/noogafoofpebimajpfpamcfhoaifemoa" target="_blank" rel="noopener noreferrer" class="">live on the Chrome Web Store</a> as of today. Two of the fixes in it were significant enough to get their own deep-dive posts while they were still in progress, so this one pulls everything together in one place, plus the smaller things that didn't get their own writeup.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-new">What's new<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#whats-new" class="hash-link" aria-label="Direct link to What's new" title="Direct link to What's new" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="separate-auto-suspend-timeout-for-battery-power">Separate auto-suspend timeout for battery power<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#separate-auto-suspend-timeout-for-battery-power" class="hash-link" aria-label="Direct link to Separate auto-suspend timeout for battery power" title="Direct link to Separate auto-suspend timeout for battery power" translate="no">​</a></h3>
<p>A new "Suspend tabs on battery power after" select, right alongside the existing plugged-in timeout in Settings. Set it once and tabs suspend more aggressively the moment you unplug, without touching your normal AC timeout at all. Defaults to "Same as when plugged in", so nothing changes unless you go set it.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="never-suspend-app-windows">"Never suspend app windows"<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#never-suspend-app-windows" class="hash-link" aria-label="Direct link to &quot;Never suspend app windows&quot;" title="Direct link to &quot;Never suspend app windows&quot;" translate="no">​</a></h3>
<p>On by default, like the pinned/audio/active-tab protections it sits next to. Keeps tabs open in an app-mode window, an installed PWA, or a site opened via "Create Shortcut → Open as window", out of automatic suspension. A manual "suspend this tab now" still works regardless, this only affects the automatic timer.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="suspendunsuspend-every-tab-in-a-tab-group">Suspend/unsuspend every tab in a tab group<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#suspendunsuspend-every-tab-in-a-tab-group" class="hash-link" aria-label="Direct link to Suspend/unsuspend every tab in a tab group" title="Direct link to Suspend/unsuspend every tab in a tab group" translate="no">​</a></h3>
<p>New page and tab-strip right-click menu items, plus two bindable keyboard shortcuts, acting on every tab sharing the clicked tab's group. Thanks to <strong><a href="https://github.com/mherkazandjian" target="_blank" rel="noopener noreferrer" class="">@mherkazandjian</a></strong> for building this, his first contribution to the project (<a href="https://github.com/gioxx/MarvellousSuspender/pull/438" target="_blank" rel="noopener noreferrer" class="">#438</a>) and part of a bigger <a href="https://github.com/gioxx/MarvellousSuspender/issues/133" target="_blank" rel="noopener noreferrer" class="">tab-groups feature set</a> still in progress for upcoming releases.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="always-reopen-suspended-tabs-scrolled-to-the-top">"Always reopen suspended tabs scrolled to the top"<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#always-reopen-suspended-tabs-scrolled-to-the-top" class="hash-link" aria-label="Direct link to &quot;Always reopen suspended tabs scrolled to the top&quot;" title="Direct link to &quot;Always reopen suspended tabs scrolled to the top&quot;" translate="no">​</a></h3>
<p>Opt-in. If you'd rather a suspended tab always reopen at the top of the page instead of wherever you left it scrolled, this does that, and overrides a <code>#section</code> link anchor in the URL too.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="reload-also-unsuspends-background-tabs">Reload also unsuspends background tabs<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#reload-also-unsuspends-background-tabs" class="hash-link" aria-label="Direct link to Reload also unsuspends background tabs" title="Direct link to Reload also unsuspends background tabs" translate="no">​</a></h3>
<p>Reloading a suspended tab you're not currently looking at, via a multi-tab selection, or right-click → Reload on an inactive tab, used to silently do nothing. Turn this on and it counts as an explicit unsuspend request, same as reloading the tab you're actively viewing already did.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-whats-new-screen-after-updates">A "What's new" screen after updates<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#a-whats-new-screen-after-updates" class="hash-link" aria-label="Direct link to A &quot;What's new&quot; screen after updates" title="Direct link to A &quot;What's new&quot; screen after updates" translate="no">​</a></h3>
<p>Exactly what you're reading the substance of right now, just inside the extension: a one-time modal on the Settings page after an update, showing only that version's changes, not the entire history.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-fixed">What's fixed<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#whats-fixed" class="hash-link" aria-label="Direct link to What's fixed" title="Direct link to What's fixed" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-rare-but-real-out-of-memory-crash">A rare but real out-of-memory crash<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#a-rare-but-real-out-of-memory-crash" class="hash-link" aria-label="Direct link to A rare but real out-of-memory crash" title="Direct link to A rare but real out-of-memory crash" translate="no">​</a></h3>
<p>Reproduced live, traced all the way to its actual mechanism, and fixed at the root rather than patched around the symptom: <code>chrome.storage.onChanged</code> was quietly broadcasting a full multi-megabyte copy of the diagnostic log buffer to every open suspended tab, every time anything was logged, and none of those copies ever got released. The whole log buffer moved to IndexedDB, which has no such broadcast, closing the gap entirely. Mostly invisible unless you use the debug page's <code>captureLogs</code> option, but the extension is more resilient across the board regardless. Full story: <a class="" href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page">9.0.3 in progress: chasing down a crash in TMS's own debug tooling</a>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="google-drive-backup-disconnecting-on-brave-and-vivaldi">Google Drive backup disconnecting on Brave and Vivaldi<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#google-drive-backup-disconnecting-on-brave-and-vivaldi" class="hash-link" aria-label="Direct link to Google Drive backup disconnecting on Brave and Vivaldi" title="Direct link to Google Drive backup disconnecting on Brave and Vivaldi" translate="no">​</a></h3>
<p>9.0.2 stopped the Drive connect flow from hanging on these browsers, but the token it fell back to was still short-lived and unreliable to renew, so accounts kept flipping back to "disconnected" after a backup or two. 9.0.3 replaces it with an authorization-code + PKCE exchange that mints a genuine long-lived refresh token, renewed by a direct call that doesn't depend on the browser at all, with the OAuth client secret moved server-side into a small proxy (<code>tms-oauth-proxy</code>) so it no longer ships inside the extension package. <strong>If you're on Brave or Vivaldi with Drive backup enabled, you'll need to reconnect once</strong> (Options → Backup → Connect) after updating, then it stays connected reliably. Full story: <a class="" href="https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token">9.0.3 in progress: a real fix for Drive backups disconnecting on Brave and Vivaldi</a>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="suspended-tab-favicons-stuck-on-the-extension-icon-after-a-restart">Suspended-tab favicons stuck on the extension icon after a restart<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#suspended-tab-favicons-stuck-on-the-extension-icon-after-a-restart" class="hash-link" aria-label="Direct link to Suspended-tab favicons stuck on the extension icon after a restart" title="Direct link to Suspended-tab favicons stuck on the extension icon after a restart" translate="no">​</a></h3>
<p>Mostly reported on Brave, Vivaldi, and Dia, where the automatic repair pass depended on a startup event those browsers don't fire reliably, so favicons reverted to TMS's own icon on every restart until manually fixed via Tab Health. A dedicated, restart-independent backstop now retries on its own on every service worker wake, and again the instant you open a suspended tab, so it recovers without you doing anything (<a href="https://github.com/gioxx/MarvellousSuspender/issues/474" target="_blank" rel="noopener noreferrer" class="">#474</a>, <a href="https://github.com/gioxx/MarvellousSuspender/issues/397" target="_blank" rel="noopener noreferrer" class="">#397</a>, <a href="https://github.com/gioxx/MarvellousSuspender/issues/260" target="_blank" rel="noopener noreferrer" class="">#260</a>). Thanks to everyone who tested pre-release builds and sent back debug reports to help pin this down.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-battery-specific-timeout-not-reacting-to-unplugging">The battery-specific timeout not reacting to unplugging<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#the-battery-specific-timeout-not-reacting-to-unplugging" class="hash-link" aria-label="Direct link to The battery-specific timeout not reacting to unplugging" title="Direct link to The battery-specific timeout not reacting to unplugging" translate="no">​</a></h3>
<p>It needed a manual trigger to take effect before; now it responds immediately when you unplug.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-bright-white-flash-switching-between-suspended-tabs">A bright white flash switching between suspended tabs<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#a-bright-white-flash-switching-between-suspended-tabs" class="hash-link" aria-label="Direct link to A bright white flash switching between suspended tabs" title="Direct link to A bright white flash switching between suspended tabs" translate="no">​</a></h3>
<p>Especially noticeable in dark mode. Reported as far back as v7.1.6.2 (<a href="https://github.com/gioxx/MarvellousSuspender/issues/168" target="_blank" rel="noopener noreferrer" class="">#168</a>), finally tracked down: a render-blocking stylesheet now paints the background immediately instead of showing the browser default until the real styles load.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-reload-link-on-suspended-tabs-too-bright-in-dark-mode">The reload link on suspended tabs, too bright in dark mode<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#the-reload-link-on-suspended-tabs-too-bright-in-dark-mode" class="hash-link" aria-label="Direct link to The reload link on suspended tabs, too bright in dark mode" title="Direct link to The reload link on suspended tabs, too bright in dark mode" translate="no">​</a></h3>
<p>Toned down from accent-blue to a subdued gray that actually fits the rest of that page's quiet dark-mode look.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="smaller-fixes">Smaller fixes<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#smaller-fixes" class="hash-link" aria-label="Direct link to Smaller fixes" title="Direct link to Smaller fixes" translate="no">​</a></h3>
<p>Tab reload/unsuspend determinism across a multi-tab selection, the debug page's tab-status list getting permanently stuck on "unknown" for a tab whose script had genuinely died, and a spacing inconsistency in Options.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-next">What's next<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-3#whats-next" class="hash-link" aria-label="Direct link to What's next" title="Direct link to What's next" translate="no">​</a></h2>
<p>The <a href="https://github.com/gioxx/MarvellousSuspender/issues/133" target="_blank" rel="noopener noreferrer" class="">tab-groups feature set</a> that @mherkazandjian and, more recently, <strong><a href="https://github.com/jadshaker" target="_blank" rel="noopener noreferrer" class="">@jadshaker</a></strong> have been building out continues past this release: a "suspend/unsuspend all tabs not in a group" counterpart and a global "never suspend tabs in a tab group" toggle have already landed on the development branch, with a per-group override still going through review, all targeting the next release. Ukrainian was added as a supported language, with translation now underway thanks to a community volunteer. Beyond that, 9.1.0 is shaping up around wider platform reach (Edge Add-ons Store, Group Policy for managed deployments) and finer control over suspend behaviour and UI.</p>
<p>I wish you all the best on your journey.</p>
<p><em>Giovanni</em></p>
<hr>
<p><em>Full changelog on GitHub: <a href="https://github.com/gioxx/MarvellousSuspender/blob/master/CHANGELOG.md" target="_blank" rel="noopener noreferrer" class="">CHANGELOG.md</a></em></p>]]></content:encoded>
            <category>Release</category>
            <category>The Marvellous Suspender</category>
        </item>
        <item>
            <title><![CDATA[9.0.3 in progress: chasing down a crash in TMS's own debug tooling]]></title>
            <link>https://kb.marvellouscode.works/blog/tms903-stability-debug-page</link>
            <guid>https://kb.marvellouscode.works/blog/tms903-stability-debug-page</guid>
            <pubDate>Wed, 26 Aug 2026 14:40:00 GMT</pubDate>
            <description><![CDATA[A live crash report led to a first, real round of fixes in TMS's log buffer and debug page, and then the crash kept happening anyway. Tracing it further uncovered the actual mechanism: a chrome.storage broadcast quietly duplicating megabytes of log data across every suspended tab, fixed by moving the whole log buffer to IndexedDB.]]></description>
            <content:encoded><![CDATA[<p>TMS's debug page has an optional <strong>captureLogs</strong> toggle for exactly one purpose: when something goes wrong, turn it on, reproduce the issue, and send us the report. It is meant to make diagnosing problems easier, not to become the problem itself.</p>
<p>A few days ago, while stress-testing 9.0.3 in development with dozens of suspended tabs open and <code>captureLogs</code> enabled, the opposite happened: the extension itself crashed, memory exhausted, requiring a full reload to recover. That is not an acceptable outcome for a tool whose entire job is to run quietly in the background and get out of the way, let alone for an extension whose whole purpose is to lighten Chrome's memory load in the first place. What follows is the real, unedited shape of tracking that down: a first round of fixes that were genuinely necessary and genuinely not enough, followed by the investigation that found what actually needed fixing.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>TL;DR</div><div class="admonitionContent_BuS1"><ul>
<li class="">Stress-testing 9.0.3 in development, with lots of suspended tabs and TMS's <code>captureLogs</code> debug option on, hit a real out-of-memory crash.</li>
<li class="">We fixed several genuine bugs in the log buffer and debug page (PR #472), and the crash kept happening anyway.</li>
<li class="">The actual cause: TMS's log storage was quietly sending a copy of itself to <em>every open suspended tab</em> every time it was written, and none of those copies ever got cleaned up. The more you logged, the faster it filled up your memory, regardless of how many tabs you had open.</li>
<li class="">The real fix moves that log storage to a different, safer mechanism (IndexedDB) that doesn't have this problem at all, plus a batch of smaller hardening fixes found along the way (PR #473, in progress).</li>
<li class=""><strong>Affects only people who turn on <code>captureLogs</code></strong> to help us debug something. If you've never touched that setting, none of this ever affected you.</li>
</ul></div></div>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="starting-from-a-real-report-not-a-hypothesis">Starting from a real report, not a hypothesis<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#starting-from-a-real-report-not-a-hypothesis" class="hash-link" aria-label="Direct link to Starting from a real report, not a hypothesis" title="Direct link to Starting from a real report, not a hypothesis" translate="no">​</a></h2>
<p>That crash produced a downloaded debug log, and that log became the map for everything that followed: every fix in this post was found by tracing an actual symptom back to its cause, not by guessing at what might theoretically go wrong.</p>
<p>The short version of what we found first: TMS's log buffer, the piece of code responsible for collecting diagnostic entries so <code>captureLogs</code> reports are useful, had accumulated several real memory and correctness bugs of its own. On top of that, the debug page's own tab-status checker had a design gap that made "unknown" tab statuses effectively permanent, and a runaway event handler that could multiply its own workload without bound.</p>
<p>None of this affects a normal TMS install with <code>captureLogs</code> off. But if you are the kind of user who leaves it on to help us track down a hard-to-reproduce issue, and you run TMS the way it is meant to be run, with a lot of tabs open, these are exactly the conditions that exposed every one of these bugs. They were real, they were fixed, and, as it turned out, they were not the whole story.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="round-one-the-log-buffers-duplicated-memory-unbounded-growth-and-a-crash-under-load">Round one: the log buffer's duplicated memory, unbounded growth, and a crash under load<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#round-one-the-log-buffers-duplicated-memory-unbounded-growth-and-a-crash-under-load" class="hash-link" aria-label="Direct link to Round one: the log buffer's duplicated memory, unbounded growth, and a crash under load" title="Direct link to Round one: the log buffer's duplicated memory, unbounded growth, and a crash under load" translate="no">​</a></h2>
<p>TMS's <code>gsUtils.js</code> module is imported by every page in the extension, the background service worker, every open settings page, and, critically, <strong>every single suspended tab</strong>. Each of those contexts used to keep its own in-memory copy of the recent log history, up to 10,000 entries, even though nothing ever read that copy back except the debug page itself (which reads straight from storage instead). With fifty suspended tabs open, that is fifty redundant buffers sitting in memory for no reason. Removed entirely.</p>
<p>The more serious issue was what happened when the service worker briefly lost contact with a suspended tab, or vice versa, which happens routinely as Chrome recycles the service worker to save memory. A failed log delivery got queued for retry, but nothing ever capped how large that retry queue could grow. Under sustained logging with <code>captureLogs</code> on, that queue could grow without limit until Chrome killed the page for memory pressure, which matched the "insufficient memory, extension disabled" report almost exactly. It was capped at 5,000 entries, oldest dropped first.</p>
<p>Fixing that surfaced the next problem: a burst of near-simultaneous log writes, for example every suspended tab reacting at once to <code>captureLogs</code> being toggled, meant dozens of full-buffer read-modify-write round trips to <code>chrome.storage.local</code> back to back. <code>chrome.storage.local</code> has no append primitive, every single log entry cost a full get-parse-stringify-set of the <em>entire</em> stored history. With ~50 tabs open, this alone was enough to make the extension noticeably sluggish, including pages unrelated to logging that just happened to be loading at the same time. Incoming log messages were coalesced into a single merge every 250ms instead of one merge per message, turning a fifty-tab burst into one round trip.</p>
<p>That coalescing change itself then introduced a genuine crash: if many contexts had each queued up their own maximum backlog while the service worker was briefly unreachable, all of them flushing at once could aggregate well over 100,000 log entries into a single batch. The code merging that batch into storage used JavaScript's spread operator (<code>array.push(...entries)</code>) to append it, and V8 throws a hard <code>RangeError</code> past a few tens of thousands of spread arguments. That failure caused every sender to requeue its batch, which reproduced the exact same oversized merge on the next attempt, forever, a real, repeatable crash that lined up precisely with the original report. Switched to <code>concat()</code>, which has no such limit, and added a hard cap on the aggregated batch itself so it could never grow that large again.</p>
<p>A few more rounds of testing turned up smaller, subtler correctness issues in the same area: log ordering could get scrambled between a page's batched writes and the service worker's own immediate ones, a corrupted or malformed persisted buffer could get the retry logic stuck trying the same broken write forever, and the "Clear log" button had a narrow race where an in-flight batch could resurrect entries the user had just wiped. Each of those was closed. This whole round of fixes <a href="https://github.com/gioxx/MarvellousSuspender/pull/472" target="_blank" rel="noopener noreferrer" class="">merged as PR #472</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-debug-page-unknown-status-that-never-got-better">The debug page: unknown status that never got better<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#the-debug-page-unknown-status-that-never-got-better" class="hash-link" aria-label="Direct link to The debug page: unknown status that never got better" title="Direct link to The debug page: unknown status that never got better" translate="no">​</a></h2>
<p>Separately from the log buffer, the debug page's tab profiler kept showing <code>unknown</code> for the status of certain tabs, indefinitely, surviving repeated manual reloads of the whole extension.</p>
<p>The cause: when a tab's content script genuinely stops responding (the page itself is still alive, just its script has died, a different failure mode from Chrome discarding a tab to save memory), recovering it requires TMS to re-inject and restart that script. The debug page's status check never attempted that recovery step, it did a single quick probe and gave up. Only the extension's own periodic background check ever did the real recovery work, and that check runs on its own schedule, independent of whatever the debug page happens to be showing you at the time.</p>
<p>The fix routed the debug page's checks through the same recovery-capable queue the background process already uses, instead of a shallow one-off probe, so a tab that needs re-injection actually gets it, and the debug page's own table now patches that row live once the real result comes back instead of leaving it stuck on a stale placeholder.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="an-unbounded-event-handler-and-an-unbounded-fan-out">An unbounded event handler and an unbounded fan-out<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#an-unbounded-event-handler-and-an-unbounded-fan-out" class="hash-link" aria-label="Direct link to An unbounded event handler and an unbounded fan-out" title="Direct link to An unbounded event handler and an unbounded fan-out" translate="no">​</a></h2>
<p>Two more issues, both specific to running with a lot of tabs open at once, also went into PR #472:</p>
<p>The debug page refreshes its tab table whenever the window regains focus. With no guard in place, rapid focus changes (multiple monitors, fast alt-tabbing) could trigger overlapping refreshes, each one repeating a full pass over every open tab. That was debounced to at most one refresh per second, with the in-flight run's result never silently dropped if the tab list changed while it was still running.</p>
<p>And the refresh itself, for every profile with more than a handful of tabs, used to fire one request per tab all at once with no cap, hundreds of simultaneous checks against the background process for a heavily-loaded profile. That was capped to a bounded number in flight at a time, spread out instead of bursting, without blocking the table from rendering while slower checks were still queued behind faster ones.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-crash-that-wouldnt-die">The crash that wouldn't die<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#the-crash-that-wouldnt-die" class="hash-link" aria-label="Direct link to The crash that wouldn't die" title="Direct link to The crash that wouldn't die" translate="no">​</a></h2>
<p>PR #472 merged. It fixed several real bugs. And going back to actually using TMS, reloading the extension, opening the debug page, browsing the tab list, it crashed again. Not eventually, not under some extreme stress test: within minutes, sometimes on nothing more than opening the debug page and looking around.</p>
<p>That is the point where a smaller team, or a less patient one, stops at "well, we fixed a bunch of real bugs, maybe it's better now" and ships it. We didn't, because the report was specific and reproducible, and specific reproducible reports deserve a specific reproducible answer, not a hopeful one.</p>
<p>The first real break came from <code>chrome://crashes</code> and the local Crashpad minidumps Chrome keeps on disk even after uploading them. Reading the crash annotations directly (no symbol server access needed, Crashpad embeds a surprising amount of plain-text diagnostic context in every dump) turned up two numbers that mattered: <code>view-count</code>/<code>web-frame-count</code> around 48–49, and <code>loaded-origin-0</code> pointing at TMS's own extension origin. Chrome puts every page sharing the same extension origin into one renderer process: every open <code>suspended.html</code>, plus the debug page itself, all sharing one process, one V8 heap, with a hard ceiling around 4GB regardless of how much physical RAM the machine actually has.</p>
<p>That heap was nearly full: <code>v8-oom-old-space-size</code> (regular JS objects) sat at a tiny ~18MB, while <code>v8-oom-memory-allocator-size</code> (backing store for large binary buffers) was pinned near the 4GB cap. Two theories followed from that, both genuinely tested, both genuinely fixed, and neither the actual answer:</p>
<ul>
<li class=""><strong>Favicon size.</strong> <code>gsFavicon.js</code> built each suspended tab's favicon at the source image's native resolution before scaling anything down, and some sites serve genuinely large "favicons" (a 512×512 apple-touch-icon reused as-is is common). Capped the working canvas to a sane maximum, and, since browsers already suspended before the fix had cached the oversized version, added a version stamp so the cache silently rebuilds at the new size instead of staying oversized forever.</li>
<li class=""><strong>The debug page's own <code>refreshLogs()</code>.</strong> It re-ran on every window focus event with no protection against overlapping calls, unlike the sibling function that debounces exactly this. Each run re-parsed the entire log buffer, including a full-buffer fetch that existed only to display a count. Fixed to coalesce concurrent calls into at most one in flight.</li>
</ul>
<p>Both fixes were correct and shipped. Neither stopped the crash. The tell was in the numbers: the same ~3.7–4GB ceiling kept showing up whether 28 suspended tabs were open or 49. If either theory were the real cause, more tabs should have meant more risk. It didn't. Something else was consuming memory at a rate tied to <em>how often the log buffer was written</em>, not to how many tabs happened to be open at the moment of the crash.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-actual-mechanism-a-broadcast-nobody-asked-for">The actual mechanism: a broadcast nobody asked for<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#the-actual-mechanism-a-broadcast-nobody-asked-for" class="hash-link" aria-label="Direct link to The actual mechanism: a broadcast nobody asked for" title="Direct link to The actual mechanism: a broadcast nobody asked for" translate="no">​</a></h2>
<p>Static analysis of crash dumps had said everything it could. The next step was live memory profiling: <code>chrome://inspect</code>, attached to the shared renderer process, taking heap snapshots at intervals while reproducing the crash, saving each one to disk immediately so a mid-recording crash couldn't take the evidence down with it.</p>
<p>The second snapshot, taken shortly before an actual crash, showed the real shape of the problem directly: dozens of near-duplicate strings, each roughly 6MB, each a full JSON-serialized copy of the log buffer, and their timestamps were <strong>hours old</strong>. Not fresh writes accumulating under load. Frozen, historical copies of the buffer, retained since early in the session, never released.</p>
<p>The mechanism, once we knew what to look for: <code>chrome.storage.onChanged</code> fires in <em>every context that has any listener registered for that storage area</em>, delivering a full copy of whatever changed, regardless of whether that context's own callback cares about the specific keys involved. <code>suspended.js</code> registers exactly such a listener, in every single suspended tab, for one small, entirely unrelated setting. Every time anything wrote to the log buffer (which, with <code>captureLogs</code> on, is constantly), Chrome dutifully constructed and delivered a multi-megabyte <code>oldValue</code>/<code>newValue</code> payload to every one of those listeners, in every suspended tab, all sharing that one renderer process. None of it released once the listener finished ignoring it.</p>
<p>This is not a bug in the sense of a typo or an off-by-one. It is <code>chrome.storage.onChanged</code> behaving exactly as documented. The log buffer's design, one shared blob in <code>chrome.storage.local</code>, read and written across dozens of contexts, was simply the wrong shape for that API's actual delivery semantics, and the more tabs (and the more logging) a session had, the more that mismatch cost, independent of the specific favicon size or refresh cadence either earlier theory had chased.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-fix-move-the-whole-log-buffer-to-indexeddb">The fix: move the whole log buffer to IndexedDB<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#the-fix-move-the-whole-log-buffer-to-indexeddb" class="hash-link" aria-label="Direct link to The fix: move the whole log buffer to IndexedDB" title="Direct link to The fix: move the whole log buffer to IndexedDB" translate="no">​</a></h2>
<p>The whole persistence layer moved from <code>chrome.storage.local</code> to IndexedDB, using the same database TMS already keeps for favicon and session data. Instead of one shared blob, the log buffer is now one record per entry. IndexedDB writes have no cross-context broadcast equivalent to <code>chrome.storage.onChanged</code>, and per-entry records mean every context, every suspended tab included, can write directly, without funneling through the service worker as a single designated writer the way the old design required.</p>
<p>A good deal of complexity the old blob-based design needed went away with it: the version-token optimistic-concurrency retry loop that guarded against two writers racing on one shared value, the 250ms incoming-message coalescing window from the earlier round of fixes, and the dedicated cross-context message action that carried log entries to the service worker in the first place. None of it is needed when every writer can safely touch its own record.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-review-caught-along-the-way">What review caught along the way<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#what-review-caught-along-the-way" class="hash-link" aria-label="Direct link to What review caught along the way" title="Direct link to What review caught along the way" translate="no">​</a></h2>
<p>Several rounds of automated review on the migration itself caught real, live issues before they shipped:</p>
<ul>
<li class="">A write failure being <em>reported</em> through the same logging pipe that had just failed, which could loop indefinitely under a persistent failure (a full disk, a corrupted database) instead of backing off and retrying normally.</li>
<li class="">Multiple contexts flushing independently meant insertion order didn't reliably match chronological order, fixed with a proper timestamp index, so "most recent" and "oldest to evict" both mean what they say.</li>
<li class="">A multi-entry write done as separate transactions per entry, which could leave a partial batch committed and then duplicated on retry after a failure partway through, now one atomic transaction per flush.</li>
<li class="">The "Clear log" button silently reporting success even when the underlying clear had failed.</li>
<li class="">The one-off cleanup of the <em>old</em> <code>chrome.storage.local</code> keys, running from a place that itself ran in every context: for a profile that had already accumulated a multi-megabyte buffer under the old design, that cleanup call was itself a <code>chrome.storage.local</code> mutation, and would have broadcast that same oversized payload to every suspended tab one more time, on exactly the code path meant to eliminate it. Moved to run once, from the service worker only.</li>
<li class="">Trimming the store back down to its cap, if triggered from the same per-context flush path the old design used, would let dozens of tabs each independently decide "trim needed" at once. Replaced with a single periodic <code>chrome.alarms</code> schedule, the same mechanism TMS already uses for backup and news-feed timing.</li>
</ul>
<p>And a real behaviour change worth naming rather than hiding: TMS declares <code>"incognito": "split"</code> in its manifest, so a regular window and an incognito one run fully separate extension instances. <code>chrome.storage.local</code> wasn't partitioned by that split (both instances shared one buffer under the old design), but IndexedDB is. A regular debug session can no longer see what happened in an incognito window. Bridging the two isn't practical without reintroducing some form of cross-context broadcast, which is the exact mechanism this whole migration exists to eliminate, so this is accepted as a known limitation rather than worked around.</p>
<p>Then live testing caught one more thing none of the automated review did: after adding that new timestamp index, the log view briefly showed "No entries" while the entry counter kept climbing normally. IndexedDB only re-runs its schema-upgrade step when the requested database version number goes <em>up</em>: a profile that had already opened the database at its current version earlier the same day, before the index existed, never got it added. A quick version bump forced the upgrade to actually apply. A good reminder that review catches a great deal, but nothing replaces someone actually reloading the extension and using it.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-couple-of-other-things-fixed-along-the-way">A couple of other things fixed along the way<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#a-couple-of-other-things-fixed-along-the-way" class="hash-link" aria-label="Direct link to A couple of other things fixed along the way" title="Direct link to A couple of other things fixed along the way" translate="no">​</a></h2>
<p>Chasing the same crash surfaced two more issues in adjacent code, both worth a brief mention even though they're not directly about the log buffer:</p>
<p>A queue used for retrying tab-initialization work during startup had a subtle timing gap: a job that legitimately needed several retries (completely normal when many tabs restore at once) could end up running for minutes with the extension's own startup-completion flag stuck <code>true</code> the whole time, silently disabling recovery behaviour. It now has a real overall time limit alongside its existing retry-count limit, generous enough not to punish normal retries, but no longer effectively unbounded.</p>
<p>And a favicon-related job that starts initializing a suspended tab could keep running against a tab that had already navigated away, been discarded, or closed mid-initialization, in a few different ways depending on exactly when that happened. Each of those was closed with a shared cancellation signal that the job checks at every step, rather than a growing pile of individual point-checks that could only ever catch the specific timing gap someone happened to find.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-this-leaves-things">Where this leaves things<a href="https://kb.marvellouscode.works/blog/tms903-stability-debug-page#where-this-leaves-things" class="hash-link" aria-label="Direct link to Where this leaves things" title="Direct link to Where this leaves things" translate="no">​</a></h2>
<p>None of this changes what TMS does for a normal user with <code>captureLogs</code> off, which is the overwhelming majority of installs. What it changes is whether the diagnostic tooling itself, and the extension underneath it, can be trusted to run for an extended period, under real load, without becoming the thing you have to reload the browser to escape from. That was the actual bar for this work, and every fix above, in both rounds, was driven by hitting it, not by a checklist.</p>
<p>If you are running a build with <code>captureLogs</code> on to help track down an issue and still see something behaving oddly, please <a href="https://github.com/gioxx/MarvellousSuspender/issues" target="_blank" rel="noopener noreferrer" class="">open an issue on GitHub</a> with a downloaded debug report attached. That is exactly the workflow that made this whole investigation possible in the first place.</p>
<div class="theme-admonition theme-admonition-info admonition_xJq3 alert alert--info"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 14 16"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg></span>info</div><div class="admonitionContent_BuS1"><p>Both rounds of fixes described above are merged (<a href="https://github.com/gioxx/MarvellousSuspender/pull/472" target="_blank" rel="noopener noreferrer" class="">#472</a> and <a href="https://github.com/gioxx/MarvellousSuspender/pull/473" target="_blank" rel="noopener noreferrer" class="">#473</a> on GitHub) and included in <strong>TMS 9.0.3</strong>, live on the Chrome Web Store. See the <a class="" href="https://kb.marvellouscode.works/blog/tms-release-9-0-3">9.0.3 release post</a> for the full picture.</p></div></div>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Bug</category>
        </item>
        <item>
            <title><![CDATA[9.0.3 in progress: a real fix for Drive backups disconnecting on Brave and Vivaldi]]></title>
            <link>https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token</link>
            <guid>https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token</guid>
            <pubDate>Tue, 25 Aug 2026 09:15:00 GMT</pubDate>
            <description><![CDATA[9.0.2's Brave/Vivaldi Drive fallback stopped the connect flow from hanging, but the underlying token it relied on was still short-lived and unreliable to renew. 9.0.3 replaces it with a proper refresh token.]]></description>
            <content:encoded><![CDATA[<p><a class="" href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#google-drive-connect-account-on-brave-and-vivaldi">9.0.2 shipped a fallback</a> for connecting Google Drive backup on Brave and Vivaldi, browsers where Chrome's own <code>chrome.identity.getAuthToken()</code> doesn't work. That fallback fixed the immediate problem: the connect button no longer hung indefinitely. It did not fully fix the underlying issue, and reports kept coming in of Drive accounts flipping back to "disconnected" after just one or two automatic backups. 9.0.3 replaces the fallback's mechanism entirely.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>TL;DR</div><div class="admonitionContent_BuS1"><ul>
<li class=""><strong>Only affects Drive backup on Brave and Vivaldi.</strong> Chrome users aren't affected at all.</li>
<li class="">The 9.0.2 fallback used a token that expired every hour and needed the browser's help to silently renew it, Brave and Vivaldi don't support that renewal reliably, so accounts kept disconnecting on their own.</li>
<li class="">9.0.3 replaces it with a long-lived token that renews itself directly, no browser dependency, no more surprise disconnects.</li>
<li class="">The token exchange goes through a small Cloudflare Worker we run (<a href="https://github.com/Marvellous-Codeworks/tms-oauth-proxy" target="_blank" rel="noopener noreferrer" class=""><code>tms-oauth-proxy</code></a>), so the OAuth client secret no longer ships inside the extension package.</li>
<li class=""><strong>If you already connected Drive on Brave/Vivaldi</strong>, you'll need to click <strong>Connect</strong> once more in Options → Backup after updating; after that, it just works.</li>
</ul></div></div>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-the-902-fallback-still-disconnected">Why the 9.0.2 fallback still disconnected<a href="https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token#why-the-902-fallback-still-disconnected" class="hash-link" aria-label="Direct link to Why the 9.0.2 fallback still disconnected" title="Direct link to Why the 9.0.2 fallback still disconnected" translate="no">​</a></h2>
<p>The fallback used <code>chrome.identity.launchWebAuthFlow()</code>, which on the first connection opens a real tab for you to sign in and grant access. What it returns is an <strong>implicit-flow access token</strong>, short-lived, about an hour, by design. Renewing it silently before it expires means calling <code>launchWebAuthFlow()</code> again with <code>prompt: 'none'</code>, no visible tab, no interaction, just a background request that depends entirely on the browser already holding an active Google session for that tab.</p>
<p>That dependency is exactly where it broke. Brave and Vivaldi don't maintain that ambient session reliably the way Chrome does, so the silent renewal call would fail once the hour was up, and the account looked disconnected from TMS's side even though nothing the user did caused it.</p>
<p>The root cause sits upstream, in Brave's own <code>chrome.identity</code> implementation, not in TMS. It's tracked in <a href="https://github.com/brave/brave-browser/issues/38066#issuecomment-5395066080" target="_blank" rel="noopener noreferrer" class="">brave-browser#38066</a>, still open as of this writing, no movement from Brave's side yet. We're not waiting on it: 9.0.3 works around it entirely on our end instead.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-903-does-instead">What 9.0.3 does instead<a href="https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token#what-903-does-instead" class="hash-link" aria-label="Direct link to What 9.0.3 does instead" title="Direct link to What 9.0.3 does instead" translate="no">​</a></h2>
<p>The fix is a proper move to <strong>authorization-code flow with PKCE</strong>. The practical difference: instead of a token that expires every hour and needs the browser's help to silently renew, one interactive consent (the same tab you already see the first time you connect) mints a long-lived <strong>refresh token</strong>, stored locally. Every renewal after that is a direct request to Google's token endpoint, no tab, no cookies, no dependency on whatever session state the browser happens to be holding onto at that moment.</p>
<p>This reuses the existing "Web application" OAuth client already registered for TMS (the same one used for <a class="" href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#google-drive-connect-account-on-brave-and-vivaldi">the 9.0.2 fallback</a>) rather than a new one. We looked at switching to a "Desktop app" client type instead, which Google documents as the more natural fit for an installed application, but tested it directly against the live authorization endpoint and confirmed it rejects the redirect URL format Chrome extensions are required to use. The existing client stays.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="if-you-already-connected-drive-on-brave-or-vivaldi">If you already connected Drive on Brave or Vivaldi<a href="https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token#if-you-already-connected-drive-on-brave-or-vivaldi" class="hash-link" aria-label="Direct link to If you already connected Drive on Brave or Vivaldi" title="Direct link to If you already connected Drive on Brave or Vivaldi" translate="no">​</a></h2>
<p>There is one unavoidable step for anyone who connected Drive through the 9.0.2 fallback already: no previous release could have stored a refresh token for you, because the mechanism didn't exist yet. Once your current short-lived session expires, roughly an hour after updating to 9.0.3, the next automatic backup attempt will fail once, and TMS will show the same "Drive disconnected" indicator it already shows for any auth problem.</p>
<p>The fix is a single click on <strong>Connect</strong> in Options → Backup, same as reconnecting for any other reason. After that one-time reconnect, you get the new, reliable renewal path with no further action needed, indefinitely, no more surprise disconnects after a couple of backups.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-client-secret-what-we-got-wrong-and-the-fix">The client secret: what we got wrong, and the fix<a href="https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token#the-client-secret-what-we-got-wrong-and-the-fix" class="hash-link" aria-label="Direct link to The client secret: what we got wrong, and the fix" title="Direct link to The client secret: what we got wrong, and the fix" translate="no">​</a></h2>
<p>An earlier draft of this post described shipping the OAuth client secret inside the extension package as a "known, accepted limitation", on the reasoning that a leak only lets a third party impersonate the app for a phishing consent screen, not touch any user's actual Drive data. That framing undersold the real risk.</p>
<p>The OAuth client TMS uses for this flow is registered as a "Web application" type, which by Google's own policy is expected to keep its client secret confidential, held server-side, never exposed. TMS has no server, so the secret was compiled straight into the extension package, and since a Chrome extension's <code>.crx</code>/<code>.zip</code> is trivially unpacked by anyone, it was effectively public the moment it shipped. The part we underweighted: this isn't just a phishing-blast-radius question, it's a policy compliance problem. Google can flag or suspend an OAuth client that doesn't meet its confidentiality expectations for its registered type, and that would break Drive backup for <em>every</em> TMS user at once, not just enable a narrow impersonation scenario.</p>
<p>We looked again at the client types Google exempts from this requirement, ones built for installed applications, like Chrome extensions, Desktop apps, iOS, and Android. Neither fits here: a "Chrome app" client only works with <code>chrome.identity.getAuthToken()</code>, the exact API that doesn't work on Brave and Vivaldi and is the whole reason this fallback exists, and a "Desktop app" client rejects the redirect URL format this flow has to use, confirmed directly against the live endpoint. So instead of swapping client types, we removed the need for the secret to be embedded at all.</p>
<p><strong><a href="https://github.com/Marvellous-Codeworks/tms-oauth-proxy" target="_blank" rel="noopener noreferrer" class=""><code>tms-oauth-proxy</code></a></strong> is a small Cloudflare Worker, free tier (at least for now), that holds the client secret server-side and does nothing but forward the token exchange to Google: the initial authorization-code grant, and every refresh_token renewal after that. TMS's own code never has the secret at all anymore, <code>gsBackup.js</code> calls the worker instead of Google's token endpoint directly. The worker handles only the exchange itself: the code or refresh token going to Google, and the tokens Google returns, pass through it without being stored. It never touches your Drive data, and TMS keeps the tokens in your own browser's storage as before. As part of shipping this, the previously-exposed secret was rotated in Google Cloud Console, so the earlier one is dead regardless.</p>
<p>This closes the gap the original "known, accepted limitation" note left open, cleanly, for zero added cost, rather than leaving it as a documented tradeoff.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-this-leaves-things">Where this leaves things<a href="https://kb.marvellouscode.works/blog/tms903-drive-pkce-refresh-token#where-this-leaves-things" class="hash-link" aria-label="Direct link to Where this leaves things" title="Direct link to Where this leaves things" translate="no">​</a></h2>
<p>If you're on Chrome, none of this affects you, <code>chrome.identity.getAuthToken()</code> already works there and this fallback never activates. If you're on Brave or Vivaldi and use Drive backup, this closes the gap that made 9.0.2's fix incomplete: one connection, one long-lived token, no more silent disconnects a couple of backups in.</p>
<div class="theme-admonition theme-admonition-info admonition_xJq3 alert alert--info"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 14 16"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg></span>info</div><div class="admonitionContent_BuS1"><p>Both pieces of this work are merged (<a href="https://github.com/gioxx/MarvellousSuspender/pull/440" target="_blank" rel="noopener noreferrer" class="">pull request #440</a> for the PKCE fallback, <a href="https://github.com/gioxx/MarvellousSuspender/pull/476" target="_blank" rel="noopener noreferrer" class="">pull request #476</a> for the <code>tms-oauth-proxy</code> move) and included in <strong>TMS 9.0.3</strong>, live on the Chrome Web Store. See the <a class="" href="https://kb.marvellouscode.works/blog/tms-release-9-0-3">9.0.3 release post</a> for the full picture.</p></div></div>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Bug</category>
        </item>
        <item>
            <title><![CDATA[9.0.2 also brings back the classic The Great Suspender artwork, as an option]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-classic-tgs-artwork</link>
            <guid>https://kb.marvellouscode.works/blog/tms-classic-tgs-artwork</guid>
            <pubDate>Sun, 09 Aug 2026 14:21:00 GMT</pubDate>
            <description><![CDATA[A new checkbox in Options → General lets you swap TMS's current mascot and icon set back to the original The Great Suspender artwork, app-wide.]]></description>
            <content:encoded><![CDATA[<p>The new mascot and icon set that shipped with TMS 9 has not landed well with everyone, <a class="" href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#the-generative-image-backlash">some of the feedback on 9.0.2 made that clear</a>. While that discussion continues, 9.0.2 also ships a direct, no-strings-attached answer for anyone who just wants the old look back: a checkbox.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="use-the-classic-the-great-suspender-artwork">Use the classic The Great Suspender artwork<a href="https://kb.marvellouscode.works/blog/tms-classic-tgs-artwork#use-the-classic-the-great-suspender-artwork" class="hash-link" aria-label="Direct link to Use the classic The Great Suspender artwork" title="Direct link to Use the classic The Great Suspender artwork" translate="no">​</a></h2>
<p>A new option in <strong>Options → General</strong>, "Use the classic The Great Suspender artwork instead of the new mascot", switches TMS's icons and illustrations back to the original The Great Suspender style, the artwork the project was originally built on, wherever a legacy version of the image exists.</p>
<p><img decoding="async" loading="lazy" alt="TMS Options page, General section, with the &amp;quot;Use the classic The Great Suspender artwork&amp;quot; checkbox enabled and the legacy suspendy mascot shown in the welcome panel" src="https://kb.marvellouscode.works/assets/images/tms-classic-tgs-artwork-options-00ac6ad1903c59ec12453a6c0f2a5378.webp" width="2994" height="1722" class="img_ev3q"></p>
<p>It is applied consistently, not just in one corner of the UI: the toolbar icon, the suspended-tab page's favicon fallback, and every extension page's own images and favicon all switch together, resolved through a single mapping so there is no mix-and-match between old and new art on different screens. A couple of illustrations that never existed in the original set (used for less common states) have no legacy equivalent, those keep using the new artwork regardless of the toggle.</p>
<p>Off by default, on-demand, reversible any time. No data migration, no restart required.</p>
<p>Full reference in the <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/settings#use-the-classic-the-great-suspender-artwork-instead-of-the-new-mascot">Settings docs</a>.</p>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Release</category>
            <category>Feature</category>
        </item>
        <item>
            <title><![CDATA[The Marvellous Suspender 9.0.2 - Always-suspend list, Drive OAuth fallback, favicon fix]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-release-9-0-2</link>
            <guid>https://kb.marvellouscode.works/blog/tms-release-9-0-2</guid>
            <pubDate>Wed, 05 Aug 2026 23:00:00 GMT</pubDate>
            <description><![CDATA[9.0.2 ships a new always-suspend list, a Google Drive OAuth fallback for Brave and Vivaldi, and a favicon fix, plus a full triage of the issue tracker and a concrete look at what's next.]]></description>
            <content:encoded><![CDATA[<p>TMS 9.0.2 is ready: one new list-based feature and a handful of confirmed bug fixes. It'll be submitted for Chrome Web Store review in a few days, not today, I'm taking a short break first for family time and some mental rest, so bear with the wait. The bigger news is behind the scenes anyway: every open issue on the tracker got triaged into an actual plan.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-new">What's new<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#whats-new" class="hash-link" aria-label="Direct link to What's new" title="Direct link to What's new" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="always-suspend-list">"Always suspend" list<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#always-suspend-list" class="hash-link" aria-label="Direct link to &quot;Always suspend&quot; list" title="Direct link to &quot;Always suspend&quot; list" translate="no">​</a></h3>
<p>A new list, right next to the whitelist in Settings, of URLs that always suspend after the normal timeout, even past the protections (pinned, audible, unsaved form input) that would otherwise keep a tab open indefinitely. Useful for something like a background Twitch or YouTube tab left playing audio that you still want suspended on schedule. Same matching rules as the whitelist (plain text or <code>/regex/</code>). Manual per-tab pauses and global protections (offline, charging, "never suspend") are still respected, this only overrides the passive automatic ones.</p>
<p>Named "always suspend" rather than "blacklist" to avoid the polarity confusion raised in the original request (<a href="https://github.com/gioxx/MarvellousSuspender/issues/103" target="_blank" rel="noopener noreferrer" class="">#103</a>). It also picked up its own <strong>"Test list"</strong> and <strong>"Suspend matching tabs now"</strong> buttons, mirroring the whitelist's existing test/wake pair, so you can check what matches or force an immediate suspend instead of waiting for the normal timeout.</p>
<p>Speaking of the whitelist: it's now called the <strong>allowlist</strong> everywhere in the UI (tooltips, popup, all 18 locales). Storage key and internal code are untouched, this was a copy pass, not a rename of the feature.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-fixed">What's fixed<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#whats-fixed" class="hash-link" aria-label="Direct link to What's fixed" title="Direct link to What's fixed" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="google-drive-connect-account-on-brave-and-vivaldi">Google Drive "Connect account" on Brave and Vivaldi<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#google-drive-connect-account-on-brave-and-vivaldi" class="hash-link" aria-label="Direct link to Google Drive &quot;Connect account&quot; on Brave and Vivaldi" title="Direct link to Google Drive &quot;Connect account&quot; on Brave and Vivaldi" translate="no">​</a></h3>
<p><code>chrome.identity.getAuthToken()</code> doesn't work on either browser, for different reasons: Brave attaches a custom URI scheme Google's backend rejects outright and shows a raw <code>Error 400: invalid_request</code> page; Vivaldi disables Google sign-in entirely, so the callback just never fires and the connect flow hangs with no feedback. TMS now falls back to <code>chrome.identity.launchWebAuthFlow()</code>, races the original method against a timeout so a Vivaldi-style hang surfaces as a failure instead of hanging forever, and remembers which method worked per install so later calls skip straight to it (<a href="https://github.com/gioxx/MarvellousSuspender/issues/420" target="_blank" rel="noopener noreferrer" class="">#420</a>).</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="suspended-tabs-stuck-with-the-default-favicon-after-a-restart">Suspended tabs stuck with the default favicon after a restart<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#suspended-tabs-stuck-with-the-default-favicon-after-a-restart" class="hash-link" aria-label="Direct link to Suspended tabs stuck with the default favicon after a restart" title="Direct link to Suspended tabs stuck with the default favicon after a restart" translate="no">​</a></h3>
<p>The startup check that repairs favicons and titles only ran from events some Chromium builds (notably Brave) never fire after a normal restart, leaving suspended tabs stuck with the generic icon until clicked. A storage-based sentinel now catches this on every service worker wake instead (<a href="https://github.com/gioxx/MarvellousSuspender/issues/397" target="_blank" rel="noopener noreferrer" class="">#397</a>). Thanks to @pbc-commits for the investigation and root-cause writeup.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="allow-access-to-file-urls-toggle-missing">"Allow access to file URLs" toggle missing<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#allow-access-to-file-urls-toggle-missing" class="hash-link" aria-label="Direct link to &quot;Allow access to file URLs&quot; toggle missing" title="Direct link to &quot;Allow access to file URLs&quot; toggle missing" translate="no">​</a></h3>
<p>Chrome only shows this toggle when the manifest declares <code>file://</code> host access, which TMS never did. Added as an optional host permission, on-demand like <code>downloads</code>/<code>identity</code>, no access granted until you flip it yourself (<a href="https://github.com/gioxx/MarvellousSuspender/issues/393" target="_blank" rel="noopener noreferrer" class="">#393</a>, <a href="https://github.com/gioxx/MarvellousSuspender/issues/416" target="_blank" rel="noopener noreferrer" class="">#416</a>, <a href="https://github.com/gioxx/MarvellousSuspender/issues/267" target="_blank" rel="noopener noreferrer" class="">#267</a>).</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="suspended-page-waited-on-the-hotkey-label-before-becoming-clickable">Suspended page waited on the hotkey label before becoming clickable<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#suspended-page-waited-on-the-hotkey-label-before-becoming-clickable" class="hash-link" aria-label="Direct link to Suspended page waited on the hotkey label before becoming clickable" title="Direct link to Suspended page waited on the hotkey label before becoming clickable" translate="no">​</a></h3>
<p>Restoring a suspended tab was gated behind a <code>chrome.commands.getAll()</code> call to fetch the shortcut-key label for display, purely cosmetic, but slow enough to make the click handler feel unresponsive. The page now becomes interactive first and fills in the hotkey label after (<a href="https://github.com/gioxx/MarvellousSuspender/issues/320" target="_blank" rel="noopener noreferrer" class="">#320</a>).</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="claim-by-default-option">"Claim by default" option<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#claim-by-default-option" class="hash-link" aria-label="Direct link to &quot;Claim by default&quot; option" title="Direct link to &quot;Claim by default&quot; option" translate="no">​</a></h3>
<p>Shortened the option label and moved its explanation into a tooltip instead of a long parenthetical (<a href="https://github.com/gioxx/MarvellousSuspender/issues/151" target="_blank" rel="noopener noreferrer" class="">#151</a>), then reworded again after that first pass still left it meaningless without opening the tooltip: it's now "Claim tabs suspended by other extensions", says what it does without requiring a hover.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="manual-backup-cooldown-had-a-hole-in-it">Manual backup cooldown had a hole in it<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#manual-backup-cooldown-had-a-hole-in-it" class="hash-link" aria-label="Direct link to Manual backup cooldown had a hole in it" title="Direct link to Manual backup cooldown had a hole in it" translate="no">​</a></h3>
<p>The 30-second cooldown after a manual "Backup now" was only ever enforced as a per-page debounce local to the Backup page's own button. The popup has its own "Backup now" menu item, with no cooldown and no shared state with the page, so triggering from both let you fire off backups back-to-back. The cooldown now lives in <code>gsBackup.performManualBackup()</code> itself, tracked in session storage so it's enforced no matter which UI triggers it; the popup shows a live countdown and disables the item if a cooldown from the other surface is already running.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="always-suspend-list-showing-a-literal-undefined">"Always suspend" list showing a literal "undefined"<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#always-suspend-list-showing-a-literal-undefined" class="hash-link" aria-label="Direct link to &quot;Always suspend&quot; list showing a literal &quot;undefined&quot;" title="Direct link to &quot;Always suspend&quot; list showing a literal &quot;undefined&quot;" translate="no">​</a></h3>
<p>Ironic given this ships in the same release that introduced the list: upgrading from an install that predates it left the textarea showing the literal word "undefined" instead of being empty, because settings only got backfilled with new defaults on a brand-new install, not on existing ones. Settings now backfill any missing keys on every load, not just first run.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="locale-drift-closed">Locale drift closed<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#locale-drift-closed" class="hash-link" aria-label="Direct link to Locale drift closed" title="Direct link to Locale drift closed" translate="no">​</a></h3>
<p>A source-string edit had quietly broken Crowdin's fuzzy match on 7 strings, reverting them to English across all 16 non-English/Italian locales, on top of a handful of genuinely new keys. Both are fixed and locales are back in sync. Added <code>scripts/check-locales.js</code> (<code>npm run check-locales</code>) so this kind of drift is caught locally before it ships, not the fix itself, but worth having.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="also-in-this-release">Also in this release<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#also-in-this-release" class="hash-link" aria-label="Direct link to Also in this release" title="Direct link to Also in this release" translate="no">​</a></h2>
<p>A handful of smaller things that don't need their own section:</p>
<ul>
<li class=""><strong>Bulk-delete Drive backups per device.</strong> The Backup page already grouped Drive files by device when more than one machine backs up to the same account, but clearing out one device's files meant deleting them one by one. A "Delete all" button next to each device's group heading now handles it in one go, with the same confirm-before-delete modal as single-file deletes.</li>
<li class=""><strong>Extension description reworded</strong> to match the tone used everywhere else TMS is described: "Free your memory. Suspend the tabs you don't need, right now."</li>
<li class=""><strong>The Backup page now shows which Drive OAuth method is active</strong> for the install (<code>getAuthToken</code> vs. the <code>launchWebAuthFlow</code> fallback from above), as a quiet second line under the "TMS Backups" folder name, mainly useful for support.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-bigger-job-triaging-the-whole-backlog">The bigger job: triaging the whole backlog<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#the-bigger-job-triaging-the-whole-backlog" class="hash-link" aria-label="Direct link to The bigger job: triaging the whole backlog" title="Direct link to The bigger job: triaging the whole backlog" translate="no">​</a></h2>
<p>9.0.2 was the small part of today's work. The real effort went into going through <strong>every open issue on the tracker</strong>, 56 of them, most untouched for months, and sorting each one into an actual plan instead of a flat list.</p>
<p>The outcome: 31 issues now sit in a concrete milestone (9.0.2, 9.0.3, 9.1.0, 9.2.0, or 10.0.0), scoped by what they actually need, a quick fix, a real feature, or a design spike, rather than by how old they are. The remaining 25 are genuinely unclear: duplicates to merge, reports that need reproduction steps, or requests that need a decision before they can be scoped at all, and they'll get worked through the same way.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-other-side-of-a-release-reviews-and-inbox">The other side of a release: reviews and inbox<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#the-other-side-of-a-release-reviews-and-inbox" class="hash-link" aria-label="Direct link to The other side of a release: reviews and inbox" title="Direct link to The other side of a release: reviews and inbox" translate="no">​</a></h2>
<p>Version 9 and its two bugfix releases were rolled out alongside a redesign, changes to permissions, and a new backup feature, and the reviews posted since then on the Chrome Web Store have made it clear that there are a lot of new features to take in all at once in a single update—and, to be honest, we were somewhat expecting this, though perhaps we hadn't factored in the "<em>unwarranted hostility</em>" that is often part of the game in the open-source world (and this is certainly no excuse, because respect, empathy, and tact always come first). It's worth examining them carefully, rather than simply highlighting only the positive aspects (which, fortunately, are there as well).</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-does-it-need-all-these-permissions-now">"Why does it need all these permissions now?"<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#why-does-it-need-all-these-permissions-now" class="hash-link" aria-label="Direct link to &quot;Why does it need all these permissions now?&quot;" title="Direct link to &quot;Why does it need all these permissions now?&quot;" translate="no">​</a></h3>
<p>This was the loudest thread, a run of 1-star reviews within hours of each other listing the new permission prompt verbatim: <em>"Read and change all your data on all websites," "Read and change your browsing history on all your signed-in devices," "Manage your downloads," "View and manage your tab groups"</em>. Read cold, with no context, that's a reasonable thing to be alarmed by. One reviewer put it plainly:</p>
<blockquote>
<p>"Now, the app itself is wonderful, but I am fearful about saying yes to so many permissions. [...] Message to the Devs: please provide an explanatory blog post on why you need so many permissions. I will happily update this to 5* if the reasons are convincing".</p>
</blockquote>
<p>The post already exists, <a class="" href="https://kb.marvellouscode.works/blog/tms9-public-permissions-faq">the 9.0 permissions FAQ</a>, and explains each permission against the feature that needs it (<code>downloads</code> for local backup, <code>identity</code> for Drive backup, the broad host permissions for the scripting-based form/scroll detection that predates 9.0). The problem is it was never linked from the Chrome Web Store update notes, so nobody hit it unless they went looking, and one reviewer said as much (<em>"Looks like all the permissions are legitimate. But in the update notice, I didn't see this link"</em>). That's on us, not on the reviewers: the explanation being technically correct and effectively invisible is the same as not having written it. The CWS listing will link it directly going forward.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-generative-image-backlash">The generative-image backlash<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#the-generative-image-backlash" class="hash-link" aria-label="Direct link to The generative-image backlash" title="Direct link to The generative-image backlash" translate="no">​</a></h3>
<p>The new suspended-tab illustration set uses AI-generated art, and the reaction has been unambiguous and consistent, from a 1-star review (<em>"So now I am forced to see garbage genAI images on every suspended tab?"</em>), to a Chinese-language review calling the new icon 丑爆了 (bluntly, "hideously ugly"), to a calm, direct email from a long-time user asking us to either revert to the old artwork or commission an actual illustrator, because shipping AI art "will make it appear cheap and rushed to the users who don't see all the code and scripts you designed for it". That last framing is the one worth sitting with: it's not really about the pixels, it's about what the choice signals for a project that otherwise puts real engineering effort into every release. This is going back into discussion, no decision made here, but the signal is too consistent across independent channels to wave off as noise.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>Can you draw better than an AI?</div><div class="admonitionContent_BuS1"><p>If you're reading this and use Photoshop (or any other graphics program, it doesn't matter) every day for a living, why not give us a hand? Neither of us is an illustrator, but we needed to give TMS's graphics a fresh look, so we set out to design a mascot that would be visually appealing. We worked on it with the help of AI and came up with a result we hoped you'd like.</p><p>If you think you can do better, please contact us! Send an email to <a href="mailto:gioxx@marvellouscode.works" target="_blank" rel="noopener noreferrer" class="">gioxx@marvellouscode.works</a> and let's talk about it :-)</p></div></div>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="stop-changing-the-ui">"Stop changing the UI"<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#stop-changing-the-ui" class="hash-link" aria-label="Direct link to &quot;Stop changing the UI&quot;" title="Direct link to &quot;Stop changing the UI&quot;" translate="no">​</a></h3>
<p>A smaller but genuine thread: the redesign changed the suspended-tab screen and, more concretely, removed a state cue some users relied on daily, the toolbar icon used to visibly change when a tab was paused from suspension, now you have to click it to check. One review called this out at length, and re-submitted the same text three times over two days, which reads less like spam and more like someone who really wanted it seen. That one is a legitimate regression report, not a taste complaint, and it's going on the backlog to fix, not just to note.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="real-bugs-found-in-the-noise">Real bugs found in the noise<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#real-bugs-found-in-the-noise" class="hash-link" aria-label="Direct link to Real bugs found in the noise" title="Direct link to Real bugs found in the noise" translate="no">​</a></h3>
<p>Sorting the sharp tone from the substance, three reports didn't match anything already tracked and got opened as issues today:</p>
<ul>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/issues/426" target="_blank" rel="noopener noreferrer" class="">#426</a></strong>: a user reported the extension's settings page and keyboard shortcuts becoming unavailable entirely after updating, no repro yet, but too specific to dismiss.</li>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/issues/427" target="_blank" rel="noopener noreferrer" class="">#427</a></strong>: automatic local backup apparently writing outside the configured <code>tms-backups</code> folder, with filenames drifting to Chrome's own <code>download.json</code>, <code>download.json (1)</code>, <code>(2)</code>... pattern and the configured file-count limit being ignored.</li>
<li class=""><strong><a href="https://github.com/gioxx/MarvellousSuspender/issues/428" target="_blank" rel="noopener noreferrer" class="">#428</a></strong>: a report that recent updates broke Gmail's own delete/move actions, symptoms that don't persist until a manual refresh. Needs isolating, but too precise a description to be a red herring.</li>
</ul>
<p>A fourth pattern, suspended tabs vanishing without a trace after a crash, showed up again in this batch too, but that one's not new: it matches <a href="https://github.com/gioxx/MarvellousSuspender/issues/396" target="_blank" rel="noopener noreferrer" class="">#396</a> and <a href="https://github.com/gioxx/MarvellousSuspender/issues/402" target="_blank" rel="noopener noreferrer" class="">#402</a>, already on the board.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="on-the-tone">On the tone<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#on-the-tone" class="hash-link" aria-label="Direct link to On the tone" title="Direct link to On the tone" translate="no">​</a></h3>
<p>Some of these criticisms were quite harsh. "Shameful", "crazy", "a terrible, truly terrible change", it's really a lot to read all at once, and a couple of reviews were clearly emotional outbursts rather than concrete reports. That's fine; that's what the reviews section is for, and it doesn't change how the actual bugs mentioned above are handled. But it's also worth stating clearly that the never-out-of-style tactic of posting a barrage of very negative reviews immediately after a release that simultaneously changed permissions, graphics, and the user interface is, in itself, a sign: bundling so many visible changes into a single update has made it much harder for anyone to distinguish at first glance between "this is a real problem" and "this is different, and I don't like the difference".<br>
<!-- -->Change is always <em>scary</em>. This is a lesson on the order of changes to keep in mind for future updates, as well as for this specific case.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="comments-are-now-open-on-the-kb">Comments are now open on the KB<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#comments-are-now-open-on-the-kb" class="hash-link" aria-label="Direct link to Comments are now open on the KB" title="Direct link to Comments are now open on the KB" translate="no">​</a></h2>
<p>Speaking of feedback: every post on the Marvellous Codeworks KB, this one included, now has a comment section right at the bottom. No Chrome Web Store review box, no GitHub account required. If you've got a bug report, a question, or an opinion on any of the above, that's the place for it now, we'll be reading.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-next-concretely">What's next, concretely<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-2#whats-next-concretely" class="hash-link" aria-label="Direct link to What's next, concretely" title="Direct link to What's next, concretely" translate="no">​</a></h2>
<ul>
<li class=""><strong>9.0.3</strong>: right after this release, already-scoped quick wins, default branch rename (<code>master</code> to <code>main</code>), a favicon-cleanup follow-up, a handful of small long-standing UX requests, plus one item needing a feasibility spike before work starts, a battery/charging-aware suspend timeout.</li>
<li class=""><strong>9.1.0</strong>: platform reach, an Edge Add-ons Store listing and Group Policy support for managed deployments, plus standalone improvements: a pause button, staggered session restore (so restoring 40 tabs at once doesn't hammer the browser), and a rework of the YouTube screenshot capture path.</li>
<li class=""><strong>9.2.0</strong>: a Session Manager rework, collapsing/reordering windows, deleting a single window without touching the rest, bulk export, plus lifecycle settings like auto-unsuspend on restart, auto-cleanup of old sessions, and an option to disable session tracking entirely.</li>
<li class=""><strong>10.0.0</strong>: no near-term date, this is where larger architecture-level changes land, per-tab-group settings is the first candidate.</li>
</ul>
<p>None of this is set in stone, milestones will keep shifting as issues get re-scoped, but there's now an actual sequence instead of one long undifferentiated backlog.</p>
<p>I wish you all the best on your journey.</p>
<p><em>Giovanni</em></p>
<hr>
<p><em>Full changelog on GitHub: <a href="https://github.com/gioxx/MarvellousSuspender/releases/tag/v9.0.2" target="_blank" rel="noopener noreferrer" class="">v9.0.2 release</a></em></p>]]></content:encoded>
            <category>Release</category>
            <category>The Marvellous Suspender</category>
        </item>
        <item>
            <title><![CDATA[The Marvellous Suspender 9.0.1: on-demand permissions, and closing the gaps from 9.0.0]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-release-9-0-1</link>
            <guid>https://kb.marvellouscode.works/blog/tms-release-9-0-1</guid>
            <pubDate>Tue, 04 Aug 2026 12:00:00 GMT</pubDate>
            <description><![CDATA[9.0.1 delivers on what we promised in the permissions FAQ post: downloads and identity are now requested on demand instead of upfront, the news feed has an opt-out, and the Drive-only local file mystery is explained right on the page.]]></description>
            <content:encoded><![CDATA[<p>We said it was coming in <a class="" href="https://kb.marvellouscode.works/blog/tms9-public-permissions-faq">the last post</a>, and it's here. 9.0.1 is a direct response to <a href="https://github.com/gioxx/MarvellousSuspender/issues/411" target="_blank" rel="noopener noreferrer" class="">issue #411</a> 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.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="permissions-are-now-on-demand-not-upfront">Permissions are now on demand, not upfront<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-1#permissions-are-now-on-demand-not-upfront" class="hash-link" aria-label="Direct link to Permissions are now on demand, not upfront" title="Direct link to Permissions are now on demand, not upfront" translate="no">​</a></h2>
<p>This is the headline change. In 9.0.0, <code>downloads</code> and <code>identity</code> were declared as regular permissions, so Chrome asked for both the moment you updated, whether or not you ever touched the backup feature. That's exactly what triggered the disable-and-reprompt dialog most of you saw, and exactly what <a href="https://github.com/gioxx/MarvellousSuspender/issues/411" target="_blank" rel="noopener noreferrer" class="">issue #411</a> called out as "substantially overprivileged for users who do not use backups."</p>
<p>Starting with 9.0.1:</p>
<ul>
<li class=""><strong><code>downloads</code></strong> is only requested the moment you toggle <strong>Enable automatic backup</strong> on, in <a class="" href="https://kb.marvellouscode.works/docs/TMS/pages/backup-sync">Backup &amp; Sync</a>. Leave it off, and TMS never asks.</li>
<li class=""><strong><code>identity</code></strong> is only requested when you click <strong>Connect</strong> to link a Google account for Drive backup. Never click it, and TMS never asks.</li>
</ul>
<p>If you already had backup enabled under 9.0.0, you won't see anything new, Chrome keeps permissions you already granted when a later update moves them from required to optional. No re-prompt, nothing to redo.</p>
<p>Full breakdown on the <a class="" href="https://kb.marvellouscode.works/docs/TMS/permissions#optional-permissions-requested-on-demand">permissions page</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-quieter-way-to-be-reminded-backup-exists">A quieter way to be reminded backup exists<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-1#a-quieter-way-to-be-reminded-backup-exists" class="hash-link" aria-label="Direct link to A quieter way to be reminded backup exists" title="Direct link to A quieter way to be reminded backup exists" translate="no">​</a></h2>
<p>Session backup is still, by a wide margin, the most requested feature TMS has ever shipped, and the vast majority of you haven't turned it on yet. Rather than push harder, 9.0.1 adds a deliberately low-key nudge: a small amber badge on the toolbar icon, a banner in the popup, and a note on the Backup &amp; Sync page, all pointing at the same place, all easy to dismiss.</p>
<p><strong>Remind me in 10 days</strong> snoozes it. A permanent <strong>I'm not interested, stop reminding me</strong> checkbox on the Backup &amp; Sync page turns it off entirely. No pop-ups, no repeated interruptions, just a quiet signal that stays out of your way once you've told it to.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="news-feed-opt-out">News feed opt-out<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-1#news-feed-opt-out" class="hash-link" aria-label="Direct link to News feed opt-out" title="Direct link to News feed opt-out" translate="no">​</a></h2>
<p>The daily background check against <code>marvellouscode.works</code> for TMS-related posts (feeding the in-extension News page) had no way to turn off. It does now: <strong>Enable news feed</strong> in Settings → General, on by default. Turn it off and the fetch alarm is cleared immediately, along with the <strong>News</strong> entry in the sidebar.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-drive-only-local-file-explained">The Drive-only local file, explained<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-1#the-drive-only-local-file-explained" class="hash-link" aria-label="Direct link to The Drive-only local file, explained" title="Direct link to The Drive-only local file, explained" translate="no">​</a></h2>
<p>If your backup destination is Google Drive but you still occasionally see a file appear in your Downloads folder, that's not a bug. On browser shutdown, TMS always writes a local safety-net copy first, a Drive upload isn't reliable in that narrow shutdown window, so the file gets queued and uploaded on the next startup instead, then cleaned up automatically once that upload succeeds. This was true since 9.0.0 but never explained anywhere in the UI, <a href="https://github.com/gioxx/MarvellousSuspender/issues/411" target="_blank" rel="noopener noreferrer" class="">issue #411</a> was right to flag it. It's now spelled out directly on the Backup &amp; Sync page.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="in-app-permissions-transparency">In-app permissions transparency<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-1#in-app-permissions-transparency" class="hash-link" aria-label="Direct link to In-app permissions transparency" title="Direct link to In-app permissions transparency" translate="no">​</a></h2>
<p>Two smaller, related additions: a one-time banner on the Settings and Backup &amp; Sync pages explaining the permissions change above (with a link to the docs), and a persistent reference note on the Backup &amp; Sync page for anyone who lands there later and wants the short version without digging through a blog archive. Going forward, this is where permission changes get explained, not just here.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-were-not-doing">What we're not doing<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-1#what-were-not-doing" class="hash-link" aria-label="Direct link to What we're not doing" title="Direct link to What we're not doing" translate="no">​</a></h2>
<p>Backup content encryption came up as a suggestion in issue #411 too. We're not adding it, not in 9.0.1 and not planning to. Backup files carry the same level of protection the manual "Export session" feature has had since 2017 (plain JSON, no encryption), nothing on your machine or your own Drive <code>appdata</code> folder is exposed to anyone else by that choice, and we'd rather keep the feature simple than bolt on a passphrase system nobody asked for twice.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="thanks">Thanks<a href="https://kb.marvellouscode.works/blog/tms-release-9-0-1#thanks" class="hash-link" aria-label="Direct link to Thanks" title="Direct link to Thanks" translate="no">​</a></h2>
<p>To everyone who pushed back on 9.0.0's permission model instead of just uninstalling and moving on: this release exists because you took the time to write it up instead. That's the whole reason <a href="https://github.com/gioxx/MarvellousSuspender/issues/411" target="_blank" rel="noopener noreferrer" class="">issue #411</a> got a direct answer instead of a shrug, and it's why the fix landed this fast.</p>
<p>If something's still off, <a href="https://github.com/gioxx/MarvellousSuspender/issues" target="_blank" rel="noopener noreferrer" class="">open an issue</a> or use the <a href="https://marvellouscode.works/tms/report" target="_blank" rel="noopener noreferrer" class="">report form</a>. We read all of it.</p>
<hr>
<p><em>Full changelog on GitHub: <a href="https://github.com/gioxx/MarvellousSuspender/releases/tag/v9.0.1" target="_blank" rel="noopener noreferrer" class="">v9.0.1 release</a></em></p>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Release</category>
            <category>Announcement</category>
        </item>
        <item>
            <title><![CDATA[TMS 9 is public now: about that permissions dialog, and where your sessions went]]></title>
            <link>https://kb.marvellouscode.works/blog/tms9-public-permissions-faq</link>
            <guid>https://kb.marvellouscode.works/blog/tms9-public-permissions-faq</guid>
            <pubDate>Mon, 03 Aug 2026 20:30:00 GMT</pubDate>
            <description><![CDATA[TMS 9 has finished rolling out to everyone. Some of you hit a scary re-enable dialog, some raised sharp technical questions about backup permissions, some lost sessions to an unrelated Chrome bug. Here's what's actually going on, and what's landing in 9.0.1.]]></description>
            <content:encoded><![CDATA[<p>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.</p>
<!-- -->
<img src="https://kb.marvellouscode.works/assets/images/permissions-reenable-dialog-c1d30d460e4d39a43c1921a81ad360d9.png" alt="Chrome dialog: 'The newest version of The Marvellous Suspender has been disabled because it requires more permissions', listing read/change data on all websites, read/change browsing history, manage downloads, view and manage tab groups, with Re-enable and Cancel buttons" style="max-width:420px">
<p>If you saw this dialog, Chrome disabled TMS on update and is asking you to confirm the new permissions before turning it back on. That's expected, and it's Chrome doing its job. Here's why each one is there, and what to do if you'd rather not grant all of them.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-the-new-permissions">Why the new permissions<a href="https://kb.marvellouscode.works/blog/tms9-public-permissions-faq#why-the-new-permissions" class="hash-link" aria-label="Direct link to Why the new permissions" title="Direct link to Why the new permissions" translate="no">​</a></h2>
<p>Two of the permissions listed, <code>downloads</code> and <code>identity</code>, are new in 9.x. Both exist for exactly one feature: <strong>session backup</strong>, the single most requested thing in TMS's entire history, now finally shipped, either to a local folder or to your own Google Drive.</p>
<ul>
<li class=""><strong><code>downloads</code></strong> lets TMS write backup files to a <code>tms-backups/</code> folder inside your Downloads, and clean up old ones automatically. TMS never reads anything in your Downloads folder beyond the files it wrote itself.</li>
<li class=""><strong><code>identity</code></strong> is used only if you choose Google Drive as your backup destination. It gets an OAuth token to talk to Drive, TMS never sees your Google password, and the token exchange is handled entirely by Chrome.</li>
<li class="">The Drive backup, if enabled, is scoped to <code>drive.appdata</code>, a hidden, app-only folder that isn't visible in your regular Drive and isn't reachable by any other app.</li>
</ul>
<p>Full breakdown, including exactly what changed since 8.x, is on the <a class="" href="https://kb.marvellouscode.works/docs/TMS/permissions#optional-permissions-requested-on-demand">permissions page</a>.</p>
<p><strong>The important part: both permissions sit dormant until you actually turn on automatic backups in Backup &amp; Sync.</strong> If you never enable that feature, TMS requests no Drive authentication and writes nothing to Downloads. We're aware that Chrome asks for the permission up front regardless, at install/update time, not at first use, which is exactly the kind of thing that reads as scarier than it is. We hear that, and we're working on a setting to opt out of backups and their reminders entirely, which should let us drop these permissions for anyone who doesn't want the feature. That's not shipped yet, it's actively in progress, and we'll cover it here once it lands.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-deeper-questions-and-whats-landing-in-901">The deeper questions, and what's landing in 9.0.1<a href="https://kb.marvellouscode.works/blog/tms9-public-permissions-faq#the-deeper-questions-and-whats-landing-in-901" class="hash-link" aria-label="Direct link to The deeper questions, and what's landing in 9.0.1" title="Direct link to The deeper questions, and what's landing in 9.0.1" translate="no">​</a></h2>
<p><a href="https://github.com/gioxx/MarvellousSuspender/issues/411" target="_blank" rel="noopener noreferrer" class="">Issue #411</a> went further than "why the new permissions," with some sharper technical points worth answering here too, not just in a GitHub thread:</p>
<ul>
<li class=""><strong><code>downloads</code> is requested unconditionally, even if you never enable local backup.</strong> Fair. It's a static manifest permission right now instead of one requested at runtime when you actually turn on local auto-backup. Moving it to on-demand is going into 9.0.1, so most people who don't use backups won't see this prompt at all.</li>
<li class=""><strong>Backup files are plain JSON, and base64 isn't encryption.</strong> Correct, base64 there only builds a <code>data:</code> URL so a service worker can hand the file to <code>chrome.downloads.download()</code> (blob URLs don't survive service worker restarts), it was never meant as protection. Worth noting: it's the same level of protection the manual "Export session" feature has had since 2017, so this isn't a new risk 9.0.0 introduced. Optional passphrase encryption for backup content is a reasonable ask and it's on the list.</li>
<li class=""><strong>A Drive-only configuration can still write a local file.</strong> Also correct. On browser shutdown, TMS runs an emergency backup that always writes locally first, because a Drive upload in that shutdown window isn't reliable, the service worker can get killed mid-request. If your destination is Drive, that file gets queued and uploaded on next startup. A deliberate reliability trade-off, but not currently explained anywhere in the UI. That's getting a note, plus cleanup of the local copy once the queued Drive upload succeeds.</li>
<li class=""><strong>A daily request to <code>kb.marvellouscode.works/blog/rss.xml</code>.</strong> Yes, an alarm every 24h feeding the sidebar News page. The host is already declared in the manifest, nothing hidden, but there's no way to turn it off today. A toggle is coming.</li>
</ul>
<p>One more thing worth admitting straight: the permissions page and the posts covering this were published before 9.0.0 went live, but nowhere the extension itself points to them. That's the actual gap, not the timing. Going forward, whenever a release changes permissions, the options page and changelog will link directly to what changed and why, instead of relying on people finding the blog on their own.</p>
<p>None of this changes what TMS does with your data today, nothing leaves your machine except to your own Drive <code>appdata</code> folder, but the scoping and the missing opt-outs were legitimate gaps, and 9.0.1 is where they get closed.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="it-requires-too-many-permissions-now-wtf">"It requires too many permissions now, wtf?"<a href="https://kb.marvellouscode.works/blog/tms9-public-permissions-faq#it-requires-too-many-permissions-now-wtf" class="hash-link" aria-label="Direct link to &quot;It requires too many permissions now, wtf?&quot;" title="Direct link to &quot;It requires too many permissions now, wtf?&quot;" translate="no">​</a></h2>
<img src="https://kb.marvellouscode.works/assets/images/review-3-stars-permissions-0f717504f365e9c183c70826f89c8dca.png" alt="Chrome Web Store review, 3 stars: 'It requires too many permissions now, wtf?'" style="max-width:460px">
<p>Fair reaction from the outside, and exactly why the section above exists. Short version: nothing new is silently collecting or shipping your data anywhere. <code>tabs</code>, <code>storage</code>, <code>history</code>, <code>contextMenus</code>, <code>alarms</code>, <code>favicon</code>, <code>scripting</code>, and <code>tabGroups</code> were all already there in 8.x, doing the same jobs they always did. <code>downloads</code> and <code>identity</code> are the two genuinely new ones, and they only exist because of the backup feature described above.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="major-updates-too-frequently-cause-suspended-web-pages-to-disappear-please-do-not-always-change-how-the-ui-looks">"Major updates too frequently cause suspended web pages to disappear. Please do not always change how the UI looks."<a href="https://kb.marvellouscode.works/blog/tms9-public-permissions-faq#major-updates-too-frequently-cause-suspended-web-pages-to-disappear-please-do-not-always-change-how-the-ui-looks" class="hash-link" aria-label="Direct link to &quot;Major updates too frequently cause suspended web pages to disappear. Please do not always change how the UI looks.&quot;" title="Direct link to &quot;Major updates too frequently cause suspended web pages to disappear. Please do not always change how the UI looks.&quot;" translate="no">​</a></h2>
<img src="https://kb.marvellouscode.works/assets/images/review-3-stars-major-updates-7dd07f66b5e3f81d124e0e80e99c1a68.png" alt="Chrome Web Store review, 3 stars: 'Major updates too frequently cause suspended web pages to disappear. Please do not always change how the UI looks. It takes time for users to get used to it before you change it again.'" style="max-width:460px">
<p>Two separate points here, and we want to be honest about both.</p>
<p>On the UI: yes, TMS 9 changed how every settings page looks. That was intentional and covered at length in <a class="" href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#not-everyone-will-love-it-and-thats-fine">the launch post</a>, it needed doing, but we know it's disruptive and we're not planning another full repaint anytime soon.</p>
<p>On suspended pages disappearing during updates: that one worries us more, because it shouldn't happen from a TMS update alone, and it's worth separating from a specific incident we're actively helping someone recover from right now.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="when-sessions-actually-vanish-its-usually-not-the-update-itself">When sessions actually vanish, it's usually not the update itself<a href="https://kb.marvellouscode.works/blog/tms9-public-permissions-faq#when-sessions-actually-vanish-its-usually-not-the-update-itself" class="hash-link" aria-label="Direct link to When sessions actually vanish, it's usually not the update itself" title="Direct link to When sessions actually vanish, it's usually not the update itself" translate="no">​</a></h2>
<p>We got a report of exactly this, sessions gone after an update, and dug into it in <a href="https://github.com/gioxx/MarvellousSuspender/issues/410" target="_blank" rel="noopener noreferrer" class="">issue #410</a>. TMS pins a fixed extension ID in its manifest, so a normal update should never touch your saved sessions in <code>chrome.storage</code>/IndexedDB, they live at that same ID before and after.</p>
<p>What we found instead: Chrome occasionally flags an extension as "corrupted" after an update and offers a repair/reinstall flow, and that repair flow can reset the extension's local storage even though the ID doesn't change. That's a Chrome-side quirk, not something TMS's update logic triggers. Cold comfort if it happens to you, we know, so if you ever hit it:</p>
<ol>
<li class="">Check the extension's History/Manage Sessions page and the Recovery page first, sometimes the data is still there and just needs a poke.</li>
<li class="">Compare the extension ID in <code>chrome://extensions</code> (Developer mode on) against your backed-up <code>IndexedDB</code> folder name, if you have one.</li>
<li class="">If you have a raw IndexedDB backup, tab URLs are recoverable as plain text even from the binary <code>.ldb</code>/<code>.log</code> files, full recovery steps are in the issue thread.</li>
</ol>
<p>If this happens to you, open an issue (or use the <a href="https://marvellouscode.works/tms/report" target="_blank" rel="noopener noreferrer" class="">no-account report form</a>) with what you're seeing, we'll walk through recovery with you the same way.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="we-read-everything">We read everything<a href="https://kb.marvellouscode.works/blog/tms9-public-permissions-faq#we-read-everything" class="hash-link" aria-label="Direct link to We read everything" title="Direct link to We read everything" translate="no">​</a></h2>
<p>As said before, we mean it: reviews, star ratings, GitHub issues, all of it gets read, and this post exists because of exactly that. If something about TMS 9 is bothering you, permissions, the redesign, anything else, <a href="https://github.com/gioxx/MarvellousSuspender/issues" target="_blank" rel="noopener noreferrer" class="">open an issue</a> or use the <a href="https://marvellouscode.works/tms/report" target="_blank" rel="noopener noreferrer" class="">report form</a>. We'd rather answer it directly than have it sit in a star rating we can't reply to.</p>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Release</category>
            <category>Announcement</category>
        </item>
        <item>
            <title><![CDATA[Road to TMS 9: we made it, and it's rolling out Monday!]]></title>
            <link>https://kb.marvellouscode.works/blog/road-to-tms9-launch</link>
            <guid>https://kb.marvellouscode.works/blog/road-to-tms9-launch</guid>
            <pubDate>Thu, 30 Jul 2026 23:00:00 GMT</pubDate>
            <description><![CDATA[TMS 9 has cleared Google's review. Starting Monday, August 3rd, the new version begins rolling out on the Chrome Web Store. A look back at the ride, the chats with Rob, the community that showed up, the new site, and what actually changes for you.]]></description>
            <content:encoded><![CDATA[<p>Five weeks ago we opened this series with <a class="" href="https://kb.marvellouscode.works/blog/road-to-tms9-visual-redesign">a new look for a new era</a>. Google just cleared v9.0.0 for review, and starting <strong>Monday morning, August 3rd</strong>, the rollout to the Chrome Web Store begins. This is the last stop on the road.</p>
<img src="https://kb.marvellouscode.works/assets/images/suspendy-summer-vacation-e12524d906044ae8393b6a7b2ff7ccd7.webp" alt="Suspendy Guy in Hawaiian shirt, sunglasses, and sandals, holding a tropical cocktail" style="float:right;margin:0 0 1rem 1.5rem;width:180px">
<p>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.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-actually-shipped">What actually shipped<a href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#what-actually-shipped" class="hash-link" aria-label="Direct link to What actually shipped" title="Direct link to What actually shipped" translate="no">​</a></h2>
<ul>
<li class=""><strong>Session backup and restore</strong> (arguably the single most requested feature, since the dawn of time), local or Google Drive, on a schedule or on demand, multi-device aware.</li>
<li class="">A Tab Health page that scans your suspended tabs and repairs the Tab Groups restart bug on Chrome, Edge, and Brave with one click (the underlying bug is fixed now, but we kept the tooling around and available on demand, just in case).</li>
<li class="">A News feed that pulls straight from this blog into the extension's sidebar.</li>
<li class="">A visual redesign that finally makes every settings page look like it belongs to the same product.</li>
<li class="">Sixteen languages brought back up to parity after being left behind for who knows how long.</li>
</ul>
<p>None of that happened in a straight line, and none of it happened alone.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-chats-with-rob">The chats with Rob<a href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#the-chats-with-rob" class="hash-link" aria-label="Direct link to The chats with Rob" title="Direct link to The chats with Rob" translate="no">​</a></h2>
<p>Rob and I don't work in the same office, the same country, or even close to the same timezone half the time. Most of TMS 9 got decided in a Slack channel, at hours that made sense for neither of us, arguing about whether a permission scope was too aggressive, whether a setting needed a tooltip, whether "Restore from backup" should live under Sessions or Backup. Small questions, but the kind that decide whether an extension feels considered or just shipped.</p>
<p>The Great-er Tab Discarder (TGD) and The Marvellous Suspender (TMS) are separate projects with separate codebases, but Marvellous Codeworks only works because there are two of us pulling in the same direction, checking each other's blind spots, and occasionally telling the other one an idea is bad before it ships. TMS 9 is better for it, and we hope to do the same for TGD soon.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-community-that-showed-up">The community that showed up<a href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#the-community-that-showed-up" class="hash-link" aria-label="Direct link to The community that showed up" title="Direct link to The community that showed up" translate="no">​</a></h2>
<p>TMS 9 also has two first-time contributors in the changelog: <a href="https://github.com/MatrixNeoKozak" target="_blank" rel="noopener noreferrer" class="">@MatrixNeoKozak</a>, who refactored the storage layer to drop unnecessary JSON serialization, and <a href="https://github.com/iGhost" target="_blank" rel="noopener noreferrer" class="">@iGhost</a>, who added the option to preserve YouTube playback position on suspend, a small feature, requested and built by someone who actually hit the problem (something I never personally needed, for what it's worth). That is exactly how an open-source project is supposed to grow: not just bug reports, but pull requests from people who decided to fix the thing themselves.</p>
<p>On top of that, sixteen locales got AI-assisted translation passes to close gaps that had been sitting there for versions (Claude had free rein here). They are not perfect. If you read TMS in your language and something sounds off, <a href="https://crowdin.com/project/tms" target="_blank" rel="noopener noreferrer" class="">Crowdin</a> is open and corrections from native speakers are exactly what closes that gap for good.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="reporting-an-issue-without-a-github-account">Reporting an issue without a GitHub account<a href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#reporting-an-issue-without-a-github-account" class="hash-link" aria-label="Direct link to Reporting an issue without a GitHub account" title="Direct link to Reporting an issue without a GitHub account" translate="no">​</a></h2>
<p>For years, the only way to tell us something was broken was to open a GitHub issue, which meant a GitHub account, which meant a wall a lot of people simply weren't willing to climb over just to report a bug. We kept hearing about problems secondhand, in reviews, in Reddit threads, never where we could actually act on them.</p>
<p><a href="https://marvellouscode.works/tms/report" target="_blank" rel="noopener noreferrer" class="">marvellouscode.works/tms/report</a> aims to fix that. Fill in a form, no sign-up, no account, and it opens a proper GitHub issue on your behalf, correctly labeled, with the fields we actually need to reproduce the problem. You get a status link back to follow along, we get a real, actionable report instead of a one-star review that just says "stopped working."</p>
<p>And on that note: we do read everything, including what shows up directly on the Chrome Web Store. Star ratings, written reviews, support requests left in that little review box, all of it gets read. We keep an eye on GitHub Issues specifically because that is where we actually track and act on things, verifying odd behavior, following up on requests, closing things out once they're fixed, but a review left on the Store is not shouting into a void either.</p>
<div class="theme-admonition theme-admonition-note admonition_xJq3 alert alert--secondary"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 14 16"><path fill-rule="evenodd" d="M6.3 5.69a.942.942 0 0 1-.28-.7c0-.28.09-.52.28-.7.19-.18.42-.28.7-.28.28 0 .52.09.7.28.18.19.28.42.28.7 0 .28-.09.52-.28.7a1 1 0 0 1-.7.3c-.28 0-.52-.11-.7-.3zM8 7.99c-.02-.25-.11-.48-.31-.69-.2-.19-.42-.3-.69-.31H6c-.27.02-.48.13-.69.31-.2.2-.3.44-.31.69h1v3c.02.27.11.5.31.69.2.2.42.31.69.31h1c.27 0 .48-.11.69-.31.2-.19.3-.42.31-.69H8V7.98v.01zM7 2.3c-3.14 0-5.7 2.54-5.7 5.68 0 3.14 2.56 5.7 5.7 5.7s5.7-2.55 5.7-5.7c0-3.15-2.56-5.69-5.7-5.69v.01zM7 .98c3.86 0 7 3.14 7 7s-3.14 7-7 7-7-3.12-7-7 3.14-7 7-7z"></path></svg></span>note</div><div class="admonitionContent_BuS1"><p>The web report form is experimental. It exists to lower the barrier for people who won't create a GitHub account just to tell us something is broken, not to replace GitHub entirely. If it ever gets abused, spam, bad-faith noise, whatever form that takes, it's the first thing we'll turn off, and reporting will go back to being GitHub accounts opening Issues under their own name, full stop.</p></div></div>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-documentation-site-built-from-scratch">A documentation site built from scratch<a href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#a-documentation-site-built-from-scratch" class="hash-link" aria-label="Direct link to A documentation site built from scratch" title="Direct link to A documentation site built from scratch" translate="no">​</a></h2>
<p>The old TMS wiki lived on the GitHub repo, half-finished, out of date in places, and honestly not the kind of thing you'd send someone to if you wanted them to actually understand the extension. It's disabled now.</p>
<p>In its place: <a class="" href="https://kb.marvellouscode.works/docs/intro">kb.marvellouscode.works/docs</a>, built from the ground up on Docusaurus, page by page, primarily for TMS 9 (though really designed to cover everything that ends up under the Marvellous Codeworks umbrella). Every settings page has its own article, Settings, Sessions, Backup, Tab Health, Quick Actions, Keyboard Shortcuts, News, About, explaining what every toggle actually does, not just what it's labeled. There's a dedicated page on <a class="" href="https://kb.marvellouscode.works/docs/TMS/permissions">permissions</a>, spelling out why TMS asks for what it asks for, and what changed with the narrower Drive scope in this release. FAQ included. Nothing hidden in a stale wiki page nobody updated since 2019.</p>
<p>We built it, page by page, deciding what actually needed explaining versus what was obvious enough to skip. The <code>marvellouscode.works</code> domain has actually been sitting registered for almost a year now, it just took weeks and weeks of actual writing, restructuring, and rewriting to turn it into the site, the docs, and the report flow you can use today.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="everything-changes-nothing-changes">Everything changes. Nothing changes.<a href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#everything-changes-nothing-changes" class="hash-link" aria-label="Direct link to Everything changes. Nothing changes." title="Direct link to Everything changes. Nothing changes." translate="no">​</a></h2>
<p>TMS 9 looks different, is organized differently, backs itself up differently, and speaks more languages correctly than it used to. That is the "everything changes" part, and it took a full rewrite of the settings pages, a new backup system, and a lot of late chats with Rob to get there.</p>
<p>The "nothing changes" part is simpler: TMS still exists to take tabs your browser is hoarding in memory and put them to sleep until you actually need them again. That was true the day <a class="" href="https://kb.marvellouscode.works/blog/the-marvellous-suspender-hello-world">The Great Suspender got rescued</a>, it was true through the Manifest V3 rewrite, and it is still true in v9.0.0. Every feature in this release, Tab Health, backups, the redesign, exists to protect that one job, not to replace it.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="not-everyone-will-love-it-and-thats-fine">Not everyone will love it, and that's fine<a href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#not-everyone-will-love-it-and-thats-fine" class="hash-link" aria-label="Direct link to Not everyone will love it, and that's fine" title="Direct link to Not everyone will love it, and that's fine" translate="no">​</a></h2>
<p>We're perfectly aware that not everyone is going to be thrilled with the new look. Change is rarely comfortable, and a redesign this size, new fonts, new colors, new layout on every single page, is exactly the kind of thing some people will need time to get used to, or just won't like at all. That's part of growing a project, it's part of the deal.</p>
<p>We still believe the repaint was necessary, and we think it's only the first big step. There are more ideas in the pipeline, and there are plenty of problems and feature requests already sitting in GitHub Issues that we intend to work through to keep pushing TMS forward. We're listening, we take feedback and constructive criticism seriously, that's the whole point of open source in the first place.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-next">What's next<a href="https://kb.marvellouscode.works/blog/road-to-tms9-launch#whats-next" class="hash-link" aria-label="Direct link to What's next" title="Direct link to What's next" translate="no">​</a></h2>
<p>Google's review is done, the changelog is final, and the rollout starts Monday morning, August 3rd. Chrome Web Store updates roll out gradually rather than to everyone at once, so don't panic if you don't see v9.0.0 the second you check, it'll reach you within the normal update window. This series is officially done. Thank you for reading along the whole way, for testing feature branches, for opening issues, for the pull requests, and for the patience.</p>
<p>See you on the other side, in v9.0.0.</p>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Road to TMS 9</category>
            <category>Release</category>
            <category>Announcement</category>
        </item>
        <item>
            <title><![CDATA[Road to TMS 9: watching the Tab Health repair work, live, on Brave]]></title>
            <link>https://kb.marvellouscode.works/blog/road-to-tms9-tab-health-repair</link>
            <guid>https://kb.marvellouscode.works/blog/road-to-tms9-tab-health-repair</guid>
            <pubDate>Fri, 03 Jul 2026 15:30:00 GMT</pubDate>
            <description><![CDATA[A quick look at TMS 9's Tab Health page catching and repairing broken grouped tabs on Brave, the same recovery logic we described in the Chrome 150 post, this time in action.]]></description>
            <content:encoded><![CDATA[<p>We spent the last few posts chasing a Chromium regression across three browsers: it <a class="" href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-149-bug">broke grouped tabs on Chrome 149</a>, <a class="" href="https://kb.marvellouscode.works/blog/tms-tab-groups-edge-chromium-bug">reached Edge</a> shortly after, and was finally <a class="" href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed">fixed upstream in Chrome 150</a>. That last post also introduced the plan for <strong>Brave</strong>, which does not follow Chrome's release schedule and might stay affected for a while: TMS 9's new Tab Health page can detect and repair the broken tabs on demand, without waiting for Brave to catch up.</p>
<p>This week we actually ran that repair on a Brave profile with tab groups in a broken state, and it is worth showing rather than just describing.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="scan-tabs">Scan Tabs<a href="https://kb.marvellouscode.works/blog/road-to-tms9-tab-health-repair#scan-tabs" class="hash-link" aria-label="Direct link to Scan Tabs" title="Direct link to Scan Tabs" translate="no">​</a></h2>
<p>The Tab Health page opens with a single button. Nothing happens until you ask for it.</p>
<p><img decoding="async" loading="lazy" alt="TMS 9 Tab Health page on Brave, before scanning, just the Scan Tabs button" src="https://kb.marvellouscode.works/assets/images/tms9-tab-health-brave-scan-566a58c0af37b3dae247793d23c450d7.webp" width="1400" height="472" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-the-scan-found">What the scan found<a href="https://kb.marvellouscode.works/blog/road-to-tms9-tab-health-repair#what-the-scan-found" class="hash-link" aria-label="Direct link to What the scan found" title="Direct link to What the scan found" translate="no">​</a></h2>
<p>Clicking <strong>Scan Tabs</strong> walks through every tab and reports back. On this Brave profile, out of 28 tabs, TMS found 5 suspended tabs, 20 cached favicons, and <strong>21 grouped tabs in a broken state</strong>, flagged specifically as the Tab Groups bug.</p>
<p>That number is the point of this post. On Brave, those 21 tabs would otherwise sit there as blank <code>chrome://newtab/</code> pages until someone clicked the browser Back button on each one, one at a time. Instead, a <strong>Repair 21 grouped tab(s)</strong> button appears right below the scan results.</p>
<p>One click later: "Restoring favicons... 21 tabs. Done. Re-scan to verify grouped tabs are back to their suspended state." All 21 tabs recovered in a single pass, matched back to their original suspended URLs by window order and tab index, the Brave-specific recovery path described in the <a class="" href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed#for-brave-and-edge-users">Chrome 150 post</a>.</p>
<p><img decoding="async" loading="lazy" alt="TMS 9 Tab Health page on Brave, after scanning and repairing, scan results showing 21 grouped tabs in broken state, followed by the repair progress and completion message" src="https://kb.marvellouscode.works/assets/images/tms9-tab-health-brave-repair-d1718fc5cfcfee3d6ca73621321bc738.webp" width="1400" height="812" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-this-matters-for-brave-users-specifically">Why this matters for Brave users specifically<a href="https://kb.marvellouscode.works/blog/road-to-tms9-tab-health-repair#why-this-matters-for-brave-users-specifically" class="hash-link" aria-label="Direct link to Why this matters for Brave users specifically" title="Direct link to Why this matters for Brave users specifically" translate="no">​</a></h2>
<p>Chrome shipped the real fix in version 150. Whether and when Brave aligns with it is out of our hands, Brave tracks upstream Chromium on its own schedule, and there is no guarantee it lands quickly. If it does, this repair simply becomes unnecessary, the same way it already is for Chrome 150 users.</p>
<p>If it does not, TMS 9 gives Brave users a real answer instead of a manual workaround: open the Tab Health page, click Scan Tabs, and if it finds broken grouped tabs, click Repair. No side-loaded companion extension, no clicking Back on every tab, no waiting on a browser vendor's release notes.</p>
<div class="theme-admonition theme-admonition-warning admonition_xJq3 alert alert--warning"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.893 1.5c-.183-.31-.52-.5-.887-.5s-.703.19-.886.5L.138 13.499a.98.98 0 0 0 0 1.001c.193.31.53.501.886.501h13.964c.367 0 .704-.19.877-.5a1.03 1.03 0 0 0 .01-1.002L8.893 1.5zm.133 11.497H6.987v-2.003h2.039v2.003zm0-3.004H6.987V5.987h2.039v4.006z"></path></svg></span>warning</div><div class="admonitionContent_BuS1"><p>TMS 9 is still in development. The screenshots in this post come from a build running on the <code>feature/session-backup</code> branch, not a public release. <strong>Do not side-load TMS 9 branches yourself</strong>, they share the same extension ID as the Chrome Web Store version, and doing so would overwrite your production installation. Wait for the official release.</p></div></div>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Road to TMS 9</category>
        </item>
        <item>
            <title><![CDATA[Chrome 150 fixes the Tab Groups bug, and here is what changed in TMS]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed</link>
            <guid>https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed</guid>
            <pubDate>Tue, 30 Jun 2026 23:00:00 GMT</pubDate>
            <description><![CDATA[Chrome 150.0.7871.47 ships the browser-side fix for the tab group restore regression that broke suspended tabs since version 149. We removed the TMS startup workarounds, but kept the recovery logic where it matters most.]]></description>
            <content:encoded><![CDATA[<p>When Chrome 149 introduced a regression that silently discarded suspended tabs inside tab groups on every browser restart, TMS shipped a workaround in <a class="" href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-149-bug">version 8.1.4</a>. When the same regression reached Microsoft Edge, <a class="" href="https://kb.marvellouscode.works/blog/tms-tab-groups-edge-chromium-bug">we addressed that too</a>. We knew from the start that these were stopgap measures, the right fix had to come from the browser itself.</p>
<p>It is now here. <strong>Chrome 150.0.7871.47</strong> ships the browser-side patch for <a href="https://crbug.com/522338670" target="_blank" rel="noopener noreferrer" class="">crbug.com/522338670</a>. 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.</p>
<p>Here is what that means for TMS, and what we decided to do with the workaround code.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-we-removed-from-the-startup-path">What we removed from the startup path<a href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed#what-we-removed-from-the-startup-path" class="hash-link" aria-label="Direct link to What we removed from the startup path" title="Direct link to What we removed from the startup path" translate="no">​</a></h2>
<p>The TMS 8.1.4 workaround lived entirely in the extension's startup sequence. Every time the browser launched, TMS would:</p>
<ol>
<li class="">Scan all tabs and cache suspended URLs for grouped tabs as Chrome assigned group IDs.</li>
<li class="">Detect grouped suspended tabs that Chrome marked as discarded before the user could click them.</li>
<li class="">Re-create those tabs in-place, restore their group membership, and remove the broken originals.</li>
<li class="">Handle late <code>onReplaced</code> events that fired after the startup window closed (the Chrome and Edge variant of the bug).</li>
<li class="">For Brave, which doesn't fire <code>onReplaced</code> at all, match broken <code>chrome://newtab/</code> grouped tabs against the last saved session by window order and tab index, then recreate them.</li>
</ol>
<p>With Chrome 150 restoring grouped tabs correctly, all of this runs for nothing on every single startup. Worse, if Chrome and TMS both try to recreate the same tab, the interaction is unpredictable. So we disabled the entire startup path.</p>
<p>The code is still there, commented out in <code>gsSession.js</code> and <code>background.js</code>, clearly marked with <code>// DISABLED FOR TESTING: Chrome 150 Tab Groups fix</code>. If a future Chrome update regresses this behavior, re-enabling it takes minutes.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-we-kept-and-where">What we kept, and where<a href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed#what-we-kept-and-where" class="hash-link" aria-label="Direct link to What we kept, and where" title="Direct link to What we kept, and where" translate="no">​</a></h2>
<img src="https://kb.marvellouscode.works/img/suspendy-guy-doctor.webp" alt="Suspendy Guy: Health" style="float:right;margin:0 0 1rem 1.5rem;width:180px">
<p>Disabling startup recovery does not mean abandoning users who hit broken grouped tabs. It means moving the recovery to the right place: <strong>the Tab Health page</strong>.</p>
<p>The Tab Health page (<code>health.html</code>) is TMS's existing on-demand diagnostic tool. You open it, click Scan Tabs, and TMS checks your suspended tabs for issues, missing favicons, stale cache entries, tabs that haven't fully loaded. It reports what it finds and offers a targeted action to fix it.</p>
<p>We added a new check to this scan: <strong>grouped tabs in broken state</strong>. The scan now detects two failure modes:</p>
<ul>
<li class=""><strong>Chrome / Edge path</strong>: a grouped suspended tab is in a discarded state. This means Chrome started the session restore but did not complete it correctly, leaving the tab with its suspended URL intact but inactive. TMS can re-create the tab in-place, restore its group, and remove the broken copy, without the user having to click anything manually.</li>
<li class=""><strong>Brave path</strong>: a grouped tab is showing <code>chrome://newtab/</code> instead of any content. Brave does not fire the <code>onReplaced</code> events that Chrome and Edge use, so the broken URL is gone. TMS recovers the suspended URL by matching the tab's position (window order and tab index) against the last saved session.</li>
</ul>
<p>If the scan finds zero broken grouped tabs, which will be the case for every Chrome 150+ user, it shows <code>0 ✓</code> and moves on. If it finds any, a <strong>Repair grouped tab(s)</strong> button appears as the first action, above the existing favicon checks, because a structurally broken tab is a more urgent problem than a missing favicon.</p>
<p>The recovery logic itself is identical to what the startup path used. It is just no longer running automatically on every launch.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-this-split-makes-sense">Why this split makes sense<a href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed#why-this-split-makes-sense" class="hash-link" aria-label="Direct link to Why this split makes sense" title="Direct link to Why this split makes sense" translate="no">​</a></h2>
<p>The startup workaround had to be aggressive by design: it ran before the user could interact with any tab, because a single click on a broken grouped tab in Chrome's session restore was enough to lose the suspended URL permanently. That aggression was justified when the bug was active. Now that Chrome fixes it natively, running the same code at startup becomes unnecessary noise, and potentially a source of conflicts if Chrome's own restore logic and TMS's recreate logic both fire on the same tab.</p>
<p>Moving recovery to the health page shifts it from "runs automatically every time, no matter what" to "runs when the user explicitly asks." That is the right model for a workaround that is no longer expected to be needed.</p>
<p>The event-driven handlers, the ones that hooked into <code>onReplaced</code> and <code>onUpdated</code> during the startup window, cannot be replicated outside the startup context, so those remain commented out in the background script. They are not lost; they are preserved exactly where they need to be if we ever want to reactivate them.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="for-brave-and-edge-users">For Brave and Edge users<a href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed#for-brave-and-edge-users" class="hash-link" aria-label="Direct link to For Brave and Edge users" title="Direct link to For Brave and Edge users" translate="no">​</a></h2>
<p>The browser-side fix shipped in Chrome 150. Brave and Edge follow their own Chromium release schedules, so the patch may arrive at different times for those browsers.</p>
<ul>
<li class=""><strong>Brave users</strong>: the Brave path in the health page recovery remains active and will work on any Brave version. If you restart Brave and notice grouped tabs showing as new tabs, open the Tab Health page and run a scan.</li>
<li class=""><strong>Edge users</strong>: Edge 149+ has shown symptoms of the same regression. Once the Chromium 150 patch reaches Edge's stable channel, you will be in the same position as Chrome users today. Until then, the health page recovery is available if you need it.</li>
</ul>
<p>We hope the other Chromium-based browsers catch up with this fix quickly. But if they don't, once <strong>TMS 9</strong> is available you will be able to rely on the new Tab Health page recovery to fix broken grouped tabs on demand, without waiting for a browser-side patch.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="summary">Summary<a href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-150-fixed#summary" class="hash-link" aria-label="Direct link to Summary" title="Direct link to Summary" translate="no">​</a></h2>
<table><thead><tr><th>What</th><th>Before (TMS 8.1.4)</th><th>After (TMS + Chrome 150)</th></tr></thead><tbody><tr><td>Chrome grouped tab restore</td><td>Broken, TMS fixed at startup</td><td>Fixed natively by Chrome 150</td></tr><tr><td>Startup workaround</td><td>Active on every launch</td><td>Disabled (code preserved as comments)</td></tr><tr><td>Manual recovery</td><td>Not available</td><td>Tab Health page → Scan Tabs</td></tr><tr><td>Brave recovery</td><td>Active at startup</td><td>Tab Health page → Scan Tabs</td></tr><tr><td>Edge recovery</td><td>Active at startup (8.1.5+)</td><td>Tab Health page → Scan Tabs</td></tr></tbody></table>
<p>If you are on Chrome 150 and everything is working: nothing to do. If you ever hit broken grouped tabs again, on any browser, open the Tab Health page and let TMS sort it out.</p>
<hr>
<p><em>Related posts: <a class="" href="https://kb.marvellouscode.works/blog/tms-tab-groups-chrome-149-bug">TMS &amp; Chrome 149: the original bug report</a> · <a class="" href="https://kb.marvellouscode.works/blog/tms-tab-groups-edge-chromium-bug">TMS &amp; Microsoft Edge: the Chromium regression hits Edge too</a></em></p>
<p><em>GitHub issues: <a href="https://github.com/gioxx/MarvellousSuspender/issues/369" target="_blank" rel="noopener noreferrer" class="">#369</a> · <a href="https://github.com/gioxx/MarvellousSuspender/issues/374" target="_blank" rel="noopener noreferrer" class="">#374</a></em></p>]]></content:encoded>
            <category>Bug</category>
            <category>News</category>
            <category>The Marvellous Suspender</category>
            <category>Announcement</category>
            <category>Road to TMS 9</category>
        </item>
        <item>
            <title><![CDATA[Under the hood: replacing abandoned libraries in TMS 9]]></title>
            <link>https://kb.marvellouscode.works/blog/tms-dependency-cleanup</link>
            <guid>https://kb.marvellouscode.works/blog/tms-dependency-cleanup</guid>
            <pubDate>Fri, 26 Jun 2026 23:00:00 GMT</pubDate>
            <description><![CDATA[The next TMS update quietly replaces two aging third-party libraries, one abandoned since 2021, one still stuck on a 2020 release candidate. Here is why it matters and what we are asking the community.]]></description>
            <content:encoded><![CDATA[<p>TMS 9 is shaping up to be one of the most significant releases in the extension's history, if you have been following along, you already know about the automatic session backups and the Google Drive integration we covered in the previous posts. But not all of the work that goes into a release shows up in the changelog. Some of the most important changes happen completely out of sight, and this one is a good example of that. We replaced two third-party libraries that had been silently aging inside the extension, and we want to be transparent about what changed and why.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-is-a-third-party-library-and-why-should-you-care">What is a "third-party library" and why should you care?<a href="https://kb.marvellouscode.works/blog/tms-dependency-cleanup#what-is-a-third-party-library-and-why-should-you-care" class="hash-link" aria-label="Direct link to What is a &quot;third-party library&quot; and why should you care?" title="Direct link to What is a &quot;third-party library&quot; and why should you care?" translate="no">​</a></h2>
<p>TMS is not written from scratch. Like most software, it relies on a handful of external libraries, small pieces of code written by other developers that handle specific tasks so we do not have to reinvent the wheel. These libraries live inside the extension you install, and their health matters: an abandoned library means bugs get no fixes, known vulnerabilities go unpatched, and compatibility with future browser versions is not guaranteed.</p>
<p>Until now, TMS included two such libraries that were overdue for attention.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="dbjs-a-quietly-abandoned-dependency">db.js: a quietly abandoned dependency<a href="https://kb.marvellouscode.works/blog/tms-dependency-cleanup#dbjs-a-quietly-abandoned-dependency" class="hash-link" aria-label="Direct link to db.js: a quietly abandoned dependency" title="Direct link to db.js: a quietly abandoned dependency" translate="no">​</a></h2>
<p><strong>db.js</strong>, written by Aaron Powell, is a small wrapper around the browser's IndexedDB storage engine. TMS uses IndexedDB to remember your suspended tabs, saved sessions, favicons, and screenshot previews. db.js was responsible for every read, write, and query against that database.</p>
<p>The problem: development on db.js effectively stopped in 2021. The npm package has been frozen at version 0.15.0 for years. No bug fixes, no security patches, no updates for changes in browser behavior. We were shipping dead code, and dead code carries risk.</p>
<p>We replaced db.js with <strong><a href="https://github.com/jakearchibald/idb" target="_blank" rel="noopener noreferrer" class="">idb</a></strong>, the IndexedDB wrapper maintained by Jake Archibald (a Google engineer who literally helped write the browser storage specs). idb is:</p>
<ul>
<li class="">Actively maintained, currently at version 8</li>
<li class="">Widely used across the web platform ecosystem</li>
<li class="">Lean, well-tested, and licensed under ISC (permissive open source)</li>
</ul>
<p>From your perspective as a user, <strong>nothing changes</strong>. Your sessions, your suspended tabs, your settings, all of it is stored the same way in IndexedDB. The only difference is that the code that reads and writes your data is now backed by a healthy, modern library instead of an abandoned one.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="html2canvas-from-a-2020-release-candidate-to-a-stable-release">html2canvas: from a 2020 release candidate to a stable release<a href="https://kb.marvellouscode.works/blog/tms-dependency-cleanup#html2canvas-from-a-2020-release-candidate-to-a-stable-release" class="hash-link" aria-label="Direct link to html2canvas: from a 2020 release candidate to a stable release" title="Direct link to html2canvas: from a 2020 release candidate to a stable release" translate="no">​</a></h2>
<p>The second change is smaller in scope but still worth mentioning. <strong>html2canvas</strong>, the library TMS uses to generate the screenshot preview shown on suspended tab pages, was pinned at version <strong>1.0.0-rc.7</strong>, a <em>release candidate</em> from 2020. We were shipping pre-release software to everyone.</p>
<p>The library's author, Niklas von Hertzen, published the stable <strong>1.4.1</strong> release in 2022. This version includes several rendering fixes, better SVG support, and improved CORS handling. We updated to it.</p>
<p>For users who have the screenshot preview feature enabled in TMS settings, this may result in slightly more accurate previews on complex pages. For everyone else, there is no visible difference.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="an-open-question-for-the-community-do-you-use-full-page-screenshots">An open question for the community: do you use full-page screenshots?<a href="https://kb.marvellouscode.works/blog/tms-dependency-cleanup#an-open-question-for-the-community-do-you-use-full-page-screenshots" class="hash-link" aria-label="Direct link to An open question for the community: do you use full-page screenshots?" title="Direct link to An open question for the community: do you use full-page screenshots?" translate="no">​</a></h2>
<p>Here is where we need your input.</p>
<p>The screenshot preview in TMS has two modes, configurable in <strong>Settings → Preview</strong>:</p>
<ul>
<li class=""><strong>Viewport</strong>: captures only the visible portion of the page when you suspend it.</li>
<li class=""><strong>Full page</strong>: scrolls and renders the entire page content, even below the fold.</li>
</ul>
<p>html2canvas is the only reason TMS needs to ship a 200 KB library. The <strong>viewport</strong> mode does not actually need it at all, Chrome provides a native API (<code>chrome.tabs.captureVisibleTab</code>) that captures the visible area of a tab directly from the extension, with no third-party code required. Full-page screenshots, however, need html2canvas because no native browser API supports them.</p>
<p>So the question is: <strong>do you actually use full-page screenshots?</strong> If the vast majority of users either have previews disabled or use viewport-only mode, we could remove html2canvas entirely in a future release, replacing the viewport capture with the native Chrome API and dropping full-page support. The result would be a smaller, simpler, more maintainable extension.</p>
<p>We have opened a discussion on GitHub for exactly this:</p>
<p>👉 <strong><a href="https://github.com/gioxx/MarvellousSuspender/discussions/381" target="_blank" rel="noopener noreferrer" class="">Discussion #381, Which screenshot preview mode do you use in TMS?</a></strong></p>
<p>If you have an opinion, whether you love the full-page preview or have never even turned it on, we would genuinely like to hear it. Community input is what drives these decisions.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="summary">Summary<a href="https://kb.marvellouscode.works/blog/tms-dependency-cleanup#summary" class="hash-link" aria-label="Direct link to Summary" title="Direct link to Summary" translate="no">​</a></h2>
<table><thead><tr><th>Library</th><th>Before</th><th>After</th><th>Why</th></tr></thead><tbody><tr><td>db.js</td><td>0.15.0 (2021, abandoned)</td><td>❌ Removed</td><td>Replaced by idb v8</td></tr><tr><td>idb</td><td>-</td><td>8.0.3</td><td>Modern IndexedDB wrapper, actively maintained</td></tr><tr><td>html2canvas</td><td>1.0.0-rc.7 (2020 RC)</td><td>1.4.1 (2022 stable)</td><td>Updated; future status depends on community feedback</td></tr></tbody></table>
<p>These changes will ship in the next TMS release. If you encounter any regressions with session storage, tab history, or screenshot previews after updating, please <a href="https://github.com/gioxx/MarvellousSuspender/issues" target="_blank" rel="noopener noreferrer" class="">open an issue on GitHub</a>.</p>
<p>Thank you for using TMS, and thank you, as always, for the patience you extend to a small team maintaining this project in their free time.</p>]]></content:encoded>
            <category>The Marvellous Suspender</category>
            <category>Road to TMS 9</category>
        </item>
    </channel>
</rss>