Fix avatar image size in user pods on desktop

chrome/browser/resources/user_manager/user_manager.css

Index: chrome/browser/resources/user_manager/user_manager.css
diff --git a/chrome/browser/resources/user_manager/user_manager.css b/chrome/browser/resources/user_manager/user_manager.css
index 53062e349347018a464bc09c142c5ee313cb5a4d..c7060deac0e4f2643a9820afa2dff9f25a599da1 100644
--- a/chrome/browser/resources/user_manager/user_manager.css
+++ b/chrome/browser/resources/user_manager/user_manager.css
@@ -58,8 +58,10 @@ html[dir=rtl] .user-image-pane {
 }
 
 .pod .user-image {
-  max-height: 180px;
-  max-width: 180px;
+  height: 180px;
+  max-height: initial;
+  max-width: initial;

[Evan Stade, 2014/07/16 23:26:24]

is there some other rule setting this somewhere? why can't you just leave it
off?

[bartfab (slow), 2014/07/16 23:53:57]

It's inherited from the CSS for Chrome OS pods, which the desktop pods are based
on:

https://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/resources/log...
(lines 86-87)

[Evan Stade, 2014/07/17 01:00:08]

I think it's a little dangerous to include css from ../login because it's not an
obviously shared location. What happens when someone makes a change to chromeos
login and it has an unexpected affect on the user manager?

I'd rather the shared CSS be moved to an obviously shared location, and the
max-height/max-width stuff in user_pod_row.css kept in an unshared css file.

+  width: 180px

[Evan Stade, 2014/07/16 23:26:24]

;

[bartfab (slow), 2014/07/21 18:27:44]

Done.

   opacity: 1;
 }