Zygote requires `--no-sandbox` option for Chrome about capybara-chrome HOT 4 OPEN

Hey @katyp, great hearing from you! I hope you're doing AWESOME as well!

I'm kicking myself for not making CHROME_ARGS configurable. And for not making it easier to swap out the browser with a subclass of browser, something like that.

I think the best way to proceed would be to add chrome_args to Configuration and merge it into the defaults in service.rb.

You're right, this project is on the back burner, or even the back back back burner…I mean, I don't even have a copy of Ruby installed on my machine besides the stock Mac version, but I'll happily accept the code contribution. And I'm sure that if I start at it long enough, I can figure out how to cut a release.

Pretty neat that this is still being used. Last I checked there are at least 3 other Chrome remote debugging protocol drivers, so it's cool that this one still gets some use. This was a fun project to write, but it's not without its warts. I just wish I could have solved the timing issues in a more atomic fashion.

from capybara-chrome.

@katyp let me know if this PR helps #3

You'd have to manually assemble the array of args yourself, but you can pull in a copy of CHROME_ARGS to get the defaults.

from capybara-chrome.

@sandro Well, you're very on issue responses considering!

YES, that is perfect! The developer we have working on our test suite said it resolves his issue.

Do you need us to do any additional testing or anything given your lack of ruby? ;)

Thanks for the gem, the responses, the PR, and just generally for being.

from capybara-chrome.

@katyp Great! I cut a release. Let me know if there are any issues.

from capybara-chrome.