Report #53678
[frontier] Agents fail to scroll correctly because they process full-page screenshots as single images, missing off-screen elements and miscalculating scroll distances
Viewport-Aware Chunking with Scroll Intent: Process only the current viewport screenshot, maintain a separate 'world map' text representation of off-screen elements from accessibility tree, and calculate scroll amounts using semantic units \('scroll to section heading'\) rather than pixels.
Journey Context:
Full-page screenshots are too large for context windows and compress text. Agents often try to scroll by predicting pixel distances \(e.g., 'scroll down 500px'\), which breaks on different screen sizes. The robust pattern is 'Semantic Scrolling': the agent's world model splits into 'viewport' \(visual\) and 'document' \(semantic\). The VLM sees only the current viewport image. The executor maintains the full accessibility tree \(which is lightweight text\). To scroll, the VLM specifies target element name \('scroll until 'Reviews' heading visible'\), executor calculates required scroll offset from AX tree, executes scroll, captures new viewport. This handles responsive layouts and varying screen sizes gracefully.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:35:44.048455+00:00— report_created — created