See more context in https://bugs.chromium.org/p/chromium/issues/detail?id=893769. Once M71 is on stable, we should be able to remove this legacy handling in M72 because all hosts should be rolled out by then.
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8a29a5503371d6aeb9f237939c75f68e84d27efd commit 8a29a5503371d6aeb9f237939c75f68e84d27efd Author: Regan Hsu <hsuregan@chromium.org> Date: Fri Jan 11 03:47:59 2019 [CrOS MultiDevice] Remove legacy handling for EasyUnlock Legacy feature state handling for EasyUnlock can be removed now that M71 is stable, and beacuse all hosts should be rolled out already. Bug: 894585 Change-Id: Ica33017847766db00f1b940346493a58b2fecb3a Reviewed-on: https://chromium-review.googlesource.com/c/1391312 Commit-Queue: Regan Hsu <hsuregan@chromium.org> Reviewed-by: Ryan Hansberry <hansberry@chromium.org> Cr-Commit-Position: refs/heads/master@{#621893} [modify] https://crrev.com/8a29a5503371d6aeb9f237939c75f68e84d27efd/chrome/browser/chromeos/login/easy_unlock/easy_unlock_service.cc [modify] https://crrev.com/8a29a5503371d6aeb9f237939c75f68e84d27efd/chrome/browser/chromeos/login/easy_unlock/easy_unlock_service.h [modify] https://crrev.com/8a29a5503371d6aeb9f237939c75f68e84d27efd/chrome/browser/chromeos/login/easy_unlock/easy_unlock_service_regular.cc [modify] https://crrev.com/8a29a5503371d6aeb9f237939c75f68e84d27efd/chrome/browser/chromeos/login/easy_unlock/easy_unlock_service_regular.h [modify] https://crrev.com/8a29a5503371d6aeb9f237939c75f68e84d27efd/chromeos/components/proximity_auth/proximity_auth_profile_pref_manager.cc [modify] https://crrev.com/8a29a5503371d6aeb9f237939c75f68e84d27efd/chromeos/components/proximity_auth/proximity_auth_profile_pref_manager.h [modify] https://crrev.com/8a29a5503371d6aeb9f237939c75f68e84d27efd/chromeos/components/proximity_auth/proximity_auth_profile_pref_manager_unittest.cc
Comment 1 by hansberry@chromium.org
, Nov 13Labels: -M-71