cros: Make sure views-based lock screen is destroyed after it is dismissed.

ash/login/ui/lock_screen.h

Index: ash/login/ui/lock_screen.h
diff --git a/ash/login/ui/lock_screen.h b/ash/login/ui/lock_screen.h
index fcccca615ae29945b5f6c25c0a8ecbde3d25fc2a..c22164770201b0da40d65c2cffeefe89952b6a6b 100644
--- a/ash/login/ui/lock_screen.h
+++ b/ash/login/ui/lock_screen.h
@@ -15,6 +15,9 @@ namespace ash {
 // The lock screen communicates with the backend C++ via a mojo API.
 ASH_EXPORT bool ShowLockScreen();
 
+// Destroys the lock screen. There must be an existing lock screen instance.
+ASH_EXPORT void DestroyLockScreen();

[xiyuan, 2017/06/05 20:39:33]

I would prefer to expose ShowLockScreen and DestroyLockScreen in
mojom::LockScreen and add the impl of both to LockScreenController.

[jdufault, 2017/06/06 21:48:43]

I've changed the approach to go through mojo. I've added a callback to
AuthenticateUser since I believe it makes sense for ash to decide when to
dismiss the lock screen (ideally chrome has little control over lock screen
life-time).

+
 }  // namespace ash
 
 #endif  // ASH_LOGIN_UI_LOCK_SCREEN_H_