Update shelf spacing in Chrome OS according to the MD specs

chrome/test/base/view_event_test_platform_part_chromeos.cc

Index: chrome/test/base/view_event_test_platform_part_chromeos.cc
diff --git a/chrome/test/base/view_event_test_platform_part_chromeos.cc b/chrome/test/base/view_event_test_platform_part_chromeos.cc
index 399595defe39f98d4c09b5fdf932e04ecd794089..a39bad9a97a5ee9359c29e2225bb04312c10c049 100644
--- a/chrome/test/base/view_event_test_platform_part_chromeos.cc
+++ b/chrome/test/base/view_event_test_platform_part_chromeos.cc
@@ -7,6 +7,7 @@
 #include <memory>
 
 #include "ash/ash_switches.h"
+#include "ash/material_design/material_design_controller.h"
 #include "ash/shell.h"
 #include "ash/shell_init_params.h"
 #include "ash/test/ash_test_helper.h"
@@ -57,6 +58,7 @@ ViewEventTestPlatformPartChromeOS::ViewEventTestPlatformPartChromeOS(
           chromeos::DBusClientBundle::BLUETOOTH));
   chromeos::CrasAudioHandler::InitializeForTesting();
   chromeos::NetworkHandler::Initialize();
+  ash::MaterialDesignController::Initialize();

[bruthig, 2016/05/25 20:24:53]

This test fixture should clean up after itself by calling
MaterialDesignControllerTestAPI::Uninitialize() from the destructor.

[yiyix, 2016/06/02 03:54:54]

The Uninitialize() function simply set the mode to uninitialized. It does not
free any memory. It is unnecessary to call
MaterialDesignControllerTestAPI::Uninitialize(). The memory will be freed after
the test case finished.  

 
   env_ = aura::Env::CreateInstance();
   ash::test::TestShellDelegate* shell_delegate =