Issue 883100 link

Starred by 1 user

Issue metadata

Status:	Available
Owner:	----
Cc:	█ jlklein@chromium.org hsuregan@chromium.org nohle@chromium.org khorimoto@chromium.org █ jhawkins@chromium.org hansberry@chromium.org
Components:	UI>SmartLock
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	3
Type:	Bug

EasyUnlockServiceRegular: directly use MultiDeviceSetupClient::GetFeatureState

Project Member Reported by hansberry@chromium.org, Sep 11

Issue description

As per suggestion on https://chromium-review.googlesource.com/c/chromium/src/+/1211246/10/chrome/browser/chromeos/login/easy_unlock/easy_unlock_service_regular.h#236, do not cache feature state, but rather grab directly.

Comment 1 by jhawkins@google.com, Nov 6

Owner: hansberry@chromium.org
Status: Assigned (was: Available)

Comment 2 by hansberry@chromium.org, Nov 15

Cc: -jordynass@chromium.org hsuregan@chromium.org
Owner: ----
Status: Available (was: Assigned)

This is still a nice cleanup, but it's low priority and I don't plan to take it on any time soon. Marking unassigned.

►

Issue 883100 link

Issue metadata

EasyUnlockServiceRegular: directly use MultiDeviceSetupClient::GetFeatureState

Issue description

Comment 1 by jhawkins@google.com, Nov 6

Comment 1 Deleted

Comment 2 by hansberry@chromium.org, Nov 15

Comment 2 Deleted

Sign in to add a comment