• Jacob Dufault's avatar
    cros: Simplify fingerprint mojom between ash and chrome · 947f2470
    Jacob Dufault authored
    - Renamed FingerprintUnlockState to FingerprintState
    - FingerprintState no longer has AUTH_FAILED and AUTH_SUCCESS. FingerprintState
      instead determines if fingerprint is enabled. A seperate mojom method is used
      to notify the ash that an authentication attempt has taken place.
    - Reordered fingerprint mojom method so it is next to PIN
    - Eliminated ScreenLocker::FingerprintState, which duplicated the mojom type
    - Fixed a bug in screen_locker.cc where timing out PIN depended on fingerprint
      being enabled.
    - Backlights being forced off is now reset only after an authentication attempt.
      This means that fingerprint timing out will not turn the display on.
    - Lock screen is now initialized with full fingerprint state instead of a bool.
    - Renamed some methods to increase clarity
    
    Bug: 897226
    Change-Id: I841c7bbdd32730532148ddae96e1b490bee4eb0a
    Reviewed-on: https://chromium-review.googlesource.com/c/1291998Reviewed-by: default avatarGreg Kerr <kerrnel@chromium.org>
    Reviewed-by: default avatarWenzhao (Colin) Zang <wzang@chromium.org>
    Commit-Queue: Jacob Dufault <jdufault@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#602450}
    947f2470
screen_locker.h 11.3 KB