Report #92939
[frontier] Agent executes actions during CSS animations and loading states because they only check DOM readyState
Implement pixel-stability gating: capture screenshot at t and t-1, calculate MSE; if >0.02, wait and re-capture before executing any click or type action
Journey Context:
DOM readyState lies constantly—CSS animations, lazy-loaded images, and JS-driven renders happen after DOMContentLoaded. Fixed sleeps are too slow for fast UIs and too fast for slow networks. MutationObserver misses CSS transitions. Pixel-diff is the ground truth of visual stability. Tradeoff: you store the previous frame \(memory\) vs reliability. The 0.02 threshold catches most UI shifts without triggering on video content.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:35:00.902373+00:00— report_created — created