-
Notifications
You must be signed in to change notification settings - Fork 717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playwright support broken as of v1.4.0 #1016
Comments
The following will hang at const pw = require('playwright');
(async () => {
const browser = await pw.chromium.connect({
wsEndpoint: 'wss://chrome.browserless.io?token=YOUR-API-TOKEN',
});
const context = await browser.newContext();
const page = await context.newPage();
await page.goto('https://www.example.com/');
await page.screenshot({ path: 'example.png' });
await browser.close();
})(); Note that the official browserless example uses |
Thanks for this, will take a look and see what's going on behind the scenes. We're working on migrating to playwright internally, but it might take some time :) |
This is fairly unfortunate, as playwright has gone away from chromes embedded protocol over to their own proprietary one. This forces browserless to do one of two potential things to fix this:
In either case both would require a bit of work to do so. I’m not sure why the breaking change on their library, as it doesn’t seem to buy much in my opinion. The transport layer is the same, and CDP already allows for cross-language/runtime compatibility. |
I agree, this is a massive breaking change that's not even documented (the API docs for |
Related Playwright issue: microsoft/playwright#4054 |
Should be fixed in #1018. Docs are needing to be updated, but you'll need to do a connection on |
Fix is now everywhere in our platform. Closing |
Describe the bug
Playwright support worked fine until version v1.4.0. That version introduced a new wire protocol, see https://github.com/microsoft/playwright/releases/tag/v1.4.0
To Reproduce
Install latest playwright (v1.4.2 as of writing). Connecting won't work, however when downgrading to v1.3.0 things work fine.
The text was updated successfully, but these errors were encountered: