Disable Chrome code sign clones #555
Merged
Conversation
This file contains hidden or 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
This prevents the creation of /private/var/folders/*/*/*/com.google.Chrome.code_sign_clone folders, that end up taking a heavy storage space on macOS; see teamcapybara/capybara#2795 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This prevents the creation of /private/var/folders///*/com.google.Chrome.code_sign_clone folders, that end up taking a heavy storage space on macOS; see teamcapybara/capybara#2795 (comment)
This was previoulsy reported for Ferrum in #500.
I haven't seen specifics specs for default browser options, so I only adjusted them and added details in the commit message to document the change. Feel free to ask for more changes if need be; while I am not used to developing gems if you have some pointers to improve this PR I'm all ears.