Pin keyboard moved to under the user profile.

chrome/browser/resources/chromeos/login/lock.js

Index: chrome/browser/resources/chromeos/login/lock.js
diff --git a/chrome/browser/resources/chromeos/login/lock.js b/chrome/browser/resources/chromeos/login/lock.js
index 51e856d1e99e996b1ecfd4abb14500a99d22bd57..5a57106414d36652f0ceb1a4c554e65877920c93 100644
--- a/chrome/browser/resources/chromeos/login/lock.js
+++ b/chrome/browser/resources/chromeos/login/lock.js
@@ -8,8 +8,10 @@
 
 <include src="login_shared.js">
 
-// Asynchronously loads the pin keyboard.
-function showPinKeyboardAsync() {
+/**
+ * Asynchronously loads the pin keyboard.
+ */
+function loadPinKeyboardAsync() {
   'use strict';
 
   // This function could get called multiple times. Do nothing if we have
@@ -25,8 +27,9 @@ function showPinKeyboardAsync() {
   });
 
   // Called after polymer has been loaded. Fades the pin element in.
-  var onPinLoaded = function(pinContainer) {
-    pinContainer.style.opacity = 1;
+  var onPinLoaded = function() {
+    var podrow = $('pod-row');

[jdufault, 2016/06/23 00:02:31]

nit: podRow

[sammiequon, 2016/06/23 19:23:21]

Done.

+    podrow.setFocusedPodPinVisibility(true);

[jdufault, 2016/06/23 00:02:31]

What's the plan for this callback? Right now it is always displaying the
keyboard, which means showPinkeyboardAsync is a better name.

If the plan is to invoke another callback like we discussed offline, then that
seems fine to me, but add a TODO please.

[sammiequon, 2016/06/23 19:23:21]

Done.

   };
 
   // We only load the PIN element when it is actually shown so that lock screen