Set the chart's placeholder version to 0.35.1

Cosmetic, as before (497086c, 4358e84): make helm-package passes --version and --app-version from the tag, so this decides nothing about what gets published. Kept in step so the tree heading for v0.35.1 doesn't say 0.35.0 to a reader who hasn't yet seen the tag. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Merge pull request 'Fix the queue chip fade falling short of the right edge' (#30 ) from fix-chips-fade-edge into main
2026-10-03 09:39:01 +02:00 · 2026-10-03 07:36:12 +00:00 · 2026-10-03 09:33:33 +02:00 · 2026-10-03 07:30:04 +00:00 · 2026-10-03 09:22:48 +02:00
2 changed files with 14 additions and 7 deletions
@@ -15,5 +15,5 @@ type: application
 # appVersion and image.tag in values.yaml no longer agree, and that is not an oversight:
 # image.tag stays "latest", which is what a local install actually pulls. appVersion is
 # metadata and drives nothing.
-version: 0.35.0
-appVersion: "v0.35.0"
+version: 0.35.1
+appVersion: "v0.35.1"
@@ -255,7 +255,6 @@ input:focus, textarea:focus { outline: none; border-color: var(--accent); box-sh
 /* Hidden here (shown from 900px below): on the phone bar the team switcher
   lives in the topbar instead, as #team-selector-mobile. */
 .nav-team-selector { display: none; }
-.nav-link-secondary { display: none; }
 .nav-link {
  position: relative;
  /* flex: 1 spreads the tabs evenly across the bar's width; the desktop
@@ -267,6 +266,10 @@ input:focus, textarea:focus { outline: none; border-color: var(--accent); box-sh
     what stops six tabs widening the bar past the screen. */
  min-width: 0; padding: 0 2px;
 }
+/* Must come after .nav-link above: same specificity (one class each), so
+   whichever is later in the file wins for an element wearing both classes,
+   and this needs to beat .nav-link's display:flex here on the phone bar. */
+.nav-link-secondary { display: none; }
 .nav-label {
  max-width: 100%; overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
 }
@@ -323,6 +326,7 @@ input:focus, textarea:focus { outline: none; border-color: var(--accent); box-sh
 /* ---------- chips ---------- */

 .chips {
+  position: relative;
  display: flex; gap: 6px;
  padding: 12px 16px 8px;
  overflow-x: auto; scrollbar-width: none;
@@ -338,11 +342,14 @@ input:focus, textarea:focus { outline: none; border-color: var(--accent); box-sh
 }
 .chip[aria-selected="true"] { background: var(--text); border-color: var(--text); color: var(--bg); }
 .chip .count { margin-left: 4px; opacity: 0.7; }
-/* Pinned to the visible right edge of the scrolling row (sticky, not
-   absolute, so it tracks the scroll position rather than the content). */
+/* An overlay, not a flex item: absolute against .chips' own (non-scrolling)
+   box stays flush with its real right edge regardless of scroll position,
+   which turned out not to be true of position:sticky here — as a flex
+   item, its sticky offset interacted with the row's gap and its own
+   negative margin, landing short of the edge by about one gap's width. */
 .chips-fade {
-  position: sticky; right: -1px; flex: none;
-  width: 24px; margin-left: -24px;
+  position: absolute; top: 0; right: 0; bottom: 0;
+  width: 24px;
  background: linear-gradient(to right, transparent, var(--bg));
  pointer-events: none;
 }
Author	SHA1	Message	Date
Niklas Ye	c83c7c2a8b	Set the chart's placeholder version to 0.35.1 CI / chart (push) Successful in 2s Details CI / security (push) Successful in 20s Details CI / test (push) Successful in 4m45s Details Release / test (push) Successful in 3s Details Release / chart (push) Successful in 2s Details Release / binaries (push) Successful in 50s Details Release / image (push) Successful in 1m21s Details Release / scan-image (push) Successful in 3s Details Cosmetic, as before (`497086c`, `4358e84`): make helm-package passes --version and --app-version from the tag, so this decides nothing about what gets published. Kept in step so the tree heading for v0.35.1 doesn't say 0.35.0 to a reader who hasn't yet seen the tag. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-03 09:39:01 +02:00
niklas	43beda9a30	Merge pull request 'Fix the queue chip fade falling short of the right edge' (#30 ) from fix-chips-fade-edge into main CI / chart (push) Successful in 1s Details CI / security (push) Successful in 21s Details CI / test (push) Has been cancelled Details	2026-10-03 07:36:12 +00:00
Niklas Ye	710521a73c	Fix the queue chip fade falling short of the right edge CI / chart (pull_request) Successful in 1s Details CI / security (pull_request) Successful in 16s Details CI / test (pull_request) Successful in 5m13s Details position: sticky, as a flex item of the row it's pinning itself against, interacted with that row's gap and its own negative margin in a way that landed it short of the true edge -- visibly, a sliver of the next chip stayed poking out past where the fade should have covered it, which is the "ends before the screen edge" bug reported against the release. Replaced with the simpler, better-supported pattern for this: an absolutely positioned overlay against a position:relative, overflow: auto parent. Unlike a sticky descendant, an absolutely positioned one is resolved against the parent's own (non-scrolling) box, so it stays flush with the real edge regardless of scroll position, without the flex-gap/margin interaction that caused this. Verified visually: a standalone reproduction of both versions, screenshotted with Chromium's headless_shell (no browser automation tool available in this environment, but the binary's right there) -- the old version shows the next chip's edge peeking past the fade, the new one doesn't. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-03 09:33:33 +02:00
niklas	d9492913ed	Merge pull request 'Fix Stats/Admin/Account showing in the bottom bar too' (#29 ) from fix-nav-secondary-cascade into main CI / chart (push) Successful in 0s Details CI / test (push) Successful in 8s Details CI / security (push) Successful in 14s Details Reviewed-on: #29	2026-10-03 07:30:04 +00:00
Niklas Ye	1770e5d945	Fix Stats/Admin/Account showing in the bottom bar too CI / chart (pull_request) Successful in 1s Details CI / security (pull_request) Successful in 16s Details CI / test (pull_request) Successful in 5m2s Details .nav-link-secondary's display:none sat before .nav-link's own display:flex in the file. Both are single-class selectors, so they tie on specificity, and a tie is broken by which one comes later in the file -- not by which class the element happens to carry. .nav-link's declaration, being later, won for every element wearing both classes, so Stats/Admin/Account rendered as three extra tabs on the phone bar instead of folding into "More" as intended. Moved the rule below .nav-link instead of changing either declaration, since nothing about the values was wrong -- only their order was. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-03 09:22:48 +02:00