Question Regarding (Possible) Deprecated Flag

1 view
Skip to first unread message

Franco Pieri

unread,
Jan 13, 2026, 6:48:09 PMJan 13
to site-isol...@chromium.org
Hi!

I'm contacting you because I found your email through Chromium's Gerrit. 

Sorry for the random email, but I promise it's worth your time to read! My name's Franco Pieri, and I'm a computer science student. This year, I contributed to Google's Chromium project by developing the “Open” button, now visible on the history page of Chrome 140 and later versions. 

I'm reaching out because I've noticed that the flag 'site-isolation-trial-opt-out' has passed its designated expiry milestone. Should the flag be removed or extended? I’m looking for further contribution experience, and I'm happy to handle it if needed. If you would prefer to handle this yourself, I completely understand.

I also wanted to ask whether you might know of other ways I could continue contributing to Chrome. I would be happy to assist with additional bug fixes or other project tasks as needed.

Thank you!

Best,
Franco Pieri 

Alex Moshchuk

unread,
Jan 14, 2026, 5:33:51 PMJan 14
to Franco Pieri, site-isol...@chromium.org
Hi Franco,

In general, we'd like to keep this flag, as it's still useful for diagnosing site isolation issues and for simulating behavior on platforms that don't have site isolation. We can consider removing the expiration. Both the flag and the feature name are a bit outdated and could be updated as well, but there are lots of references to existing names in documentation, config files, etc, so it might be a non-trivial effort.

We're a little confused, though, because this flag doesn't expire until M150: https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/flag-metadata.json;l=8694;drc=5b205ca1dffb207d8eee3e19d482e0c4d05a6bbb. What criteria were you using to determine that a flag was past its expiration?

Thanks,
Alex
Reply all
Reply to author
Forward
0 new messages