Skip to content

fix(range): keep Range usable at the largest text sizes - #110

Merged
btripp merged 2 commits into
mainfrom
fix/range-large-text
Oct 11, 2026
Merged

btripp merged 2 commits into
mainfrom
fix/range-large-text

Conversation

@btripp

@btripp btripp commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Summary

Range layout problems at the largest text size, from a tester's report (2026-10-09).

  • Prev, Play and Next (replay and overlay) stay on screen. When the metrics don't fit, they scroll above the controls, in portrait and narrow landscape, on Android and iOS.
  • iOS: Ball speed and Carry scale with Dynamic Type, and the "Driving Range Ready" card no longer covers the metrics. In landscape the controls share one row.
  • The shot table switches to one card per shot at large text sizes instead of cutting clubs and numbers short ("Dri…", "1…").

Test plan

  • Commit gate (full invariant chain), rerun after rebasing on feat: shot detail sheet with mini ball flight, and shot shape at a glance #107.
  • xcodebuild … build (iosApp)
  • :feature:range:ui:connectedDebugAndroidTest (52/52), including the new RangeLargeTextTest (3/3).
  • iOS Range UI tests (19/19), including RangeLargeTextUITests, on iOS 26.5 (not yet on iOS 27).
  • Before and after screenshots at the largest text size on both platforms.

🤖 Generated with Claude Code

btripp and others added 2 commits October 11, 2026 09:56
- Prev/Play/Next stay on screen; the metrics scroll above them when they
  don't fit, in portrait and narrow landscape (Android and iOS).
- iOS: Ball speed and Carry scale with Dynamic Type, the "Driving Range
  Ready" card no longer covers the metrics, landscape controls share a row.
- Shot table switches to one card per shot at large text instead of
  truncating clubs and numbers.
- RangeLargeTextTest (Android) and RangeLargeTextUITests (iOS) cover it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@btripp
btripp merged commit f9900a9 into main Oct 11, 2026
7 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