Pass SequencedTaskRunner to PowerSaveBlocker for ui/file operations

content/browser/power_save_blocker_factory.cc

Index: content/browser/power_save_blocker_factory.cc
diff --git a/content/browser/power_save_blocker_factory.cc b/content/browser/power_save_blocker_factory.cc
new file mode 100644
index 0000000000000000000000000000000000000000..d9a65554f005e7f230f0dfeb400db47ea101eab2
--- /dev/null
+++ b/content/browser/power_save_blocker_factory.cc
@@ -0,0 +1,21 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "content/public/browser/power_save_blocker_factory.h"
+
+#include "content/public/browser/browser_thread.h"
+
+namespace content {
+
+std::unique_ptr<PowerSaveBlocker> CreatePowerSaveBlocker(
+    PowerSaveBlocker::PowerSaveBlockerType type,
+    PowerSaveBlocker::Reason reason,
+    const std::string& description) {
+  return PowerSaveBlocker::CreateWithTaskRunners(
+      type, reason, description,
+      BrowserThread::GetMessageLoopProxyForThread(BrowserThread::UI),
+      BrowserThread::GetMessageLoopProxyForThread(BrowserThread::FILE));

[hashimoto, 2016/05/24 06:02:42]

How about using BrowserThread::GetBlockingPool()->GetSequencedTaskRunner()
instead of the FILE thread?

The FILE thread was declared dead long ago.
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/OaA-9rnjOqI/H0cDC...

[scottmg, 2016/05/24 17:18:03]

Done.

+}
+
+}  // namespace content