[variations] Enable sticky activation on Canary. This implements VariationsServiceClient::IsStickyActivationEnabled() for Chrome, iOS, and WebView. The function returns true if the current channel is UNKNOWN or CANARY, enabling studies with sticky activation on these channels. (Unknown channel can be the case in tests.) The method ordering in the header and implementation files has been made consistent for the modified classes. This has the effect of the new StickyActivationManager (implemented under crbug.com/435630455) of running on canary and studies with the STICKY_AFTER_QUERY activation mode being handled. Once this is out on canary, I plan on exercising these changes with a test study. The extra channel-gating is a safety precaution to ensure the new functionality doesn't get widely rolled out before it has been sufficiently tested in the wild. Bug: 435630455 Change-Id: I7d300e026d7e15ca807f6015c0056472ba9e9ae2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6828554 Reviewed-by: Nate Fischer <ntfschr@chromium.org> Auto-Submit: Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/main@{#1499051}
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.