Mac: Make content shell work with remote CoreAnimation

chrome/browser/chrome_browser_main_mac.mm

Index: chrome/browser/chrome_browser_main_mac.mm
diff --git a/chrome/browser/chrome_browser_main_mac.mm b/chrome/browser/chrome_browser_main_mac.mm
index f016458e62a7e009efa8f26cdf6cbfe99e3a61bc..c097c49e4271d44132a9336d5f5202763231de42 100644
--- a/chrome/browser/chrome_browser_main_mac.mm
+++ b/chrome/browser/chrome_browser_main_mac.mm
@@ -156,13 +156,7 @@ void ChromeBrowserMainPartsMac::PreMainMessageLoopStart() {
       // |-application:openFiles:|, since we already handle them directly.
       // @"NO" looks like a mistake, but the value really is supposed to be a
       // string.
-      @"NSTreatUnknownArgumentsAsOpen": @"NO",
-      // CoreAnimation has poor performance and CoreAnimation and
-      // non-CoreAnimation exhibit window flickering when layers are not hosted
-      // in the window server, which is the default when not not using the
-      // 10.9 SDK.
-      // TODO: Remove this when we build with the 10.9 SDK.
-      @"NSWindowHostsLayersInWindowServer": @(base::mac::IsOSMavericksOrLater())
+      @"NSTreatUnknownArgumentsAsOpen": @"NO"
   }];
 }