Skip to content

0.3.2: big ▲ ▼ page buttons for TV browsers - #25

Merged
ralyodio merged 1 commit into
mainfrom
feat/page-buttons
Oct 14, 2026
Merged

ralyodio merged 1 commit into
mainfrom
feat/page-buttons

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

Silk on a Fire TV can't scroll hdtilt's lists: its pointer scrolls the page, and the page itself never scrolls, only the lists inside it.

  • Large ▲/▼ buttons on the channel list, the Movies & Shows list and the TV guide, plus a pair pinned to the bottom of each category rail.
  • Each press moves one screen, and the remote's focus lands on the first row in view.
  • On by default on TV browsers (isTvBrowser; the Fire TV AFT… user agent counts). ?pager=on or ?pager=off overrides that on any device and is remembered.
  • Tested in headless Chrome with a Fire TV Silk user agent at 1920×1080, against the real line: 13/13 checks pass. Live TV, the groups rail, Movies & Shows and its category rail, and the guide all page down and back up. A row clicked after paging opens, rows aren't covered by the buttons, and the buttons stay hidden on desktop unless ?pager=on.
  • bun test: 87 pass.

🤖 Generated with Claude Code

Silk on a Fire TV drives the page with a pointer, and that pointer cannot
scroll a list inside the page (the page itself never scrolls), so long
lists were out of reach. The channel list, Movies & Shows, the guide and
both category rails get large page-up/page-down buttons; each press moves
a screen and puts the remote's focus on the first row in view (the guide
moves its view and focused row together). On by default on TV browsers
(isTvBrowser: AFT*, Silk, Android TV, webOS, Tizen...); ?pager=on|off
overrides it on any device and is remembered.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ralyodio
ralyodio merged commit 4c36d88 into main Oct 14, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant