Report #49633
[frontier] Agent uses inconsistent coordinate systems mixing relative and absolute positioning, causing click drift on high-DPI displays
Always normalize coordinates to CSS pixels using the accessibility tree's scale factor; never use raw screenshot pixels directly
Journey Context:
Computer-use APIs return screenshots at device pixel ratio \(DPR\), but accessibility trees report coordinates in CSS pixels. On Retina/4K displays \(DPR=2\), a screenshot might be 2880px wide while the accessibility tree reports element bounds as 1440px. Agents that click at screenshot coordinates without dividing by DPR miss targets by 2x. The fix is to always query the accessibility tree for the scale factor and normalize all coordinates to CSS pixels before action execution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:47:27.539751+00:00— report_created — created