Simplify PIN dialog closing assumptions
Don't require the implementations of the SecurityTokenPinDialogHost interface to run any callback when CloseSecurityTokenPinDialog() is called. The caller knows anyway that the dialog is being closed, so it's just unnecessary and error-prone to rely on every implementation to notify the caller about the closing. This is a small refactoring, which should have no effect on the currently implemented behavior. This change should slightly simplify writing other implementations of the PIN dialog host - for the Login/Lock screens. Bug: 964069 Change-Id: Ied94a1e90bb3f4063081427888d8fcc566719777 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743729 Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Reviewed-by:Igor <igorcov@chromium.org> Cr-Commit-Position: refs/heads/master@{#685164}
Showing
Please register or sign in to comment