5 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 4.8	67c7ca8603	fix(ui): measure real nav height (--fc-nav-h), stop Explore breadcrumb tucking under nav (#1481) ... The app uses a plain sticky TopNav (no v-main), and the nav's height was hardcoded as 64px in ~6 places: the Explore + Subscriptions full-height workspaces (height: calc(100vh - 64px)) and every sticky sub-header pinned beneath the nav (top: 64px — Gallery filter bar, Browse/Series/Settings tabs). Vuetify 4's MD3 sizing changed the real nav height, so 64px was wrong: the Explore workspace was sized taller than the space below the nav, overflowed the viewport, and its breadcrumb tucked under the (taller) nav on 1080p. TopNav now measures its own height via ResizeObserver and publishes it as --fc-nav-h on documentElement (default 64px in app.css). Every consumer uses var(--fc-nav-h) instead of the magic number, so the layout self-corrects to the nav's real height and stays correct as it reflows (per-view teleported actions, mobile breakpoint). Also tightens the new chrome-gradient seam — sub-headers now pin at the nav's exact bottom. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-13 15:27:37 -04:00
bvandeusenandClaude Opus 4.8	eed42a260a	fix(ui): one continuous chrome gradient across nav + sticky sub-headers (#1478) ... The TopNav and each sticky sub-header pinned beneath it (Gallery's filter bar, the Browse/Series/Settings/Subscriptions tabs bars) each painted their OWN dark-to-transparent gradient (Gallery) or a solid surface band (the rest), so the fade read as happening twice — dark, fade out, then dark again — instead of one gradient flowing from the nav down through the sub-nav. Operator asked to treat the sub-nav as part of the nav with a single gradient. New shared .fc-chrome-continues primitive (app.css): the nav fades from opaque to a shared --fc-chrome-seam alpha (on views flagged meta.stickyChrome), and the sub-header continues from that exact seam alpha to transparent over its own height. Both reference the same var so the alphas meet at the 64px boundary — no re-darkening, no doubling. Percentage stops keep it spanning the filter bar's expanding refine panel; the primitive's blur keeps tabs/controls legible where the old solid bars had none. --fc-chrome-seam is the single tuning knob. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-13 14:42:07 -04:00
bvandeusenandClaude Opus 4.8	3e1303ea3c	fix(browse): put tabs and search on one row ... Operator-asked: the tab strip and search field were stacked; place them side-by-side in a single flex bar (tabs left, search + scope chips right), wrapping to two rows only on narrow viewports. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-12 00:25:03 -04:00
bvandeusenandClaude Opus 4.8	2c544ad5af	feat(browse): sticky tabs + per-tab search bar (server-side, scope-aware) ... The Browse tab nav scrolled away (operator didn't know it existed) and Posts had no search. Roll the tab strip + a shared search field into one sticky block pinned under the 64px TopNav. - Posts gains server-side text search: PostFeedService.scroll()/around() + /api/posts accept q (ILIKE over post_title OR description), applied INSIDE the artist/platform WHERE so search stays scoped to the active filter. Scope shown as clearable chips next to the search field. - Artists/Tags search consolidates into the sticky bar: their inner search boxes are removed; they react to route.query.q (q is deep- linkable, e.g. /browse?tab=posts&q=foo). Platform/kind filters stay. - Posts empty state now distinguishes 'no matches' from 'no posts yet'. Tests: posts q-search matches title|description and stays artist-scoped (service); q passthrough (api). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-12 00:04:06 -04:00
bvandeusenandClaude Opus 4.8	d5d23a92f2	feat(nav): consolidate Posts/Artists/Tags into a Browse hub ... Posts, Artists, and Tags are the three 'browse the library by an axis' surfaces; Subscriptions stays purely management (operator-asked 2026-06-09). New BrowseView renders them as tabs (?tab=posts|artists|tags); only the active tab mounts. The old standalone paths become redirects into the matching tab, preserving deep-link query (/posts?post_id=N → /browse?tab=posts&post_id=N) and keeping the route names so existing { name: 'posts'|'artists'|'tags' } links and path pushes still resolve. Nav now reads Showcase · Gallery · Browse · Series · Subscriptions, with Settings pinned right. Test: /browse resolves; /tags and /artists redirect into their tabs; a posts deep link survives the redirect. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-09 21:18:02 -04:00