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

Add GetBrowserPid option to browser.go #566

Closed
wants to merge 1 commit into from
Closed

Conversation

Ajod
Copy link

@Ajod Ajod commented Jan 27, 2020

The process PID can come in handy when there is talk about running a third party software against a remotely controlled browser.

New PR from clean fork

@mvdan
Copy link
Contributor

mvdan commented Jan 31, 2020

The process PID can come in handy when there is talk about running a third party software against a remotely controlled browser.

I don't get what the purpose here is. Can you provide an example?

Also, the API seems pretty stiff. Why not expose https://golang.org/pkg/os/#Process? We could expose and document the field in Browser. It wasn't done initially because, in general, it's not very useful.

@mvdan
Copy link
Contributor

mvdan commented May 1, 2020

Friendly ping @Ajod. This would also need a test before merging.

Copy link
Contributor

@mvdan mvdan left a comment

Choose a reason for hiding this comment

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

Reminder for myself that this isn't ready for merging.

@Ajod
Copy link
Author

Ajod commented May 29, 2020

Hi, based on your comment that it might not have a purpose I eventually ended up not needing to expose the PID or the Process at all. This would probably a somewhat pointless PR and I should probably close it if that is okay with you

@mvdan
Copy link
Contributor

mvdan commented May 29, 2020

Sounds good, thanks!

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.

None yet

2 participants