browser-use--browser-harness
sergeclaesen
4ec625595a
Documents the Monaco + React-canvas seam that causes most 'automation silently did nothing' failures in Framer: - Double-click requires the full pointer+mouse event chain (detail:2 matters) - Monaco paste must be clipboard + OS-level Cmd+A/Cmd+V, then wait before save - Publish button only mounts when a page is selected in the Pages tab; it rejects synthetic clicks and must be driven by screen-coord input - Framer autolayout preempts programmatic Header position/left/right writes, forcing nodes offscreen; delete-and-copy is the working workaround Plus the list of canvas-level interactions that consistently reject automation (drag-drop, variant switching, property binding, Page Settings) so agents know to escalate to the human instead of retrying. Stable data-testid selectors table for Pages/Layers/Assets tabs, and the edge-cache + sitemap quirks on framer-hosted live domains.