Accessibility fixes for quick unlock settings.

chrome/browser/resources/settings/people_page/password_prompt_dialog.js

Index: chrome/browser/resources/settings/people_page/password_prompt_dialog.js
diff --git a/chrome/browser/resources/settings/people_page/password_prompt_dialog.js b/chrome/browser/resources/settings/people_page/password_prompt_dialog.js
index 7dae95142d97ae14d155c4d897468b608f94a32a..e7c23575511f4dda5ebc0877ebc8f8ef8931cb6d 100644
--- a/chrome/browser/resources/settings/people_page/password_prompt_dialog.js
+++ b/chrome/browser/resources/settings/people_page/password_prompt_dialog.js
@@ -81,6 +81,17 @@ Polymer({
     },
   },
 
+  /** @override */
+  ready: function() {
+    // The first time the dialog is shown, the password prompt does not
+    // auto-focus itself. However, if the dialog has been created already
+    // and is only being redisplayed, the password input will correctly
+    // capture focus by itself.
+    setTimeout(function() {
+      this.$.passwordInput.focus();

[tommycli, 2016/10/25 18:13:50]

Two questions:

1. Why doesn't autofocus attribute work the first time?

2. I see that you removed the autofocus attribute. Doesn't that conflict with
the comment above?

[jdufault, 2016/10/26 22:38:36]

I believe autofocus does not work because the content is in a dialog.

The focus behavior is very weird - for example, moving the setTimeout call to
the open method will cause document to get focused instead of passwordInput, but
only after the dialog has been displayed once before.

+    }.bind(this));
+  },
+
   /**
    * Open up the dialog. This will wait until the dialog has loaded before
    * opening it.