<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Vertical tabs: close the gap with Arc's sidebar (URL-bound pins, favorites, folders, true hide) in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/vertical-tabs-close-the-gap-with-arc-s-sidebar-url-bound-pins/m-p/135309#M54483</link>
    <description>&lt;P&gt;Firefox 136 shipped vertical tabs, which was the right foundation — but the sidebar is still "the tab strip, rotated." Arc treated it as the browser's primary navigation surface, and with Arc now in maintenance mode there's a large, technically literate user base looking for a new home. Four things stand between Firefox and being the obvious destination:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Pins should remember a URL.&lt;/STRONG&gt; In Arc, a pinned tab is bound to a home address — navigate away and one click (or a restart) returns it there. Firefox pins are just small tabs that drift, so they stop being reliable navigation targets. Store a home URL per pin, restore to it on restart, add "reset to pinned URL."&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;A favorites tier above pins.&lt;/STRONG&gt; Arc has three tiers with three different lifetimes: favorites (always visible, icon-only, global), pinned tabs (per-space, named, ordered), ordinary tabs (transient). That tiering is what lets a sidebar hold 60 tabs and stay usable. Firefox has two, weakly separated.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Persistent folders for pinned tabs.&lt;/STRONG&gt; Vertical space is cheap and supports hierarchy — that's the actual argument for vertical tabs over horizontal. Collapsible, drag-and-drop folders whose state survives restart.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;A sidebar that hides to zero width.&lt;/STRONG&gt; Arc's hidden state reserves no space at all; hovering the window edge slides it back as an overlay &lt;EM&gt;above&lt;/EM&gt; the page, without reflowing content. Firefox's collapsed state keeps an icon rail and pushes content when it expands. This sounds cosmetic but it's the mechanism that makes a rich sidebar affordable on a 13" screen. (Configurable delay + click-instead-of-hover option for accessibility.)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;All of it is additive and can sit behind the existing vertical-tabs prefs with today's behaviour as default. Containers already map cleanly onto Arc's Spaces — the harder primitive is arguably built. Suggested order by value-to-effort: URL-bound pins → true hide/hover reveal → folders → favorites.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Aug 2026 10:20:19 GMT</pubDate>
    <dc:creator>kiroshi</dc:creator>
    <dc:date>2026-08-21T10:20:19Z</dc:date>
    <item>
      <title>Vertical tabs: close the gap with Arc's sidebar (URL-bound pins, favorites, folders, true hide)</title>
      <link>https://connect.mozilla.org/t5/discussions/vertical-tabs-close-the-gap-with-arc-s-sidebar-url-bound-pins/m-p/135309#M54483</link>
      <description>&lt;P&gt;Firefox 136 shipped vertical tabs, which was the right foundation — but the sidebar is still "the tab strip, rotated." Arc treated it as the browser's primary navigation surface, and with Arc now in maintenance mode there's a large, technically literate user base looking for a new home. Four things stand between Firefox and being the obvious destination:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Pins should remember a URL.&lt;/STRONG&gt; In Arc, a pinned tab is bound to a home address — navigate away and one click (or a restart) returns it there. Firefox pins are just small tabs that drift, so they stop being reliable navigation targets. Store a home URL per pin, restore to it on restart, add "reset to pinned URL."&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;A favorites tier above pins.&lt;/STRONG&gt; Arc has three tiers with three different lifetimes: favorites (always visible, icon-only, global), pinned tabs (per-space, named, ordered), ordinary tabs (transient). That tiering is what lets a sidebar hold 60 tabs and stay usable. Firefox has two, weakly separated.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Persistent folders for pinned tabs.&lt;/STRONG&gt; Vertical space is cheap and supports hierarchy — that's the actual argument for vertical tabs over horizontal. Collapsible, drag-and-drop folders whose state survives restart.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;A sidebar that hides to zero width.&lt;/STRONG&gt; Arc's hidden state reserves no space at all; hovering the window edge slides it back as an overlay &lt;EM&gt;above&lt;/EM&gt; the page, without reflowing content. Firefox's collapsed state keeps an icon rail and pushes content when it expands. This sounds cosmetic but it's the mechanism that makes a rich sidebar affordable on a 13" screen. (Configurable delay + click-instead-of-hover option for accessibility.)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;All of it is additive and can sit behind the existing vertical-tabs prefs with today's behaviour as default. Containers already map cleanly onto Arc's Spaces — the harder primitive is arguably built. Suggested order by value-to-effort: URL-bound pins → true hide/hover reveal → folders → favorites.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Aug 2026 10:20:19 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/vertical-tabs-close-the-gap-with-arc-s-sidebar-url-bound-pins/m-p/135309#M54483</guid>
      <dc:creator>kiroshi</dc:creator>
      <dc:date>2026-08-21T10:20:19Z</dc:date>
    </item>
  </channel>
</rss>

