We disabled both the browser’s same-site-by-default-cookies and cookies-without-same-site-must-be-secure in flag because the development environment required it. However, after update to version 91, Chromium directly turned off the option (Chromium update log) and set it to default, so it can’t be set in flag.

The flags #same-site-by-default-cookies and #cookies-without-same-site-must-be-secure have been removed from chrome://flags as of Chrome 91, as the behavior is now enabled by default. In Chrome 94, the command-line flag –disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure will be removed.

That is, we can pass in the command line as a startup parameter when the APP starts:

    1. (Windows) Right-click Chrome/Edge shortcut and click “Properties”. To the end of the “Target” property--disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecureThen restart the browser.
  • 2. (Mac) Add startup parameters to the browser using a script
    • 2.1 Create a new text (e.gChromeStart)
    • 2.2 Then EditChromeStart 
      #! /bin/bash "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --args --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecureCopy the code
    • 2.3 Adding The Execution Permission to a Script 
      sudo chmod u+x "ChromeStart"
Copy the code
    • 2.4 Close the browser and execute the script

Chromium 94 will remove the comman-line option as well because, according to the official statement, if developers are allowed to disable these options, they become an easy target. So Chromium has chosen to gradually close this channel to protect developers.

Add boot parameters for Mac Chrome