[Bug]: Weekend Hub card — page scroll snaps back to top in the iOS Companion App (works in desktop browser) #696

Prerequisites

• I am running the latest version of F1 Sensor
• I have searched existing issues
• I have restarted Home Assistant
• All information in this issue, including logs and screenshots, is written in English. Issues containing non-English content will be closed without response.

F1 Sensor Version

5.5.1

Component

Live data card

Device

VMware Workstation VM on an HP EliteDesk mini PC (4 vCPU / 6 GB)

Home Assistant Installation Type

Home Assistant OS

System Architecture

amd64

Screenshot or Screen Recording

No response

Current Behavior

With the new Weekend Hub card (custom:f1-weekend-hub-card) on its own dashboard view, scrolling down the page in the Home Assistant iOS Companion App doesn't stick — the page keeps jumping back to the top, so nothing below the Overview tiles can be read.

The same dashboard and card scroll normally in a desktop web browser.

Environment: HA Core 2026.9.1, HAOS 18.2, iOS Companion App (current App Store version) on iPhone, storage-mode dashboard.

Tried:

• View type sections (max_columns: 1) → snaps to top
• View type panel (single card, full width) → snaps to top
• Same view in a desktop browser → scrolls fine
• Hard refresh / cache clear after updating to 5.5.1 → no change

Card config:
type: custom:f1-weekend-hub-card
entry_id: auto
theme_mode: auto
no_spoiler_entity: switch.f1_no_spoiler_mode

Observations:

• Happened both during a live session (Spanish GP FP2, ~280 timeline events) and after it had finished.
• The card bundle doesn't appear to call scrollTo/scrollIntoView, so it looks like the page height briefly collapsing on re-render with WebKit clamping the scroll position, rather than the card scrolling deliberately.
• The other bundled F1 cards on the same dashboard (Live Session, Race Control, Track Map etc.) scroll fine in the app.

Expected Behavior

The page should hold its scroll position in the Companion App while the card updates, the same as it does in a desktop browser.

Logs

No errors or warnings are logged for f1_sensor when this happens — it is a front-end rendering issue only. Happy to enable debug logging and attach a log if that would help.