Add the --no-sandbox argument for Chrome Set Headless #3740
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…at occurred when using the script. The --no-sandbox argument disables the sandbox mode in Chrome
|
Thanks for the contribution! Before we can merge this, we need @xmtigra to sign the Salesforce Inc. Contributor License Agreement. |
|
@xmtigra Thanks for your contribution. We've reviewed the addition of the If you need to use Chrome without the sandbox in your local setup, you can customize your Robot Framework test suite to add this argument when you open the browser. I'm closing this PR now. If you have any questions or need to discuss this further, please let us know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The last command was added to address an issue related to an error that occurred when using the script. The --no-sandbox argument disables the sandbox mode in Chrome