This bug requires manual review: M68 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), kariahda@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Why does this need to be merged to M68 vs waiting until M69?

It doesn't strictly need to merged to 68, but we're running Finch experiments that are currently useless due to this being accidentally turned off. We'd prefer not to have to wait for 69 to start collecting data again. 

How safe is this merge overall and well tested in canary?

I believe it's pretty safe. 

The change is small and re-enables a feature that was previously tested, stable and working in canary, dev, and beta before being inadvertently deactivated. 

The feature is currently performing as expected in Canary according to both manual testing and UMA, and has normal stability numbers. 

Approving merge to M68. Branch:3440

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The merge commit wasn't auto-linked to this bug. It landed at refs/branch-heads/3440@{#531} on the 26th

See https://crrev.com/c/1115378

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot