title: How to enable chrome features from the command line?
body: <p>I am trying to test fixes to a single sign-on process that is affected by Chrome's pending changes to the SameSite cookie attribute (see <a href="https://www.chromium.org/updates/same-site" rel="noreferrer">SameSite Updates</a>).</p>
  
  <p>I can enable these two features in chrome://flags to ensure that chrome exhibits the new behaviour:</p>
  
  <pre><code>SameSiteByDefaultCookies
  CookiesWithoutSameSiteMustBeSecure
  </code></pre>
  
  <p>The above link also mentions this additional feature that I also need to set for my tests, to ensure my single sign-on process will continue to work for chrome 81+:</p>
  
  <pre><code>SameSiteDefaultChecksMethodRigorously 
  </code></pre>
  
  <p>However, that feature isn't present in the chrome://flags page. The link suggests I can enable it with a command line option:</p>
  
  <pre><code>--enable-features=SameSiteDefaultChecksMethodRigorously
  </code></pre>
  
  <p>But without the feature showing in chrome://flags it's hard to say whether that feature (a) exists, and (b) has been set.</p>
  
  <p>I also tried setting the other two features from the command line:</p>
  
  <pre><code>--enable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure
  </code></pre>
  
  <p>Again, it's hard to say whether this has worked as the features still appear as 'Default' in chrome://flags.</p>
  
  <p>From chrome://version I can see the full command line, and that my option has been placed before the --flag-switches-begin option. So I tried again with this command line:</p>
  
  <pre><code>--flag-switches-begin --enable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure --flag-switches-end
  </code></pre>
  
  <p>chrome://version now shows the command line as:</p>
  
  <pre><code>--flag-switches-begin --enable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure --flag-switches-end --flag-switches-begin --flag-switches-end --enable-audio-service-sandbox
  </code></pre>
  
  <p>I.e. something is adding a second pair of --flag-switches-begin --flag-switches-end. And the features remain set to 'Default' in chrome://flags.</p>
  
  <p>chrome://version</p>
  
  <pre><code>80.0.3987.42 (Official Build) beta (64-bit) (cohort: Beta)
  Revision    fef3617f1566dc6972bc613792b56edb25311554-refs/branch-heads/3987@{#436}
  </code></pre>
  
  <p>Any ideas?</p>
  
  <p>Thanks.</p>