[Android History] Add Android history manager UI and bridge

[Android History] Add Android history manager UI and bridge

Adds the basic scaffolding for the Android history manager UI:

 * Creates a JNI BrowsingHistoryBridge that serves as a conduit
   between the native BrowsingHistoryService and Java UI.
 * Creates a new Android-specific history manager UI hidden
   behind a command line flag.
 * Displays history items in history manager UI.

BUG=654071
Committed: https://crrev.com/87cc36611529a2271b09989491561b3a631ef8cd
Cr-Commit-Position: refs/heads/master@{#436648}

[Theresa, 2016-12-01 19:27:51]

The CQ bit was checked by twellington@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-01 19:28:29]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Theresa, 2016-12-01 19:30:10]

twellington@chromium.org changed reviewers:
+ dfalcantara@chromium.org

[Theresa, 2016-12-01 19:30:11]

ptal - apologies in advance for the large CL. Let me know if you see a good way
to split to it up (I tried to keep the functionality added in this CL as limited
as possible). It's not as bad as it look (there are many small files rather than
a few large ones).

[gone, 2016-12-02 19:34:37]

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/res...
File chrome/android/java/res/layout/history_item_view.xml (right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/res...
chrome/android/java/res/layout/history_item_view.xml:7: <view
class="org.chromium.chrome.browser.history.HistoryItemView"
Could you just use the class instead of the "view class" bit?  I think that's
only required for inner classes.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/res...
File chrome/android/java/res/layout/history_toolbar.xml (right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/res...
chrome/android/java/res/layout/history_toolbar.xml:10: <include
layout="@layout/number_roll_view" />
nit: newlines above and below <include>?  alternatively indent new tags by 4 and
attributes by 8 so we can see how things break apart more easily?

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/BrowsingHistoryBridge.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/BrowsingHistoryBridge.java:14:
/** The JNI bridge for Android to fetch and manipulate browsing history. **/
Single asterisk to close

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/BrowsingHistoryBridge.java:42:
List<HistoryItem> historyItems = new ArrayList<>();
Is this needed just to make the call?  Doesn't seem it's used anywhere, yet.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryAdapter.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryAdapter.java:26:
private SelectionDelegate<HistoryItem> mSelectionDelegate;
finals?

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryAdapter.java:49:
loadItems(result);
What happens if this class (or the bridge) is destroyed before onResult is
called?  Do you need to track a destroyed state?

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryItem.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryItem.java:13:
private String mUrl;
Can any of these things be final?

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManager.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManager.java:26:
private SelectionDelegate<HistoryItem> mSelectionDelegate;
finals?

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManager.java:35:
mSelectionDelegate = new SelectionDelegate<HistoryItem>();
new SelectionDelegate<>();

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManagerUtils.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManagerUtils.java:26:
public static boolean isAndroidHistoryManagerEnabled() {
Does this need to worry about what thread it's called on (i.e. do we need to
synchronize on something)?

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
File chrome/browser/android/history/browsing_history_bridge.cc (right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.cc:30:
BrowsingHistoryBridge::~BrowsingHistoryBridge() {}
Do you need to destroy the browsing_history_service_?  If you do, would it make
sense to just have a scoped ptr?

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.cc:41: int64_t
j_query_end_time) {
nit: remove newline?

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.cc:57:
BrowsingHistoryService::QueryResultsInfo* query_results_info) {
Given the asyncedness, do you need to check if the native or java parts have
been destroyed before proceeding?

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.cc:58: for
(std::vector<BrowsingHistoryService::HistoryEntry>::iterator it =
Is this something you could use "auto" for?

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
File chrome/browser/android/history/browsing_history_bridge.h (right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.h:51: JNIEnv* env_;
Should just call AttachCurrentThread() instead of storing the env_.

[Theresa, 2016-12-02 20:47:07]

The CQ bit was checked by twellington@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-02 20:47:56]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Theresa, 2016-12-02 20:49:31]

twellington@chromium.org changed reviewers:
+ miu@chromium.org, sky@chromium.org

[Theresa, 2016-12-02 20:49:33]

+miu@ - ptal at time.* changes (added a FromJavaTime method)
+sky@ - ptal at browsing_history_service_handler.h change (made destructor
virtual)

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/res...
File chrome/android/java/res/layout/history_item_view.xml (right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/res...
chrome/android/java/res/layout/history_item_view.xml:7: <view
class="org.chromium.chrome.browser.history.HistoryItemView"
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Could you just use the class instead of the "view class" bit?  I think that's
> only required for inner classes.

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/res...
File chrome/android/java/res/layout/history_toolbar.xml (right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/res...
chrome/android/java/res/layout/history_toolbar.xml:10: <include
layout="@layout/number_roll_view" />
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> nit: newlines above and below <include>?  alternatively indent new tags by 4
and
> attributes by 8 so we can see how things break apart more easily?

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/BrowsingHistoryBridge.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/BrowsingHistoryBridge.java:14:
/** The JNI bridge for Android to fetch and manipulate browsing history. **/
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Single asterisk to close

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/BrowsingHistoryBridge.java:42:
List<HistoryItem> historyItems = new ArrayList<>();
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Is this needed just to make the call?  Doesn't seem it's used anywhere, yet.

This is the list that gets passed back to the callback in onQueryHistoryComplete
below. I moved the ArrayList creation inline in the call to nativeQueryHistory.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryAdapter.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryAdapter.java:26:
private SelectionDelegate<HistoryItem> mSelectionDelegate;
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> finals?

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryAdapter.java:49:
loadItems(result);
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> What happens if this class (or the bridge) is destroyed before onResult is
> called?  Do you need to track a destroyed state?

I don't think it's technically possible (see comments in
browsing_history_Bridge.cc), but there's no harm in adding a check. I added
boolean tracking destroyed state.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryItem.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryItem.java:13:
private String mUrl;
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Can any of these things be final?

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManager.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManager.java:26:
private SelectionDelegate<HistoryItem> mSelectionDelegate;
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> finals?

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManager.java:35:
mSelectionDelegate = new SelectionDelegate<HistoryItem>();
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> new SelectionDelegate<>();

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManagerUtils.java
(right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManagerUtils.java:26:
public static boolean isAndroidHistoryManagerEnabled() {
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Does this need to worry about what thread it's called on (i.e. do we need to
> synchronize on something)?

It's currently only called from the UI thread but tests may change that. Moved
most of this method into a synchronized block.

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
File chrome/browser/android/history/browsing_history_bridge.cc (right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.cc:30:
BrowsingHistoryBridge::~BrowsingHistoryBridge() {}
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Do you need to destroy the browsing_history_service_?  If you do, would it
make
> sense to just have a scoped ptr?

Done. I made it a unique_ptr<>.

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.cc:41: int64_t
j_query_end_time) {
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> nit: remove newline?

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.cc:57:
BrowsingHistoryService::QueryResultsInfo* query_results_info) {
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Given the asyncedness, do you need to check if the native or java parts have
> been destroyed before proceeding?

I don't think so. The bridge gets destroyed when the Java counterpart gets
destroyed. I changed the BrowsingHistoryService* that this class owns a
std::unique_ptr so the BrowsingHistoryService gets destroyed when this class
gets destroyed.

In BrowsingHistoryService's destructor, all in-flight queries get canceled, so
it won't receive results after it's been destroyed, which means this method
shouldn't be called after BrowsingHistoryBridge's destructor has been called.

Destruction happens on the UI thread and this class and BrowsingHistoryService
do their work on the UI thread so I don't think there's a race condition between
destruction and returning results.

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.cc:58: for
(std::vector<BrowsingHistoryService::HistoryEntry>::iterator it =
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Is this something you could use "auto" for?

Done.

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
File chrome/browser/android/history/browsing_history_bridge.h (right):

https://codereview.chromium.org/2542203002/diff/20001/chrome/browser/android/...
chrome/browser/android/history/browsing_history_bridge.h:51: JNIEnv* env_;
On 2016/12/02 19:34:37, dfalcantara (check my queue) wrote:
> Should just call AttachCurrentThread() instead of storing the env_.

Done.

[gone, 2016-12-02 20:52:29]

https://codereview.chromium.org/2542203002/diff/60001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManagerUtils.java
(right):

https://codereview.chromium.org/2542203002/diff/60001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManagerUtils.java:21:
private static final Object sLock = new Object();
nit: NATIVE_HISTORY_ENABLED_LOCK?

[sky, 2016-12-02 21:24:24]

LGTM

[Theresa, 2016-12-02 21:33:54]

The CQ bit was checked by twellington@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-02 21:34:13]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Theresa, 2016-12-02 21:35:35]

https://codereview.chromium.org/2542203002/diff/60001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManagerUtils.java
(right):

https://codereview.chromium.org/2542203002/diff/60001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/history/HistoryManagerUtils.java:21:
private static final Object sLock = new Object();
On 2016/12/02 20:52:28, dfalcantara (check my queue) wrote:
> nit: NATIVE_HISTORY_ENABLED_LOCK?

Done.

[gone, 2016-12-02 22:52:50]

lgtm

[miu, 2016-12-02 23:33:50]

base/time/* changes lgtm.

[commit-bot: I haz the power, 2016-12-02 23:33:53]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-02 23:33:54]

Dry run: Try jobs failed on following builders:
  android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
  android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...)
  android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)

[Theresa, 2016-12-02 23:35:13]

The CQ bit was checked by twellington@chromium.org

[Theresa, 2016-12-02 23:35:14]

The patchset sent to the CQ was uploaded after l-g-t-m from sky@chromium.org
Link to the patchset: https://codereview.chromium.org/2542203002/#ps80001
(title: "Rename variable")

[commit-bot: I haz the power, 2016-12-02 23:36:03]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-03 01:12:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-03 01:12:30]

Try jobs failed on following builders:
  android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)

[Theresa, 2016-12-05 17:42:57]

The CQ bit was checked by twellington@chromium.org

[commit-bot: I haz the power, 2016-12-05 17:43:29]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-05 19:45:37]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-05 19:45:39]

Try jobs failed on following builders:
  chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Theresa, 2016-12-05 19:57:09]

The CQ bit was checked by twellington@chromium.org

[commit-bot: I haz the power, 2016-12-05 19:58:00]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-06 00:00:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-06 00:00:42]

Try jobs failed on following builders:
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Theresa, 2016-12-06 00:05:15]

The CQ bit was checked by twellington@chromium.org

[commit-bot: I haz the power, 2016-12-06 00:05:40]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Theresa, 2016-12-06 00:16:44]

The CQ bit was unchecked by twellington@chromium.org

[Theresa, 2016-12-06 01:10:33]

The CQ bit was checked by twellington@chromium.org

[commit-bot: I haz the power, 2016-12-06 01:10:58]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-06 02:40:50]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-06 02:40:51]

Failed to apply patch for
chrome/android/java/strings/android_chrome_strings.grd:
While running git apply --index -p1;
  error: patch failed:
chrome/android/java/strings/android_chrome_strings.grd:1784
  error: chrome/android/java/strings/android_chrome_strings.grd: patch does not
apply

Patch:       chrome/android/java/strings/android_chrome_strings.grd
Index: chrome/android/java/strings/android_chrome_strings.grd
diff --git a/chrome/android/java/strings/android_chrome_strings.grd
b/chrome/android/java/strings/android_chrome_strings.grd
index
d4d8c329f9f2f3305fcd9711b6b849ce70dee8c1..f54f5b648810a61716249538c778d6245752c136
100644
--- a/chrome/android/java/strings/android_chrome_strings.grd
+++ b/chrome/android/java/strings/android_chrome_strings.grd
@@ -1784,6 +1784,11 @@ To obtain new licenses, connect to the internet and play
your downloaded content
         Open with...
       </message>
 
+      <!-- Browsing History UI -->
+      <message name="IDS_HISTORY_MANAGER_EMPTY" desc="Indicates that there are
no browsing history items.">
+        No history here
+      </message>
+
       <!-- Document mode messages -->
       <message name="IDS_CLOSE_ALL_INCOGNITO_NOTIFICATION" desc="Message on the
notification that closes all incognito tabs in document mode">
         Close all incognito tabs

[Theresa, 2016-12-06 17:00:06]

The CQ bit was checked by twellington@chromium.org

[Theresa, 2016-12-06 17:00:06]

The patchset sent to the CQ was uploaded after l-g-t-m from sky@chromium.org,
miu@chromium.org, dfalcantara@chromium.org
Link to the patchset: https://codereview.chromium.org/2542203002/#ps100001
(title: "Rebase, drop changes to time.*")

[commit-bot: I haz the power, 2016-12-06 17:00:33]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-06 18:15:09]

CQ is committing da patch.

Bot data: {"patchset_id": 100001, "attempt_start_ts": 1481043606391190,
"parent_rev": "c953d57c5dadb9d1b73740d8a53575e5cff45587", "commit_rev":
"623b747a0415b4f62b66a66eac1078f6f8029c3b"}

[commit-bot: I haz the power, 2016-12-06 18:15:36]

Committed patchset #6 (id:100001)

[commit-bot: I haz the power, 2016-12-06 18:18:05]

Description was changed from

==========
[Android History] Add Android history manager UI and bridge

Adds the basic scaffolding for the Android history manager UI:

 * Creates a JNI BrowsingHistoryBridge that serves as a conduit
   between the native BrowsingHistoryService and Java UI.
 * Creates a new Android-specific history manager UI hidden
   behind a command line flag.
 * Displays history items in history manager UI.

BUG=654071
==========

to

==========
[Android History] Add Android history manager UI and bridge

Adds the basic scaffolding for the Android history manager UI:

 * Creates a JNI BrowsingHistoryBridge that serves as a conduit
   between the native BrowsingHistoryService and Java UI.
 * Creates a new Android-specific history manager UI hidden
   behind a command line flag.
 * Displays history items in history manager UI.

BUG=654071

Committed: https://crrev.com/87cc36611529a2271b09989491561b3a631ef8cd
Cr-Commit-Position: refs/heads/master@{#436648}
==========

[commit-bot: I haz the power, 2016-12-06 18:18:06]

Patchset 6 (id:??) landed as
https://crrev.com/87cc36611529a2271b09989491561b3a631ef8cd
Cr-Commit-Position: refs/heads/master@{#436648}