Skip to content
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

feat: ability to send headers when connect to browser using puppeteer #9354

Merged

Conversation

DudaGod
Copy link
Contributor

@DudaGod DudaGod commented Dec 8, 2022

Proposed changes

I have browsers pool in some cloud. I want that only users with access will be able to connect to them. So they must provide token through headers. But wdio does not send headers when connect to browser using puppeteer, because puppeteer didn't support it before. But from puppeteer-core@19.4.0 it became possible (PR in puppeteer - puppeteer/puppeteer#9314).

Moreover I want to support it for webdriverio@7, but branch v7 - https://github.com/webdriverio/webdriverio/tree/v7 use puppeteer-core@13.1.3 - https://github.com/webdriverio/webdriverio/blob/v7/packages/webdriverio/package.json#L79. And I'm not sure that I can bump it to 19. What should I do with it?

Reviewers: @webdriverio/project-committers

Copy link
Member

@christian-bromann christian-bromann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we update the docs to reflect that headers are also used when connecting to Puppeteer using the devtools automation protocol?

@DudaGod DudaGod force-pushed the feat.cdp_connect_with_headers branch from efe8883 to c227141 Compare December 9, 2022 08:52
@DudaGod
Copy link
Contributor Author

DudaGod commented Dec 9, 2022

Can we update the docs to reflect that headers are also used when connecting to Puppeteer using the devtools automation protocol?

Fixed. And can you answer for my question about webdriverio@7? Thank you.

@christian-bromann
Copy link
Member

And I'm not sure that I can bump it to 19. What should I do with it?

Feel free to bump to v19, there might be some problems that got fixed in main, we stopped updating because we were running into these.

Copy link
Member

@christian-bromann christian-bromann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: New Feature 🚀 PRs that contain new features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants