Extend expiration for several site isolation flags. disable-process-reuse: this flag is still useful for additional protection against certain types of side channel attacks, at the cost of more processes being created. It's also useful to see if process reuse is to blame for a particular issue. This isn't practical to ship at this time, but doing smarter process reuse policies in the future is on our radar. site-isolation-trial-opt-out: this is still useful for debugging site isolation issues on both Android and desktop (especially on ChromeOS). enable-site-isolation-for-password-sites: for now, this is useful as an opt-in for partial site isolation on low-end Android devices, where this mode is disabled by default. isolate-origins: this is useful for debugging origin isolation, where more work is planned in the near future, as well as for manually isolating additional sites on Android, beyond those covered by heuristics. Change-Id: I8f1fe4eaabf03511fdaca8eb25c6929324edb4c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4025774 Reviewed-by: Charlie Reis <creis@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/main@{#1071148}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.