1ce804397f
It previously did some of the logic of dismiss() itself: checking to see if the KG is secure, and if not, proceeding to call keyguardDone() to actually hide everything. But now that we have the "bouncer" authentication UI, the WM should let the keyguard challenge the user to see if even a secure keyguard should be dismissed. (Insecure keyguards should behave exactly has they did before.) Unless, of course, the KVM is in a "dismissable" state, in which case it's safe to call keyguardDone() directly. (This can happen if the user has *already* authenticated and we're ending up in this codepath in response.) Bug: 7458531 Change-Id: I9571acf19f9bcc16bba7a826f916da7be8ca9c33