Send microsecond resolution timestamps to Java history page so they can be sent back.

Send microsecond resolution timestamps to Java history page so they can be sent back.

When an entry on the history page is deleted, we create history
deletion directives that are sent through sync. These are required to
support offline history deletions, and make sure these are properly
propagated. However, these deletion directives rely on exact matches in
timestamps, which are in microseconds since the epoch.

The History page on Android converted microsecond timestamps to
millisecond timestamps for Java compatibility, but when these
timestamps were handed to the logic that created history deletion
directives, they were now slightly off. This change simply plumbs
through microsecond timestamps through the java code and back.

BUG=729020
Review-Url: https://codereview.chromium.org/2935783002
Cr-Original-Commit-Position: refs/heads/master@{#478756}
Review-Url: https://codereview.chromium.org/2953673002 .
Cr-Commit-Position: refs/branch-heads/3112@{#429}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
Committed: https://chromium.googlesource.com/chromium/src/+/ec2a6b24c7b356aa35cbe950a49bf4cd7f1909bb

[skym, 2017-06-21 22:23:38]

Description was changed from

==========
Send microsecond resolution timestamps to Java history page so they can be sent
back.

When an entry on the history page is deleted, we create history
deletion directives that are sent through sync. These are required to
support offline history deletions, and make sure these are properly
propagated. However, these deletion directives rely on exact matches in
timestamps, which are in microseconds since the epoch.

The History page on Android converted microsecond timestamps to
millisecond timestamps for Java compatibility, but when these
timestamps were handed to the logic that created history deletion
directives, they were now slightly off. This change simply plumbs
through microsecond timestamps through the java code and back.

BUG=729020

Review-Url: https://codereview.chromium.org/2935783002
Cr-Commit-Position: refs/heads/master@{#478756}
(cherry picked from commit 209633050f6d05fff54e8dcd2195743858b33125)
==========

to

==========
Send microsecond resolution timestamps to Java history page so they can be sent
back.

When an entry on the history page is deleted, we create history
deletion directives that are sent through sync. These are required to
support offline history deletions, and make sure these are properly
propagated. However, these deletion directives rely on exact matches in
timestamps, which are in microseconds since the epoch.

The History page on Android converted microsecond timestamps to
millisecond timestamps for Java compatibility, but when these
timestamps were handed to the logic that created history deletion
directives, they were now slightly off. This change simply plumbs
through microsecond timestamps through the java code and back.

BUG=729020

Review-Url: https://codereview.chromium.org/2935783002
Cr-Original-Commit-Position: refs/heads/master@{#478756}
Review-Url: https://codereview.chromium.org/2953673002 .
Cr-Commit-Position: refs/branch-heads/3112@{#429}
Cr-Branched-From:
b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
Committed:
https://chromium.googlesource.com/chromium/src/+/ec2a6b24c7b356aa35cbe950a49b...
==========

[skym, 2017-06-21 22:23:44]

Committed patchset #1 (id:1) manually as
ec2a6b24c7b356aa35cbe950a49bf4cd7f1909bb.