I _think_ for policy reasons all of Chromes experimental flags have deprecation deadlines to ensure they it doesn't accumulate endless flags that eventually break. These deadlines can be moved.
All past bumps however were only done by updating flag-metadata.json (this includes the most recent bump to M115 as well). Changing the user-facing message is new, and it doesn't help that the commit author is Vignesh Venkatasubramanian, who developed AVIF muxer for FFmpeg in the past. M115 therefore might be the final deadline this time.
Comments
As funny as this is, I don't think this is true.
I _think_ for policy reasons all of Chromes experimental flags have deprecation deadlines to ensure they it doesn't accumulate endless flags that eventually break. These deadlines can be moved.
Just search the jxl issue for "expiry", they've bumped it a few times already: https://bugs.chromium.org/p/chromium/issues/detail?id=117805...
All past bumps however were only done by updating flag-metadata.json (this includes the most recent bump to M115 as well). Changing the user-facing message is new, and it doesn't help that the commit author is Vignesh Venkatasubramanian, who developed AVIF muxer for FFmpeg in the past. M115 therefore might be the final deadline this time.