[Feature] Allow connecting to CEF instances via `browserType.connectOverCDP`
See original GitHub issueContext:
- Playwright Version: [Version 1.17.1]
- Operating System: [Windows]
- Node.js version: [v12.16.1]
- Browser: [ CEF | 90.6.3+gc53c523+chromium-90.0.4430.93]
- Extra:
- CEF | 90.6.3+gc53c523+chromium-90.0.4430.93 Chromium | 90.0.4430.93 OS | Windows WebKit | 537.36 (@4df112c29cfe9a2c69b14195c0275faed4e997a7) JavaScript | 9.0.257.23 User Agent | Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93; ) Safari/537.36
Code Snippet
import { test, expect ,chromium } from ‘@playwright/test’;
test(‘my test’, async () => {
const cdpBrowser1 = await chromium.connectOverCDP({
wsEndpoint: ws://localhost:9222/devtools/browser/01582b7e-7cb0-4bed-a8b1-5e211d3a3ab6
,
});
});
Describe the bug
I have an application that uses the chromium version 90 from CEF as a browser . when I run the above snippet it throws the following exception: browserType.connectOverCDP: Protocol error (Browser.setDownloadBehavior): Browser context management is not supported. =========================== logs =========================== <ws connecting> ws://localhost:9222/devtools/browser/01582b7e-7cb0-4bed-a8b1-5e211d3a3ab6 <ws connected> ws://localhost:9222/devtools/browser/01582b7e-7cb0-4bed-a8b1-5e211d3a3ab6 ============================================================
6 | const cdpBrowser1 = await chromium.connectOverCDP({ ^ 7 | wsEndpoint:
ws://localhost:9222/devtools/browser/01582b7e-7cb0-4bed-a8b1-5e211d3a3ab6
, 8 | }); 9 | console.log('connected ');
at D:\projects\playwright\tests\demo.spec.ts:6:39
at FixtureRunner.resolveParametersAndRunHookOrTest (D:\projects\\playwright\node_modules\@playwright\test\lib\fixtures.js:306:12)
at WorkerRunner._runTestWithBeforeHooks (D:\projects\playwright\node_modules\@playwright\test\lib\workerRunner.js:499:7)
same snippet works fine for the chromium browser 90 when it launched via: “C:\Users\rakshetri\AppData\Local\Google\Chrome\Application\chrome.exe” --remote-debugging-port=9333 – “%1”
Issue Analytics
- State:
- Created 2 years ago
- Reactions:32
- Comments:11 (5 by maintainers)
@mxschmitt I am evaluating playwright for our automation requirements and so far it seems to be a great e2e testing framework!!..We also need this feature to connect to CEF. Most of the latest testing frameworks do support Chromium Embedded Framework… Waiting to have it supported by playwright soon.!!
@mxschmitt thank you very much I will be highly appreciate your efforts towards this . I am eagerly waiting for this support as this is road blocking for our CEF e2e testing with PW.