-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): Upgrade chrome-launcher from 0.15.1 to 1.1.2 #3200
Conversation
chrome-launcher
to 1.1.2There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
None of the changes to the default flags seem relevant to extensions so I didn't adjust the filtering, but someone more familiar with browsers might want to double check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@@ -49,7 +49,7 @@ describe('util/extension-runners/chromium', async () => { | |||
it('uses the expected chrome flags', () => { | |||
// Flags from chrome-launcher v0.14.0 | |||
const expectedFlags = [ | |||
'--disable-features=Translate', | |||
'--disable-features=Translate,OptimizationHints,MediaRouter,DialMediaRouteProvider,CalculateNativeWinOcclusion,InterestFeedContentSuggestions,CertificateTransparencyComponentUpdater,AutofillServerCommunication,PrivacySandboxSettings4', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do any of these cover the new search engines picker? It's quite annoying.
Starting a new profile (web-ext run --target chromium
) is basically a whack-a-mole.
Extracted from #2912, and replaces #3170.