Closed andrea11 closed 1 week ago
Can someone review this PR? (@willdurand maybe?)
I'd prefer to not auto-download a bunch of extra stuff, but since it is currently possible to add it again, but not to opt out, I reluctantly approve this change.
I am not clear on what that means, @Rob--W.
I'd prefer to not auto-download a bunch of extra stuff, but since it is currently possible to add it again, but not to opt out, I reluctantly approve this change.
I am not clear on what that means, @Rob--W.
I am approving this change, even if it means that Chrome will auto-download some additional components after startup. This will utilize extra bandwidth and CPU when launching (new) browser profiles instances. In exchange for that downside, the upside is that the launched Chrome browser will more closely match production. One example of that is that websites requiring DRM will work.
If devs want to revert to the behavior from before, they can manually add the command line flag to web-ext run
.
TL;DR: LGTM, let's merge.
Similarly to puppeteer/puppeteer#13010, Quoting @mathiasbynens:
Disable this flag grant more flexibility, and it can always be disabled via the
web-ext run --arg option