TumbleTab

Create playlists for your favorite dashboards or webpages! Cycle through any set of URLs in one tab.

Create your own webpage playlists. TumbleTab cycles through any set of URLs you give it, on a timer, in one tab — save and reload as many named playlists as you like. How it works 1. Click the TumbleTab toolbar icon — it opens the configuration page. Use the Light / Dark / Auto toggle in the top-right corner to set the interface's theme; “Auto” follows your OS's light/dark setting and updates live if that changes. Your choice is remembered next time you open TumbleTab, and also applies to TumbleTab's own feed reader page. 2. Enter URLs, one per row, drag the ⋮⋮ handle to reorder them. 3. Either give every row its own interval, or turn on “Use the same interval for all URLs” and set a single global interval (default 15s). While that toggle is on, individual row durations are greyed out and locked. 4. Optionally check “Fullscreen when started” — this puts the browser window itself into fullscreen (like pressing F11), not just the page content. 5. Give the playlist a name and click Save to keep it around, or + New to start a fresh one. Use the “Load saved…” dropdown to switch between saved playlists, and Delete to remove the one you're currently viewing. If you change the name before hitting Save, it saves as a new playlist rather than overwriting the one you started from. 6. Export downloads the playlist you're currently editing as a .json file (this is TumbleTab's own format, and re-importing it restores everything — URLs, durations, fullscreen setting). Import loads a file in as a new saved playlist, named after the file itself (minus its extension). It accepts: - a TumbleTab .json export, or a plain JSON array of URLs / {url, value, unit} objects - an exported browser bookmarks file (.html) — every link in it is added, using the default interval - a .csv file — one URL per line, optionally followed by ,duration,unit (e.g. https://example.com,30,sec) 7. Click Start Playlist. The current tab starts cycling through your URLs in order, looping back to the top when it reaches the end. The tab's title stays fixed as “TumbleTab” throughout — including on pages that try to change their own title after loading — rather than switching to each site's title as it cycles through. 8. While it's running, move your mouse to the top of the page to reveal a small ✕ button in the corner, or just press Esc. Either one stops the rotation and returns you to the TumbleTab configuration page. Press the right arrow or left arrow key at any time to jump to the next or previous URL immediately, without stopping the playlist. 9. Clicking a link on any page while a playlist is running opens it in a new tab instead of navigating away — the playlist keeps cycling in the original tab untouched. (Ctrl/Cmd/Shift-click and middle-click still behave normally, since those already mean “open in a new tab” on their own.) Links inside TumbleTab's own feed reader always open in a new tab this way, whether or not a playlist is running. If the browser window is fullscreen at the time (from the “Fullscreen when started” option), it exits fullscreen first so the new tab is actually visible, and stays out of fullscreen for the rest of that playlist run. Direct file-download links (e.g. a .zip or .docx URL) aren't allowed, since TumbleTab can't display a file the browser would just download — you'll get an error message if you try to start a playlist with one. Whatever you're editing is saved automatically as you type, whether or not you've explicitly saved it as a named playlist, so it's still there next time you open TumbleTab. RSS and Atom feeds Add a feed's own URL (RSS, Atom, or RSS 1.0/RDF) to a playlist row like any other link. When you land on a page that's actually a feed, TumbleTab shows a clean, readable list of the feed's entries instead of the raw XML Chrome would normally show: title, date, and a short summary for each, with the entry title linking through to the full article. Pages that aren't a feed are left completely alone. Chrome's own built-in raw-XML viewer for these pages isn't reachable by extension content scripts at all — the same restriction that keeps extensions out of the PDF viewer and view-source: pages — so TumbleTab can't rewrite that page in place the way it can with an ordinary webpage. Instead, as soon as it sees a page's Content-Type come back looking like a feed, it redirects that tab to a small reader page of its own, which re-fetches the feed and renders it. Because of this, the address bar shows TumbleTab's own page while a feed is open, rather than the feed's original URL — there's no way around that given the restriction above. The feed's own URL is still shown at the top of the reader itself, and everything is fetched fresh at that point, so it reflects the feed's current content, not a cached copy. This isn't limited to playback — it applies any time you land on a raw feed URL in Chrome while TumbleTab is installed, not just while a playlist is running. If a page's Content-Type looks like a feed but turns out not to actually be one, TumbleTab sends you back to the original page rather than leaving you stuck on an empty reader view. Notes / limitations (v1) - Only one tab can run a playlist at a time. - If you manually navigate the playing tab away from the extension, the countdown for the page you land on will still be running — clicking the stop button in that tab (or reopening TumbleTab) resets things. - Fullscreen uses chrome.windows.update (whole browser window) rather than the page-content Fullscreen API, so the whole browser chrome — tabs, bookmarks bar, address bar — is hidden, similar to pressing F11. - The file-download check is based on the URL's file extension, since TumbleTab can't know ahead of time how a server will respond — a small number of edge cases may still slip through or get blocked incorrectly. - CSV import uses simple comma-splitting, so a URL containing a literal comma isn't supported. Bookmarks HTML import flattens any folder structure and just imports every link it finds. - If a page fails to load entirely (unreachable host, DNS failure, timeout, etc.), TumbleTab skips it and moves on to the next URL automatically rather than getting stuck — a normal HTTP error page (like a 404) still counts as “loaded” and keeps its assigned interval like any other page. If every single URL in a playlist fails to load, TumbleTab stops and returns to the dashboard rather than looping through broken pages forever. - Feed detection is based on the page's Content-Type (application/rss+xml, application/atom+xml, application/rdf+xml, application/xml, or text/xml) and then confirmed by parsing the feed's own root element (rss, feed, or rdf) — not the URL or file extension, so it works on feed URLs that don't end in .xml/.rss too. If a page's Content-Type looks XML-ish but it turns out not to actually be a feed, or a feed uses an unusual structure that doesn't match, TumbleTab sends you back to the original page rather than displaying a broken reader view. - While a feed is open, the address bar shows TumbleTab's own reader page rather than the feed's original URL — see “RSS and Atom feeds” above for why.