/* Page tools: the toolbar's share / capture / downloads / history panels, and
   the split-screen layout they cooperate with. Split out of styles.css so the
   sheet that owns the rail, the tabs and the dock never has to be touched to
   change how a panel looks. Mirrored to dist by scripts/copy-renderer.js. */

/* ── the lines a panel adds after it acts ────────────────────────────────────
   setStatus() writes the first one in place of whatever it said last, so a
   confirmation such as "Link copied" is part of the panel rather than a toast
   that leaves with the pointer. .tb-note is the quieter form: a line that
   explains what the list below it is, and is meant to be read rather than
   noticed. */
.tb-status{margin-top:9px;padding:7px 9px;border:1px solid var(--accent);border-radius:8px;color:var(--fg);font-size:13px}
.tb-note{margin:9px 0 0;color:var(--fg);font-size:12px;line-height:1.5;opacity:.62}

/* Save on a capture is a real <a download>, so it is an anchor wearing the
   button row's clothes: styles.css styles .tb-shot-actions button and this is
   the same box with the link's own colour and underline taken off. */
.tb-shot-actions a{display:inline-flex;align-items:center;padding:7px 11px;border:1px solid var(--line);border-radius:8px;background:var(--surface);color:var(--fg);font-size:13px;text-decoration:none;cursor:pointer}
.tb-shot-actions a:hover{border-color:var(--accent)}

/* ── split screen ────────────────────────────────────────────────────────────
   Two pages side by side. In the desktop shell the layout is main.ts's: a
   WebContentsView composites above this document, so only the main process can
   move it, and renderer.ts asks for it through the bridge. A browser tab has no
   such layer - every page is an <iframe> in this one document - so there the
   layout is this sheet's, driven by the single attribute renderer.ts owns and
   the pane class it puts on the frame it is showing.

   Every rule is written against html[data-split="on"], and only the browser
   build ever writes that attribute or those classes, so a shell or a page that
   has never turned split screen on is laid out exactly as it was. Half the
   surface each, with one hairline between them, and the frame's 42px top inset
   kept so both panes start on the line they started on before. */
html[data-split="on"] .surface-frame.tb-pane-left{inset:42px 50% 0 0;width:50%;border-right:1px solid var(--line)}
html[data-split="on"] .surface-frame.tb-pane-right{inset:42px 0 0 50%;width:50%;border-right:0}

/* The right half while no second page is open. Split screen with one page open
   is still split screen, and saying what fills the pane is better than an empty
   rectangle - the same rule the rail follows when it says a module could not be
   opened rather than leaving a blank tile. [hidden] is repeated because the
   sheet's own display:grid would otherwise outrank the user agent's rule for it
   and leave the hint on screen when split screen is off. */
.tb-split-hint{position:absolute;inset:42px 0 0 50%;width:50%;display:grid;place-content:center;gap:7px;padding:0 9%;border-left:1px solid var(--line);background:var(--surface);color:var(--fg);text-align:center;font-family:"Cascadia Code","IBM Plex Mono",monospace}
.tb-split-hint[hidden]{display:none}
.tb-split-hint b{font-size:13px;letter-spacing:.16em;text-transform:uppercase;color:var(--accent)}
.tb-split-hint span{font-size:13px;line-height:1.55;opacity:.72}