[MCP]: --extension --background: noDefaults skips focus emulation, hidden tabs get no rAF and clicks time out
Maintainers usually reply within 1 day
@yury-s is already working on this.
Since Nov 20, 2026.
- #44101 by @microsoft-playwright-automation — open
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- testing-qa
Research direction
Read packages/playwright-core/src/tools/mcp/extensionContextFactory.ts and packages/playwright-core/src/server/chromium/crPage.ts to trace how noDefaults affects focus emulation; compare the issue’s hidden-tab reproduction with focus emulation enabled. Check linked PR #44101, which is already open. Done means the reported background-tab click and Enter failures are addressed without overriding the user's browser defaults.
Written by the indexing model from the issue text.
Description
Follow-up to #43868, as asked there: with extension 0.5.0 and @playwright/mcp 0.0.85, clicks and Enter still fail in --background tabs. In my setup focus emulation isn't enabled on the controlled tab.
What's going on?
In a tab controlled by @playwright/mcp --extension --background (not the active tab of its window), the page reports:
document.visibilityState === 'hidden',document.hasFocus() === false- 0
requestAnimationFramecallbacks in 2 s, and a 10 mssetTimeoutloop runs about once per second
On https://en.wikipedia.org/wiki/Main_Page:
browser_clickon the "Search" button fails withTimeoutError: browserBackend.callTool: Timeout 5000ms exceeded., and the call log ends atwaiting for element to be visible, enabled and stablebrowser_typewithsubmit: true, and a laterbrowser_press_keyEnter, leave the page on Main_Page: the search is never submitted
Why
In #43868 the comment says Playwright enables focus emulation on each page. On main today, the extension path still connects with noDefaults: true (packages/playwright-core/src/tools/mcp/extensionContextFactory.ts, line 45):
const browser = await playwright.chromium.connectOverCDP(relay.cdpEndpoint(), { isLocal: true, timeout: 0, noDefaults: true });
In packages/playwright-core/src/server/chromium/crPage.ts (lines 547-552), noDefaults on the default context also skips focus emulation:
const skipDefaultOverrides = browserOptions.noDefaults &&
this._crPage._browserContext === this._crPage._browserContext._browser._defaultContext;
...
if (this._isMainFrame() && !skipDefaultOverrides)
promises.push(this._client.send('Emulation.setFocusEmulationEnabled', { enabled: true }));
I understand noDefaults is there so the extension doesn't override the user's existing browser defaults (#42117). Focus emulation goes with them, and it's the setting that lets a background tab render and pass actionability checks.
Repro without the extension
Plain connectOverCDP with noDefaults: true, against Chrome started with --remote-debugging-port=9334 and a fresh --user-data-dir:
const { chromium } = require('playwright-core');
(async () => {
const b = await chromium.connectOverCDP('http://127.0.0.1:9334', { noDefaults: true });
const ctx = b.contexts()[0];
const bg = ctx.pages()[0];
await bg.goto('https://example.com');
const fg = await ctx.newPage(); await fg.goto('https://example.com'); await fg.bringToFront();
const frames = () => bg.evaluate(async () => { const t0 = performance.now(); let n = 0;
await new Promise(r => { const f = () => { n++; performance.now() < t0 + 2000 ? requestAnimationFrame(f) : r(); };
requestAnimationFrame(f); setTimeout(r, 2500); });
return { vis: document.visibilityState, raf: n }; });
console.log(await frames()); // { vis: 'hidden', raf: 0 }
await bg.click('a', { trial: true, timeout: 5000 }).catch(e => console.log('timeout')); // timeout
const s = await ctx.newCDPSession(bg);
await s.send('Emulation.setFocusEmulationEnabled', { enabled: true });
console.log(await frames()); // { vis: 'visible', raf: 97-103 }
await bg.click('a', { trial: true, timeout: 5000 }); // ok
await b.close();
})();
The same setup on the Wikipedia main page, filling the search box in the hidden tab and then pressing Enter or clicking "Search":
visibilityState |
Enter submits the search | click on "Search" | |
|---|---|---|---|
| focus emulation off | hidden | no (still on Main_Page after 8 s) | Timeout 5000ms exceeded, waiting for "stable" |
| focus emulation on | visible | yes | ok, 717 ms |
Through the extension I couldn't turn it on from the MCP side: browser_run_code_unsafe with page.context().newCDPSession(page) returns Protocol error (Target.attachToBrowserTarget): {"code":-32000,"message":"Not allowed"}, and I found no option for it.
Suggestion
Keep noDefaults for the user's browser defaults, but enable Emulation.setFocusEmulationEnabled on the tabs the MCP controls in extension mode, at least with --background.
Version
@playwright/mcp 0.0.85 (playwright-core 1.66.0-alpha-2026-11-09), Playwright Extension 0.5.0, Google Chrome 157.0.8103.52, macOS 27.2, Node 20.6.1. The test in #43868 used Chromium 158.0.8127.2. I haven't tested 158.
- Dominant language
- TypeScript
- Stars
- 100k
- Forks
- 6.9k
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 281
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/playwright
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
agent-triage-done
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/playwright#44264 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/playwright#44290 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
microsoft/playwright#44288 ·
Maintainers usually reply within 1 day
-
[Bug]: page.goto never returns for a load started as a newer service worker takes over (Chromium)Open
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/playwright#44287 ·
Maintainers usually reply within 1 day
All issues in microsoft/playwright
Similar issues
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#203385 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nwverse/persona#12800 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
WISE-Community/WISE-Client#2404 ·
Maintainers usually reply within 1 day