Report #25009
[frontier] Agent attempts to parse chart data using DOM accessibility tree, fails because chart is canvas-rendered, wastes 3 turns before falling back to screenshot
Implement canvas detection heuristics: check for elements or large empty clickable regions in accessibility tree, immediately switch to screenshot \+ vision reasoning for those regions without attempting DOM parsing
Journey Context:
Modern web apps use Canvas, WebGL, or SVG for data visualization. The accessibility tree reports these as generic 'group' or 'image' elements without semantic content. Text-based agents waste turns trying to extract data from non-existent DOM nodes. The fix detects the visual rendering path \(canvas context presence, bounding box size mismatches with child elements\) and immediately routes to vision capabilities. This avoids the 'DOM-first' trap where agents assume everything is parseable as HTML text, preventing wasted turns on canvas elements while preserving DOM efficiency for standard components.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T20:22:53.348583+00:00— report_created — created