/* ============ Design tokens (shared with the Workout Generator, Print Cost * and the Inspiration Gallery) ============ * * Same palette and geometry as the sibling apps — this is the house system, * not a per-app choice. Change a token here only if it's changing in all of * them. Copied verbatim from the Workout Generator. */ :root { /* SEMANTIC NAMES, unlike every sibling app, which calls these --teal. DELEGATION-PLAN.md §2.11: this app may be renamed and re-skinned for a public release, and a stylesheet full of `var(--teal)` makes that a find-and-replace across a thousand lines instead of three values here. The VALUES are still the house teal, so it looks like the rest of the suite until somebody decides otherwise. */ --accent: #41b7ab; --accent-dark: #369a90; /* accessible against white for text */ --slate: #515a60; --bg: #ffffff; --border: #dddddd; --ink: #222222; --black: #000000; --accent-tint: #e8f6f4; --error: #c05252; --surface: #ffffff; --text: var(--slate); --heading: var(--slate); --radius: 10px; --tap: 48px; --maxw: 620px; --font: "Avenir Next", Avenir, "Segoe UI", system-ui, -apple-system, sans-serif; --safe-top: env(safe-area-inset-top, 0px); --safe-bottom: env(safe-area-inset-bottom, 0px); /* Pin to light so iOS doesn't auto-darken inputs and scrollbars for people whose phone is in dark mode. */ color-scheme: light; } /* Deliberately light-only, matching the siblings. * * NOTE FOR ANYONE PORTING MORE CSS FROM THE GALLERY: that app pins * html,body { overflow:hidden; touch-action:none } because it's a full-bleed * pannable WebGL canvas. Do NOT bring that here. Three of this app's screens * are scrolling lists, and those two rules would make every row below the fold * unreachable — and would kill the swipe gestures outright. */ * { box-sizing: border-box; } html, body { margin: 0; padding: 0; } body { font-family: var(--font); font-size: 16px; line-height: 1.5; color: var(--text); background: var(--bg); -webkit-text-size-adjust: 100%; -webkit-font-smoothing: antialiased; } button, input, textarea, select { font: inherit; } button { cursor: pointer; } [hidden] { display: none !important; } .hidden { display: none !important; } .muted { color: var(--slate); opacity: 0.7; font-weight: 400; } .hint { font-size: 0.82rem; color: var(--slate); opacity: 0.75; } .sr-only { position: absolute; width: 1px; height: 1px; padding: 0; margin: -1px; overflow: hidden; clip: rect(0 0 0 0); white-space: nowrap; border: 0; } /* ============ Layout ============ */ /* The centred column. Bottom padding clears the fixed tab bar plus the iPhone home-indicator inset. */ .wrap { max-width: var(--maxw); margin: 0 auto; padding: calc(var(--safe-top) + 18px) 18px calc(var(--safe-bottom) + var(--tap) + 34px); } /* Signature divider — a 2px teal rule under headings. */ .screen-head { display: flex; align-items: baseline; justify-content: space-between; gap: 12px; border-bottom: 2px solid var(--accent); padding-bottom: 10px; margin: 4px 0 20px; } h1 { font-size: 1.7rem; font-weight: 500; margin: 0; color: var(--heading); letter-spacing: 0.2px; } h2 { font-size: 1.1rem; font-weight: 600; margin: 26px 0 10px; color: var(--heading); } .rule { border: 0; border-top: 2px solid var(--accent); margin: 28px 0 18px; } .stack { display: grid; gap: 14px; } .row { display: flex; align-items: center; gap: 10px; } .row-between { display: flex; align-items: center; justify-content: space-between; gap: 10px; } /* Heading row actions. Sits in the heading row rather than floating over the page, so it can never overlap content. */ .head-actions { display: flex; align-items: center; gap: 8px; flex: none; } /* ============ Bottom tab bar ============ */ .tabbar { position: fixed; left: 0; right: 0; bottom: 0; display: flex; background: var(--surface); border-top: 1px solid var(--border); padding-bottom: var(--safe-bottom); z-index: 20; } .tabbar a { flex: 1; min-height: var(--tap); display: flex; align-items: center; justify-content: center; text-decoration: none; color: var(--slate); font-size: 0.9rem; font-weight: 600; border-top: 2px solid transparent; margin-top: -1px; } .tabbar a.is-active { color: var(--accent-dark); border-top-color: var(--accent); } /* ============ Sheet (menus, pickers) ============ * * Ported from the Inspiration Gallery, same markup and behaviour: a bottom * sheet on a phone, a centred dialog once there's room. Bottom-anchored because * that's where your thumb is — a menu that drops from the top corner it was * tapped in is a desktop habit. * * The Grocery tab's category picker is expected to use this. */ .sheet { position: fixed; inset: 0; z-index: 50; display: flex; align-items: flex-end; justify-content: center; background: rgba(0, 0, 0, 0.4); } .sheet-panel { background: var(--bg); width: 100%; max-width: var(--maxw); border-radius: 16px 16px 0 0; display: grid; gap: 2px; padding: 16px 16px calc(20px + var(--safe-bottom)); /* The category sheet is ten rows tall and the archive-move sheet could grow. Without this, a sheet taller than the viewport puts its last option — which is always Cancel — permanently off-screen. */ max-height: 80vh; overflow-y: auto; overscroll-behavior: contain; } @media (min-width: 620px) { .sheet { align-items: center; } .sheet-panel { border-radius: 16px; } } .sheet-panel button, .sheet-panel a { min-height: var(--tap); display: flex; align-items: center; padding: 0 16px; background: var(--surface); border: 1px solid var(--border); border-radius: var(--radius); color: var(--heading); font-weight: 600; text-align: left; text-decoration: none; } .sheet-panel button:hover, .sheet-panel a:hover { border-color: var(--accent); color: var(--accent-dark); } .sheet-panel button.is-current { border-color: var(--accent); background: var(--accent-tint); color: var(--accent-dark); } .sheet-cancel { justify-content: center; color: var(--slate) !important; margin-top: 8px; } /* ============ Fields ============ */ .field { display: flex; flex-direction: column; gap: 6px; } .field > span, .label { font-size: 0.95rem; font-weight: 400; color: var(--heading); } .field input, .field textarea, .field select, .input { font: inherit; color: var(--text); background: var(--surface); border: 1px solid var(--border); border-radius: var(--radius); padding: 12px 14px; width: 100%; appearance: none; } .field input, .field select, .input { min-height: var(--tap); padding: 0 14px; } .field textarea { resize: vertical; line-height: 1.5; } .field input:focus, .field textarea:focus, .field select:focus, .input:focus { outline: 2px solid var(--accent); outline-offset: 1px; border-color: var(--accent); } .field-err { font-size: 0.82rem; color: var(--error); min-height: 1em; } /* ============ Buttons ============ */ /* These work on as well as * * * A real
rather than a div plus a click handler, so Enter on a phone * keyboard submits without any JS at all — and so the whole thing still works * on a full page POST if a tab module wants to skip fetch entirely. */ .composer { display: flex; gap: 8px; align-items: stretch; margin-bottom: 18px; } /* A composer at the TOP of a screen needs no space above it — the heading rule * already provides it. One that follows content does, and the Shopping tab's * "Add a store" box sits directly under the store list, where margin-bottom * alone left the input butted against the last row's border with the two * rounded corners touching. Scoped to the adjacency so the leading composer on * every tab is untouched. */ .list + .composer, .card + .composer, .accordion + .composer { margin-top: 14px; } .composer-input { flex: 1 1 auto; min-width: 0; min-height: var(--tap); /* 16px EXACTLY, never smaller. Below 16px iOS zooms the page on focus and never zooms back out, which on a list you're adding six things to means re-pinching after every item. */ font-size: 16px; color: var(--text); background: var(--surface); border: 1px solid var(--border); border-radius: var(--radius); padding: 0 14px; appearance: none; } .composer-input:focus { outline: 2px solid var(--accent); outline-offset: 1px; border-color: var(--accent); } /* Overrides .btn-primary's width:100% — in a flex row the button sizes to its label, and "Add" is two thumbs wide, not a full bar. */ .composer-add { flex: 0 0 auto; width: auto; min-height: var(--tap); padding: 0 18px; border: 1px solid transparent; border-radius: var(--radius); background: var(--accent); color: #fff; font-weight: 600; } .composer-add:hover { background: var(--accent-dark); } .composer-add:disabled { opacity: 0.45; cursor: not-allowed; } /* ============ The list row primitive ============ * * The shared swipeable row used by all three tabs. One structure, three * meanings: * * * * TWO LAYERS, and both are load-bearing. The
  • is the fixed frame: it holds * the delete affordance, the borders and the collapse animation. .row-slide is * the only thing that moves under the finger. Translating the
  • itself would * drag its own border and its delete label along with it, so there would be * nothing revealed underneath. */ .list { list-style: none; margin: 0; padding: 0; border: 1px solid var(--border); border-radius: var(--radius); /* Clips the sliding layer at the rounded corners, and stops a row mid-swipe painting over the group heading above it. */ overflow: hidden; } .list:empty { display: none; } .list-row { position: relative; background: var(--error); /* only ever visible behind a swiped row */ /* Vertical panning stays with the browser; horizontal movement comes to swipe.js as pointer events. This one declaration is what stops the swipe handler from hijacking the page scroll, and it does it in the compositor rather than in JS — no amount of preventDefault() discipline is as reliable. Do not change it to `none`: that kills scrolling over the list. Do not remove it: without it the browser may claim the horizontal gesture as an overscroll/back-navigation before swipe.js ever sees a move. */ touch-action: pan-y; /* The collapse animation's starting point. A fixed max-height rather than `height: auto` because auto is not animatable; 300px is far above any real row and is never reached, so it has no visual effect until .is-removing drops it to zero. */ max-height: 300px; transition: max-height 0.18s ease, opacity 0.18s ease; } .list-row + .list-row .row-slide { border-top: 1px solid var(--border); } /* The delete affordance, revealed as the row slides left. * * A ::after on the frame rather than a real element: it is decoration, it is * never tappable (the gesture is the control), and a real button here would be * announced by a screen reader as a control that cannot be reached by keyboard. */ .list-row::after { content: "Delete"; position: absolute; top: 0; right: 0; bottom: 0; /* Bottom of an explicit three-layer stack: this label, then .row-slide over it, then the grace bar over that. All three are positioned inside the same stacking context, and with z-index:auto the painting order is tree order — which puts generated ::after content ABOVE the element's own children. The label therefore sat on top of the row at rest, showing through wherever the row had content to collide with, most visibly across the category pill. It is only ever meant to be seen through the gap a swiped row leaves behind. */ z-index: 0; display: flex; align-items: center; padding: 0 18px; color: #fff; font-size: 0.85rem; font-weight: 700; letter-spacing: 0.04em; text-transform: uppercase; pointer-events: none; } /* The desktop way out of a touch gesture. * * Swipe-to-delete is the whole interaction on a phone and does not exist on a * desktop: there is no flick with a mouse, and the row is otherwise undeletable * there. This is that backup — the same delete, the same undo snackbar, reached * by a button instead of a thumb. * * Hidden by default and shown only to a fine pointer, so the phone keeps the * clean row it was designed around and does not grow a 48px target sitting * right beside the category pill, waiting to be fat-fingered. Delete it from * the media query to show it everywhere. */ .row-del { display: none; flex: 0 0 auto; align-items: center; justify-content: center; width: 34px; height: 34px; padding: 0; border: 0; border-radius: 8px; background: none; color: var(--slate); opacity: 0.45; transition: opacity 0.12s ease, background 0.12s ease, color 0.12s ease; } .row-del svg { width: 19px; height: 19px; fill: none; stroke: currentColor; stroke-width: 1.7; stroke-linecap: round; stroke-linejoin: round; } @media (hover: hover) and (pointer: fine) { .row-del { display: flex; } .row-del:hover, .row-del:focus-visible { opacity: 1; color: var(--error); background: #f7ecec; } } /* The moving layer. Everything visible lives in here. */ .row-slide { position: relative; display: flex; align-items: center; gap: 10px; min-height: var(--tap); padding: 8px 14px; background: var(--surface); transform: translateX(var(--swipe-dx, 0px)); transition: transform 0.18s ease; /* Middle layer: covers the Delete label until the swipe slides this aside. The opaque background is half of that job and this is the other half — without it the label paints over this element's own children. */ z-index: 1; } /* Finger-tracking: no transition, or every frame lags 180ms behind the thumb. swipe.js adds .is-swiping on gesture lock and removes it on release, which is what makes the spring-back animate while the drag does not. */ .list-row.is-swiping .row-slide { transition: none; will-change: transform; } /* Past the delete threshold. The label goes bold-white on full red so you can see the commit point without watching the pixel offset — the gesture is otherwise entirely un-discoverable in its most important respect, which is how far is far enough. */ .list-row.is-armed::after { font-size: 0.95rem; } .list-row.is-armed .row-slide { box-shadow: -6px 0 12px -6px rgba(0, 0, 0, 0.25); } /* Collapsing out after a delete. The row stays in the DOM through the undo window so that Undo restores this exact element with its listeners intact; this is what it looks like while it is gone. */ .list-row.is-removing { max-height: 0; opacity: 0; overflow: hidden; pointer-events: none; } /* Checked / crossed out. * * ONE class for two tabs. Grocery uses it for a checked item during its grace * window; Shopping uses it for a permanently crossed-out line. They look the * same because they mean the same thing to the eye — done, but still here. */ .list-row.is-checked .row-text { text-decoration: line-through; text-decoration-thickness: 2px; color: var(--slate); opacity: 0.55; } .list-row.is-checked .row-cat { opacity: 0.5; } /* The grace window: checked, and counting down to disappearing. * * The countdown is a real bar rather than a fade, because a fade reads as "this * is loading" and the whole point is that you have a few seconds to change your * mind. Duration comes from --grace-ms, set by the tab module from * cfg('grocery.grace_seconds') — so the bar and the server-side sweep are * driven by the same number and can't drift apart. * * The row is still visible and still swipeable while this runs. */ .list-row.is-grace { background: var(--accent-tint); } .list-row.is-grace .row-slide { background: var(--accent-tint); } .list-row.is-grace::before { content: ""; position: absolute; left: 0; bottom: 0; height: 2px; background: var(--accent); /* Top layer, above .row-slide's 1. This bar is drawn across the bottom edge of the row it is counting down, so it has to sit over the sliding layer rather than under it — at z-index 1 it would tie with .row-slide and lose on tree order, because a ::before paints before the element's children. */ z-index: 2; animation: grace-drain var(--grace-ms, 3000ms) linear forwards; } @keyframes grace-drain { from { width: 100%; } to { width: 0%; } } /* Someone who has asked the OS to stop animating things still needs to know the row is on its way out; they get the tint and the strike-through, without a bar sliding across their screen. */ @media (prefers-reduced-motion: reduce) { .list-row.is-grace::before { animation: none; width: 100%; opacity: 0.4; } .row-slide, .list-row { transition: none; } } /* ---- row contents ---- */ /* The text. Tapping it opens the inline editor (inline-edit.js), so it needs a full-height hit area — a single line of text in a 48px row is a 22px target otherwise. It is NOT a