Title pages: drop the back button, banner meets the rail #229

Closed
opened 2026-08-25 08:29:03 +01:00 by naps62-yolo · 0 comments
Owner

The movie and series pages open with a back button floating above the hero,
and a band of empty space between the rail and the banner.

Two changes:

  • Drop the back button. The rail is always present, browser back works, and
    Esc already returns to the parent route — the button is a third way to do what
    two other things already do, and it costs the page its first line.
  • The banner meets the rail. No padding or margin between the header and the
    top of the hero; the banner starts where the rail ends.

Removing the button means checking what depended on it. movie-back and the
series equivalent are referenced in web/src/main.ts, and the focus handling
after a removal or a failed load may focus them — that focus has to land
somewhere sensible instead, not nowhere. Esc must keep working, and so must the
parent-route logic the button shared.

Goes through the impeccable skill. Drive a real browser with agent-browser,
never google-chrome --headless, and check a title with a backdrop and one
without — the hero renders differently when has-backdrop is absent and the
spacing change has to hold in both.

Non-goals: no change to what the hero contains, and no change to the rail.

The movie and series pages open with a `back` button floating above the hero, and a band of empty space between the rail and the banner. Two changes: - **Drop the back button.** The rail is always present, browser back works, and Esc already returns to the parent route — the button is a third way to do what two other things already do, and it costs the page its first line. - **The banner meets the rail.** No padding or margin between the header and the top of the hero; the banner starts where the rail ends. Removing the button means checking what depended on it. `movie-back` and the series equivalent are referenced in `web/src/main.ts`, and the focus handling after a removal or a failed load may focus them — that focus has to land somewhere sensible instead, not nowhere. Esc must keep working, and so must the parent-route logic the button shared. Goes through the `impeccable` skill. Drive a real browser with `agent-browser`, never `google-chrome --headless`, and check a title with a backdrop and one without — the hero renders differently when `has-backdrop` is absent and the spacing change has to hold in both. Non-goals: no change to what the hero contains, and no change to the rail.
naps62-yolo added this to the Feedback pass 2 milestone 2026-08-25 08:29:03 +01:00
naps62-yolo added the difficulty/easytype/bugarea/web labels 2026-08-25 08:29:03 +01:00
naps62-yolo added a new dependency 2026-08-25 08:29:33 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: yolo/arr#229