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

[Feature]: Remote Browser Control via API #31178

Closed
KSemenenko opened this issue Jun 5, 2024 · 3 comments
Closed

[Feature]: Remote Browser Control via API #31178

KSemenenko opened this issue Jun 5, 2024 · 3 comments

Comments

@KSemenenko
Copy link

🚀 Feature Request

Connecting to a remote browser can be very useful. For instance, if I have a browser running on a virtual machine, I need a way to connect to it. It would be great to use an API to connect to that machine and control the browser from my computer, as if it were running locally.

Example

Remote connection, remove browser control. Remove view. like I use browser operating on a virtual machine with a Japanese language in OS, and I need to do automation on it, take some screenshot, press some buttons.

Motivation

I have a lot of workers that control the browser on my virtual machines, and every time I need to do authorization or save cookies, but sometimes it happens that I need exactly one browser for one user. and so I would know that somewhere there is a browser running and I can use it from other machines.

@mxschmitt
Copy link
Member

Playwright already offers running browsers remotely in the library:

And you can also use it inside the test-runner as well: #26482

Not sure if I understand your use-case entirely. If this is about combining manual interaction with automated Playwright end-to-end testing, this is not something we recommend/support.

@KSemenenko
Copy link
Author

It’s about some stable environment where I can run tests.
but it keeps my cookies, state and etc.
your examples looks exactly as I looking for!
thanks a lot!

@mxschmitt
Copy link
Member

If its about keeping cookies/state we recommend following our auth guide. Closing by that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants