From 50981545858b3ab13be2e1fed00c76a7a8a77ffc Mon Sep 17 00:00:00 2001 From: "Tommy D. Rossi" Date: Wed, 11 Feb 2026 16:16:39 +0100 Subject: [PATCH] docs: avoid focus stealing in framer iframe workflow Document the page-reuse pattern for the Framer project tab so repeated checks do not spawn duplicate tabs, and explicitly ban bringToFront in this guide to avoid interrupting the active browser window during local debugging. --- docs/framer-iframe-snapshot-guide.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/framer-iframe-snapshot-guide.md b/docs/framer-iframe-snapshot-guide.md index da49a5b..996ba70 100644 --- a/docs/framer-iframe-snapshot-guide.md +++ b/docs/framer-iframe-snapshot-guide.md @@ -16,6 +16,14 @@ prompt: | ## Step-by-step +- Always reuse an existing Framer tab when possible (do not open a new page each run). + Use this pattern to pick an existing page first, then navigate only if needed: +```bash +playwriter -s 1 -e "const target = 'https://framer.com/projects/unframer-source--XOxwdyyCrFEE9uKnKFPq-6gX7n?node=augiA20Il'; const framerPage = context.pages().find((p) => p.url().includes('framer.com/projects/unframer-source')) || page; if (!framerPage.url().includes('framer.com/projects/unframer-source')) { await framerPage.goto(target, { waitUntil: 'domcontentloaded' }); } console.log(framerPage.url());" +``` + +- Never call `bringToFront()` in this flow. It steals focus and interrupts manual work while tests are running. + - Open the Framer project URL in Chrome: https://framer.com/projects/unframer-source--XOxwdyyCrFEE9uKnKFPq-6gX7n?node=augiA20Il