Skip to content

Conversation

@aslushnikov
Copy link
Contributor

@aslushnikov aslushnikov commented Sep 13, 2017

This patch teaches puppeteer.launch to run chromium with disabled
chrome extensions and google translate services.

References #760

@aslushnikov
Copy link
Contributor Author

@ebidel it turned out I don't really know why we want this in. Why would we want this?

@ebidel
Copy link
Contributor

ebidel commented Sep 14, 2017

Keep the launched chrome slimmer? Not sure it adds a ton of value for us. Turning these off makes more sense for Lighthouse where we're reusing an existing install of chrome.

@aslushnikov
Copy link
Contributor Author

I slept with this and now I like the patch since it aligns headful/headless with each other.
@JoelEinbinder any concerns?

@aslushnikov aslushnikov merged commit 86b05da into puppeteer:master Sep 15, 2017
@cretz
Copy link

cretz commented Sep 21, 2017

@aslushnikov , @JoelEinbinder, et al - Sadly creating and merging this has disabled everyone's ability to automate with extensions in non-headless mode. Is there any way to work around this, or are these "default" args more like "permanent unchangeable" args?

@aslushnikov
Copy link
Contributor Author

@cretz @JoelEinbinder is working on a patch to override default arguments. Filed #872 to track progress.

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.

4 participants