Fixed the look of the pin input.

chrome/browser/resources/chromeos/quick_unlock/pin_keyboard.html

 <!-- TODO(crbug.com/603217): Use i18n instead of string literals. Figure out
                              what i18n to use for keypad, ie, does 1 ABC make
                              sense in every scenario? -->
 
 <link rel="import" href="chrome://resources/html/i18n_behavior.html">
 <link rel="import" href="chrome://resources/polymer/v1_0/paper-button/paper-button.html">
 <link rel="import" href="chrome://resources/polymer/v1_0/paper-icon-button/paper-icon-button.html">
 <link rel="import" href="chrome://resources/polymer/v1_0/paper-styles/paper-styles.html">
 <link rel="import" href="chrome://resources/polymer/v1_0/iron-icons/iron-icons.html">
 
@@ skipping 86 matching lines @@
       .first-row {
         height: 64px;
         min-height: 64px;
         padding: 28px 15px 12px 15px;
       }
 
       #pin-input {
         -webkit-text-security: disc;
         background-color: white;
         border: 0;
+        box-sizing: border-box;
         font-size: 18px;
         height: 64px;
         left: 20px;
+        outline: 0;
         padding: 28px 3px 12px 3px;
         position: relative;
         width: 180px;
       }
 
       #pin-input[type=number]::-webkit-inner-spin-button,
       #pin-input[type=number]::-webkit-outer-spin-button {
         -webkit-appearance: none;
         margin: 0;
       }
@@ skipping 70 matching lines @@
             <inner-text class="icon-subheading">
               $i18n{pinKeyboardClear}
             </inner-text>
           </paper-button>
         </div>
       </div>
     </div>
   </template>
   <script src="pin_keyboard.js"></script>
 </dom-module>