[CrOS MultiDevice] Stop Setup Flow from accumulating password attempts
The current HEAD behavior of the Setup Flow password page is to allow the user to repeatedly request forward navigation while the IPC for a password check is in progress. Then these requests for a queue so that the next time the user changes the contexts of the password input field, the next request in the queue is sent causing an accidental password check/setup attempt. This CL adds a field to the password page to allow it to determine whether it is in the middle of waiting for a password check to complete and if so, prevent any forward navigation attempt (including from the 'enter' key) and disable the button so the user knows it is out of commission while waiting for the IPC response. The CL also removes some now unused code surrounding expired auth tokens which made it harder to follow the logic flow for the IPC and callback: In the original design, the user would enter their password before they got to the start setup page and would therefore have to hold onto an auth token throughout the flow. In particular, it was necessary to set a timeout leading to a callback to erase the token once it was expired. In the current design, however, the auth token is used to complete the setup flow as soon as it is successfully obtained so there is no case in which a user would have time to let their token expire. Bug: 890958 Change-Id: Ia82af98ebaeeed0429c2da114d6e667130100c99 Reviewed-on: https://chromium-review.googlesource.com/c/1260215Reviewed-by:Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Jordy Greenblatt <jordynass@chromium.org> Cr-Commit-Position: refs/heads/master@{#596491}
Showing
Please register or sign in to comment