Enabled Selection (ctrl-A) on login password

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

Index: chrome/browser/resources/chromeos/login/login.js
diff --git a/chrome/browser/resources/chromeos/login/login.js b/chrome/browser/resources/chromeos/login/login.js
index 5e46fbe4343447185806d39d3ffb25047bb4958e..b6096e05c070f4a0ead3de753a1a9a00e51bbdfa 100644
--- a/chrome/browser/resources/chromeos/login/login.js
+++ b/chrome/browser/resources/chromeos/login/login.js
@@ -179,6 +179,10 @@ cr.define('cr.ui', function() {
 
 var Oobe = cr.ui.Oobe;
 
-disableTextSelectAndDrag();
+// Allow selection events specifically on InputElements (password field)
+// bug (http://code.google.com/p/chromium/issues/detail?id=125863)
+disableTextSelectAndDrag(function(e) {
+    return e.target instanceof HTMLInputElement;

[Dan Beam, 2012/07/24 23:07:49]

Copy pasta detected, remove two spaces from this line and below in each file.
Also, do you only care about password or text inputs? If so, you should probably
check e.target.type is 'password' or 'text' or 'search' or has no type or
something...

[Harry McCleave, 2012/07/24 23:21:15]

The behavior identified in the bug was on a password field however any text
input field would be unintuitive without this change (page identified only has
password field) so I think not limiting the type is correct.

[Dan Beam, 2012/07/25 00:04:59]

You may want to allow <textarea>s as well then, perhaps something like:

  var src = e.target;
  return src instanceof HTMLTextAreaElement ||
         src instanceof HTMLInputElement &&
         /text|password|search/.test(src.type);

+  });
 
 document.addEventListener('DOMContentLoaded', cr.ui.Oobe.initialize);