THETAB TEAM

18 articles, 155 sources published

Editorial team, TheTab

We build TheTab, a browser extension that saves your open tabs so you can close them without losing them. Everything on this blog is written by the same small team that writes the extension.

That is worth stating plainly rather than hiding behind a byline, because it cuts both ways. We spend our working days on tab management, browser storage limits and extension permissions, so we know the subject in detail. We also make one of the products in the category, which gives us an interest in how the category is described.

The way we deal with that is process rather than promises. Every factual claim on this blog is traceable to a source you can open, our own product is disclosed as ours every time it appears, and the parts of the process that can be enforced by a machine are enforced by one.

HOW WE WRITE THIS

Primary sources only
Claims are traced to the organisation that made them - Google's own documentation for Chrome behaviour, Mozilla's release notes for Firefox, the published paper for a research finding. We do not cite blog posts summarising a source when the source itself is public, and we never cite ourselves as evidence for a fact.
Every source is published
Articles carry a reference list at the end, and each entry names the specific claim it supports rather than sitting there as decoration. If you think we have read a source wrong, you can check it in one click.
The build enforces it
A check runs before the site can be deployed. An article with no sources fails it, a source we cannot categorise fails it, and citing this domain as evidence for a factual claim fails it. Articles that legitimately need no sources have to say so explicitly rather than pass by omission.
Corrections are dated, not silent
When an article changes materially it gets an updated date shown at the top of the page, and the change is described in the text rather than edited in quietly. Where we removed a figure because we could no longer stand behind it, the article says that we removed it.
No invented numbers, no AI-generated imagery
Statistics are quoted from a named source or they are not published. Diagrams, screenshots and cards are generated from the real extension and from real data by scripts in this repository, so a screenshot of the product is a screenshot of the product.
Photography is licensed, and it is only decoration
The photographs on this site - hero backgrounds like the one on this page - are stock photography licensed through Envato Elements. They are used as decoration, never as evidence: no photo on this site depicts our team, our office, or a test we ran.

DISCLOSURE We make TheTab. Any article comparing tab managers is written by a competitor of the other tools in it, and says so where it names them. Sponsored placements are labelled as sponsored and their links are marked accordingly.

EVERYTHING WE HAVE PUBLISHED

18 of 18 articles
Title card reading "OneTab vs Simple Tab Groups: Close Tabs or Just Hide Them?"
September 6, 20268 MIN READ

OneTab vs Simple Tab Groups: Close Tabs or Just Hide Them?

Both promise to fix a full tab strip on Firefox, and they do it in opposite ways. OneTab closes every tab and replaces them with a list. Simple Tab Groups keeps every tab running and hides the ones you are not using, through a Firefox-only API Chrome does not have. Compared on memory, switching windows, and what survives a browser restart.

READ ARTICLE →
Title card reading "Session Buddy vs Tab Session Manager: Polished or Open"
September 3, 20268 MIN READ

Session Buddy vs Tab Session Manager: Polished or Open

Both take a snapshot of every open window so a crash cannot cost you your tabs. Session Buddy is a polished, Chrome-only, closed app with a million users. Tab Session Manager is open source, runs on Firefox and Edge too, lets you set the auto-save interval, and can sync through your own Google Drive. Compared on storage, automation, what you can read, and how each one came through the Manifest V3 cutover.

READ ARTICLE →
Title card reading "Manifest V3 Weakened Chrome Ad Blockers. What Else It Changed"
August 30, 202610 MIN READ

Manifest V3 Weakened Chrome Ad Blockers. What Else It Changed

Manifest V3 is three changes, not a hundred. Background pages became service workers that sleep after thirty seconds. The blocking network API became a rules list with a fixed ceiling, which is why the full uBlock Origin no longer runs on Chrome. And extensions can no longer load code from the web. Here is which of your extensions each change touches, and what Firefox, Brave and Edge decided to do instead.

READ ARTICLE →
Title card reading "Chrome Extension Permissions: What the Prompt Leaves Out"
August 27, 202613 MIN READ

Chrome Extension Permissions: What the Prompt Leaves Out

Chrome shows you warnings, not permissions, and the two are different lists. More than forty permissions produce no line at all, one permission can hide another's line entirely, and the most alarming sentence in the box usually comes from the most ordinary thing an extension can ask for. Including our own extension's list, where eight of the thirteen permissions never reach the box.

READ ARTICLE →