Remove java ViewAndroid class

content/public/android/java/src/org/chromium/content/browser/PowerSaveBlocker.java

Index: content/public/android/java/src/org/chromium/content/browser/PowerSaveBlocker.java
diff --git a/content/public/android/java/src/org/chromium/content/browser/PowerSaveBlocker.java b/content/public/android/java/src/org/chromium/content/browser/PowerSaveBlocker.java
deleted file mode 100644
index 3c561c3c49030d3a1b1d39fd8e754ecf5791318e..0000000000000000000000000000000000000000
--- a/content/public/android/java/src/org/chromium/content/browser/PowerSaveBlocker.java
+++ /dev/null
@@ -1,20 +0,0 @@
-// Copyright 2013 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.
-
-package org.chromium.content.browser;
-
-import org.chromium.base.CalledByNative;
-import org.chromium.ui.base.ViewAndroid;
-
-class PowerSaveBlocker {
-    @CalledByNative
-    private static void applyBlock(ViewAndroid view) {

[Ted C, 2015/04/06 20:56:11]

I honestly would prefer this class remain and all the logic in CVC could live in
here (making this a 1:1 relationship with the native delegate).

[boliu, 2015/04/06 21:04:06]

Sounds fine. Will do.

[boliu, 2015/04/06 22:47:00]

Oh, now I remember why I didn't do this..

Current implementation keeps a per-ViewAndroid KeepScreenOn count. So 1:1 with
native PowerSaveBlocker is wrong, and a global count is not correct either.

[boliu, 2015/04/06 22:50:20]

Could totally do one anchor view per PowerSaveBlocker (instead the current
behavior of one anchor view per ViewAndroid, and then keep a count). WDYT?

-        view.incrementKeepScreenOnCount();
-    }
-
-    @CalledByNative
-    private static void removeBlock(ViewAndroid view) {
-        view.decrementKeepScreenOnCount();
-    }
-}