Skip to content

Set Chrome flags manually #6

@alebelcor

Description

@alebelcor

As far as I know there's no programmatic way to set Chrome flags, unless it's via command-line arguments on startup.

So I'm instead documenting them here so I can enable/disable them manually until I find a workaround.

Enable these flags:

  • chrome://flags/#allow-insecure-localhost
  • chrome://flags/#enable-devtools-experiments

Disable these flags:

  • chrome://flags/#autofill-profile-server-validation
  • chrome://flags/#data-saver-server-previews
  • chrome://flags/#enable-autofill-account-wallet-storage
  • chrome://flags/#enable-autofill-credit-card-upload
  • chrome://flags/#enable-autofill-save-card-sign-in-after-local-save
  • chrome://flags/#enable-autofill-send-experiment-ids-in-payments-rpcs
  • chrome://flags/#enable-navigation-tracing
  • chrome://flags/#enable-network-logging-to-file
  • chrome://flags/#enable-offer-store-unmasked-wallet-cards
  • chrome://flags/#enable-speculative-service-worker-start-on-query-input
  • chrome://flags/#hardware-media-key-handling
  • chrome://flags/#network-service
  • chrome://flags/#omnibox-experimental-keyword-mode
  • chrome://flags/#omnibox-group-suggestions-by-search-vs-url
  • chrome://flags/#omnibox-local-entity-suggestions
  • chrome://flags/#omnibox-rich-entity-suggestions
  • chrome://flags/#omnibox-tail-suggestions
  • chrome://flags/#safe-search-url-reporting
  • chrome://flags/#show-autofill-type-predictions
  • chrome://flags/#site-characteristics-database
  • chrome://flags/#sync-support-secondary-account
  • chrome://flags/#top-sites-from-site-engagement

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions