playwriter
Code Issues

docs: avoid focus stealing in framer iframe workflow

Browse Source 
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.
This commit is contained in:
Tommy D. Rossi
2026-02-11 16:16:39 +01:00
parent e6f1e8c089
commit 5098154585
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/framer-iframe-snapshot-guide.md
+8
View File
@@ -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