Allow backgrounding processes on Mac

content/browser/renderer_host/render_process_host_impl.cc

Index: content/browser/renderer_host/render_process_host_impl.cc
diff --git a/content/browser/renderer_host/render_process_host_impl.cc b/content/browser/renderer_host/render_process_host_impl.cc
index 8646cc48d900ccecd4baf34320e918edc44c6857..13daab69b11b8f5b49861e381f51586a495789c9 100644
--- a/content/browser/renderer_host/render_process_host_impl.cc
+++ b/content/browser/renderer_host/render_process_host_impl.cc
@@ -2805,14 +2805,20 @@ void RenderProcessHostImpl::OnProcessLaunched() {
     // Not all platforms launch processes in the same backgrounded state. Make
     // sure |is_process_backgrounded_| reflects this platform's initial process
     // state.
+#if defined(OS_MACOSX)
+    is_process_backgrounded_ =
+        child_process_launcher_->GetProcess().IsProcessBackgrounded(
+            MachBroker::GetInstance());
+#else
     is_process_backgrounded_ =
         child_process_launcher_->GetProcess().IsProcessBackgrounded();
+#endif  // defined(OS_MACOSX)
 
-    // Disable updating process priority on startup for now as it incorrectly
-    // results in backgrounding foreground navigations until their first commit
-    // is made. A better long term solution would be to be aware of the tab's
-    // visibility at this point. https://crbug.com/560446.
-    // Except on Android for now because of https://crbug.com/601184 :-(.
+// Disable updating process priority on startup for now as it incorrectly

[shrike, 2016/10/31 17:26:05]

It seems like this comment should stay at its current indentation level?

[lgrey, 2016/10/31 19:22:02]

This was from git cl format. Is it OK to override it?

[shrike, 2016/10/31 20:32:36]

As long as your change follows the spec it should be OK to change what git cl
format does. That said, this formatting should be based on the brace nesting
level, so it would be surprising for it to be wrong. I applied your patch and
the formatting looks correct - I don't know what's going on but it seems like
leaving as is should be OK.

[Nico, 2016/11/01 02:07:27]

`git cl format` aligns comments in front of a preprocessor directive with the
alignment of the following preprocessor directive (or the prior one, don't
remember right now). If you don't want this, move the comment after the
preprocessor directive.

+// results in backgrounding foreground navigations until their first commit
+// is made. A better long term solution would be to be aware of the tab's
+// visibility at this point. https://crbug.com/560446.
+// Except on Android for now because of https://crbug.com/601184 :-(.
 #if defined(OS_ANDROID)
     UpdateProcessPriority();
 #endif