The latest articles on DEV Community by MarshalX (@marshalx). https://dev.to/marshalx https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4175383%2F823558c0-1ed7-404c-9eed-93ea94e2e229.png https://dev.to/marshalx en MarshalX Sat, 10 Oct 2026 14:04:53 +0000 https://dev.to/marshalx/chrome-cant-give-a-tab-a-history-heres-how-i-gave-it-one-anyway-3mgk https://dev.to/marshalx/chrome-cant-give-a-tab-a-history-heres-how-i-gave-it-one-anyway-3mgk <p>Chrome lets you save a tab group. Close it, reopen it later, and every tab comes back on the right page. Press Back, though, and nothing happens: Chrome saved where each tab <em>is</em>, not where it <em>had been</em>.</p> <p>I wanted the whole thing back, so I built Back Pocket, a Chrome extension that saves tab groups with each tab's Back history.</p> <h2> What it keeps </h2> <p>Back Pocket follows each tab's Back and Forward pages as you browse, up to 50 a tab, the most Chrome itself keeps. It records only the addresses, never what was on the pages, and all of it stays on your computer.</p> <h2> Giving it back </h2> <p>Saving the history turned out to be the easy half. Chrome has no way for an extension to hand a tab a history, and getting it to accept those pages as real Back entries was the hardest part of the whole project, and the part I'm proudest of.</p> <p>It works now: restore a group with its history, and each tab's Back button goes where it went before. While that runs, Chrome shows its "started debugging this browser" bar, because that is the only access Chrome gives an extension to a tab's history. The bar goes away when the restore is done, and a plain restore never shows it.</p> <h2> Not paying for it in memory </h2> <p>Restoring a 30-tab group shouldn't load 30 pages. Restored tabs load only when you click them, so even a big group costs almost nothing until you use it.</p> <h2> What I'd tell anyone building something similar </h2> <ul> <li>Measure what Chrome actually does. The documentation and the browser don't always agree, and only a test tells you which one is right.</li> <li>If people will see a warning, explain it before they do. A debugging bar nobody expected looks alarming; one you were told about is just a step.</li> </ul> <p>Back Pocket is free on the Chrome Web Store: <a href="https://chromewebstore.google.com/detail/hpihlojfcfnmcnaafeepfdgbfjoipfkb" rel="noopener noreferrer">https://chromewebstore.google.com/detail/hpihlojfcfnmcnaafeepfdgbfjoipfkb</a>. More about it at <a href="https://backpocket.marshalx.dev" rel="noopener noreferrer">https://backpocket.marshalx.dev</a>, and what else I make at <a href="https://marshalx.dev" rel="noopener noreferrer">https://marshalx.dev</a>.</p> chrome javascript webdev showdev