Flags come and go as a natural part of the development process; they're
almost an internal thing. If you found a particular flag useful, though,
consider filing a feature request for a more well-engineered version of the
functionality; a permanent fix often looks quite different from a
"temporarily
On Wednesday, 29 September 2021 at 17:56:49 UTC+2 km...@chromium.org wrote:
> All chrome://flags are temporary, and should never be relied on as
> permanent controls over behavior:
>
> https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/docs/flag_expiry.md#Do-Not-Depend-On-Flag
All chrome://flags are temporary, and should never be relied on as
permanent controls over behavior:
https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/docs/flag_expiry.md#Do-Not-Depend-On-Flags
On Wed, Sep 29, 2021 at 8:39 AM Luca Fabbri wrote:
> From https://www.chromium.org/
>From https://www.chromium.org/updates/same-site I read:
*Mar 18, 2021:* 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
-
