Skip to content

Comments

Added support for using local chrome browser instance#9

Open
kranthi419 wants to merge 2 commits intohrithikkoduri:mainfrom
kranthi419:feature/LocalBrowserInstanceUse
Open

Added support for using local chrome browser instance#9
kranthi419 wants to merge 2 commits intohrithikkoduri:mainfrom
kranthi419:feature/LocalBrowserInstanceUse

Conversation

@kranthi419
Copy link

Hi @hrithikkoduri , Please checkout this feature request of using local chrome use instance instead of playwright instance.

@kranthi419 kranthi419 changed the title Added support for local browser use Added support for using local chrome browser instance Jan 30, 2025
@hrithikkoduri
Copy link
Owner

@kranthi419
I tried implementing your solution, but wasn't able to initialize a local instance for chrome browser.

I have created a new PR #13 , please check that

Few key points about it

  • Allows local instance to use the system browser on remote debugging with Playwright.
  • Removes the need to manually set environment variables for Chrome executable path and profile selection.
  • Prompts the user to select a profile while connecting to the browser and initializes the variables automatically.

Let me know how its works.

@kranthi419
Copy link
Author

kranthi419 commented Jan 31, 2025

added a comment @hrithikkoduri in the PR, wrt to chrome instance path under "async def launch_chrome_with_remote_debugging(self):" ... for windows, it can be "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" as well.

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

Successfully merging this pull request may close these issues.

2 participants