GitLab

TBR=ellyjones@chromium.org,liaoyuke@chromium.org

Bug: 828031
Change-Id: I1df91e8a002d3bbb6852d5fa40cbf4b8cae2680a
Reviewed-on: https://chromium-review.googlesource.com/1028669Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553730}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/96706998..69a2f03a

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I66f0dc50ffeb7e5de1c5bec3c928740115afc81c
Reviewed-on: https://chromium-review.googlesource.com/1028184Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553729}

This was introduced in the following patch as a typo:
https://codereview.chromium.org/1927803002/diff/320001/components/arc/bluetooth/arc_bluetooth_bridge.cc

BUG=727843
TEST=Run CtsVerifier and confirm that non-bonded devices don't show up as paired

Change-Id: Id50a5564257a270b62bc78c63835e194af772cce
Reviewed-on: https://chromium-review.googlesource.com/1028574Reviewed-by: Rahul Chaturvedi <rkc@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Commit-Queue: Qiyu Hu <qiyuh@google.com>
Cr-Commit-Position: refs/heads/master@{#553728}

WebViewTests and WebViewInteractiveTests now only run for the
GuestViewCrossProcessFrames enabled case.

Bug: 533069, 544782, 627962, 796344, 807116, 818161, 818205, 829846
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ic3a971b553fe343466a440ed4363389cd9e89214
Reviewed-on: https://chromium-review.googlesource.com/1000137
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553727}

The FileReaders themselves will abort once they realize the context is
destroyed anyway, so it is pretty pointless (and potentially
problematic) to start new FileReaders after the context is destroyed.

Bug: 836724
Change-Id: I7bcbdf7d7905448df794df423a3fb0fe1697dd95
Reviewed-on: https://chromium-review.googlesource.com/1028555
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553726}

This new UMA will replace
DataReductionProxy.SavingsCleared.NegativeSystemClock and add on more
enum values for all the possible reasons the data savings could have
been cleared. This will be done in a follow up CL.

Bug: 812922
Change-Id: Ibc82d187045444b6ca7812e2fc2097549501c0aa
Reviewed-on: https://chromium-review.googlesource.com/1024880
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553725}

The LSI allocators previously did not store a copy of the last generated
LSI. As a result, many call sites would have to keep their own copies.

Now that the LSI allocators have their own copies, the call sites can be
updated to no longer store a separate copy.

RenderFrameProxy is one such call site.

BUG=759031

Change-Id: Id40e679f2c41876fd7e23aa8f2e70817445be420
Reviewed-on: https://chromium-review.googlesource.com/1024747
Commit-Queue: Chris Blume <cblume@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553724}

Currently, we reset the media ID associated with Picture-in-Picture
when OnMediaDestroyed is called, which includes when the video stops
playing. This causes crashes when we attempt to control the video from
the Picture-in-Picture window, such as play/pause and close.

This also means that even if we leave Picture-in-Picture mode, the
video media player will still show the Picture-in-Picture interstitial
because the WebMediaPlayer isn't updated with the fact we've left
Picture-in-Picture mode.

It is okay to keep the id around; when another video is PiP'd, the ID
will be updated.

BUG: 726619
Change-Id: I0e665047b85f20bc7bb9795273a5640460e7612f
Reviewed-on: https://chromium-review.googlesource.com/1026974Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: apacible <apacible@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553723}

The exclusion space already didn't use it, but rather returned a pure
LayoutUnit set to LayoutUnit::Min() if there was no clearance to apply.
Do this everywhere, instead of using Optional<LayoutUnit> some places.

Better have one way of saying "no clearance", than two
(Optional<LayoutUnit> not set OR Optional<LayoutUnit> set to

LayoutUnit: :Min()).
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I3a858397c28ca83ba96ae4d749f97dfa5e7b0cb3
Reviewed-on: https://chromium-review.googlesource.com/1027810Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553722}

Ozone demo is intended to be the simplest possible program that uses the
ozone API to create a window and render to it. Porters use this to see if
their platform implements the API correctly without having to build or
run the entire browser.

Ozone demo recently started using skia infrastructure for rendering via
GL. However, this arguably makes the demo less useful to porters because
it is additional complexity that is not relevant to implementing the
platform window or rendering surface.

This splits the skia demo into a new executable and brings back the
"simple" renderer that just clears the screen to a solid color.

Bug: none
Test: ozone_demo, skia_demo
Change-Id: I8570d43949d68dcf87175c53057c7c72cf45ea6e
Reviewed-on: https://chromium-review.googlesource.com/1028579Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553721}

R=amineer@chromium.org

Change-Id: Ib73b7a656694a80810402b4a3e8f078448e54e9f
Reviewed-on: https://chromium-review.googlesource.com/1028723Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553720}

BUG=773295

Change-Id: Ia199631a83a21b3210baa7741f6591875075a3b5
Reviewed-on: https://chromium-review.googlesource.com/1024992
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553719}

There was an outstanding TODO to validate that during Apply the writes
to the |new_image| and copies from the |old_image| were within valid
ranges. During raw apply fuzzing a number of memory violations occurred
this is a fix for those.

Bug: 835341
Change-Id: I669304e93e51ba7cd2b862189fbc0a6f3cea1748
Reviewed-on: https://chromium-review.googlesource.com/1028575
Commit-Queue: Calder Kitagawa <ckitagawa@google.com>
Reviewed-by: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553718}

Eventually these tests should be renamed to not be specific to ResourceDispatcherHost.

Bug: 787614
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I5cd54463f2bf296f58bbea40b0058fa802f35d13
Reviewed-on: https://chromium-review.googlesource.com/1026703
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553717}

The function implementation always returns asynchronously - either via
an delayed task, or  BluetoothLowEnergyConnectionFinder::Find callback,
which is run from InvokeCallbackAsync

BUG=829182

Change-Id: Id85b4b13fba166d10690eb258d034aab75a46b24
Reviewed-on: https://chromium-review.googlesource.com/1022372Reviewed-by: James Hawkins <jhawkins@chromium.org>
Commit-Queue: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553716}

This interface allows interested classes, including
AwBrowserTerminator, ChromeStabilityMetricsProvider,
OutOfMemoryReporter, and DataReductionProxyPingbackClientImpl to
distinguish between child process crashes and kills on Android.
Previously, this was done by either passing a file descriptor to the
child process (AwBrowserTerminator) or by observing whether a crash
dump was successfully produced. This eliminates the need for the extra
descriptor for AwBrowserTerminator, as well as providing a more
accurate signal for classes that relied on checking for a crash dump.

Observers can use this interface in combination with observing child
process exits/disconnects. If an observer sees a child process
disconnect without having observed a crash signal for the child, it
can deduce that the child was killed.

Bug: crashpad:30
Change-Id: I6213d31f30d15b30d2a3987fe95229042371938b
Reviewed-on: https://chromium-review.googlesource.com/1026085
Commit-Queue: Joshua Peraza <jperaza@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553715}

Currently if an Async Trace event was processed by early tracing it is
given the category (EarlyJava) and if the finish of that same event
happened after native has loaded and regular tracing has started then it
is given a different category (Java).

This CL fixes this bug by keeping track of all async events started
during early tracing and making sure the finish event is also sent from
early tracing.

Bug: 822816
Change-Id: Idaec00c243b9b77195b91e8409e99076be158853
Reviewed-on: https://chromium-review.googlesource.com/1024911
Commit-Queue: Mohamed Heikal <mheikal@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553714}

Test ChromeLoggingCapabilityTest.testPerformanceLogger is not flaky anymore on Android build.
Enabling test execution on Waterfall for Android builds.

Bug: chromedriver:2108
Change-Id: Iee167f37a195385ab5e65fb20261256cd28801fe
Reviewed-on: https://chromium-review.googlesource.com/1028618Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553713}

The ChromeOS debugging instructions include a HTTP link that should be
using HTTPS instead.

TBR=jcivelli@chromium.org

Change-Id: I678027a32b9de592c4d37849c546de265e3e7d48
Reviewed-on: https://chromium-review.googlesource.com/1028659Reviewed-by: Eric Lawrence <elawrence@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Commit-Queue: Eric Lawrence <elawrence@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553712}

These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.

Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.

The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).

As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.

Possible script screw ups / things to look out for in this review:
 - Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
   one (I will go over that in a separate pass).

Includes should have been stripped if that was the last usage of message_loop.h
in that file.

Please CQ if LGTY

This CL was uploaded by git cl split.

TBR=msw@chromium.org

Bug: 825327
Change-Id: I508ddefd5a91415253e907811a17b7d11c818a12
Reviewed-on: https://chromium-review.googlesource.com/1024712Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553711}

These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.

Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.

The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).

As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.

Possible script screw ups / things to look out for in this review:
 - Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
   one (I will go over that in a separate pass).

Includes should have been stripped if that was the last usage of message_loop.h
in that file.

Please CQ if LGTY

This CL was uploaded by git cl split.

TBR=kinuko@chromium.org

Bug: 825327
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ie66f2b93d069fae255bd65750a27e2aeef819ffd
Reviewed-on: https://chromium-review.googlesource.com/1024652Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553710}

Bug: 714018
Test: CQ & run chrome on eve

Change-Id: I7f6bb7a0165d99fb1890cdaa4e893f1fbb28ff51
Reviewed-on: https://chromium-review.googlesource.com/1026417
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553709}

TBR=perezju@chromium.org
NOTRY=true

Bug: 836447
Change-Id: I8058c3f219831333b7539e5d015d825cf53620e8
Reviewed-on: https://chromium-review.googlesource.com/1028715Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#553708}

This refactor CL allows useful GPU service flags like
--enable-gpu-service-logging (log all GL commands processed) and
--enable-gpu-debugging (check for GL error after every command) to be
used when running unittests (e.g. cc_unittests) that use
InProcessCommandBuffer.

There are no security implications of this change because

- only tests use the codepath updated here (Viz and android webview do
  not)

- flags are whitelist passed to child processes (renderer/GPU processes)

ParseGpuPreferences could not easily be added as a member of
GpuPreferences because of dependencies.

  - ParseGpuPreferences depends on gpu/command_buffer/service:gles2 to
    check if passthrough decoder is enabled.

  - gpu/command_buffer/service:gles2 has a dependency on
    gpu/command_buffer/service:service

  - GpuPreferences lives in gpu/command_buffer/service:service

  - Moving GpuPreferences to gpu/command_buffer/service:gles2 seems
    non-trivial. I did not want to introduce a new component just for
    GpuPreferences.

ParseGpuPreferences did not seem to belong to gpu_preferences_util.h
because that is IPC specific.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I76db4fe0eebd3eb7720fa24265f69093715c6137
Reviewed-on: https://chromium-review.googlesource.com/1019662Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Jonathan Backer <backer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553707}

This implements SetColorSpaceMetadata for
Raster{Implementation,Decoder}. Mostly copy paste from
GLES2{Implementation,Decoder}. Other changes:

- parameterize raster_in_process_context_tests.cc to test
  both RasterDecoder and GLES2Decoder

- added a new
  RasterInProcessCommandBufferTest.SetColorSpaceMetadata to
  cover the new RasterDecoder codepath and the prior
  GLES2Decoder path

Bug: 789238
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I437955dfc0821866e251aa15efa2adbfbb9ad8ed
Reviewed-on: https://chromium-review.googlesource.com/1024607Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Jonathan Backer <backer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553706}

Bug: None
Change-Id: I4b88978f8088cc65be94955c0e037fbb580e08ae
Reviewed-on: https://chromium-review.googlesource.com/1028455Reviewed-by: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553705}

Android Nexus 7v2 Perf
Android Nexus6 Perf
Win 8 Perf
Win 7 ATI GPU Perf
Win 7 x64 Perf

Bug: 836798
Change-Id: I072b4ed9b0cc49ac6179cb49dcab067bb2dc2f79
Reviewed-on: https://chromium-review.googlesource.com/1027995Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#553704}

Writer for Priority List. Write a base::Value() in a string with PLIST
format. The decisions were all as pretty print format and kept only the
types that we need for policies. The implemented types are Boolean,
string, integer, list and dictionary.

Bug: 
Change-Id: If43041a2e5dd2e97014a266f35b176019fffb2ff
Reviewed-on: https://chromium-review.googlesource.com/986912
Commit-Queue: Martin Rodriguez <rodmartin@google.com>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Georges Khalil <georgesak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553703}

This CL stubs in an AssistantBubble/AssistantContainerView as part of a
series of CLs to move the AssistantBubbleView out of the app_list.

With this CL:
- Bubble will be shown on interaction start.
- Bubble will be auto-dismissed after interaction finish (w/ delay).

See bug for demo.

Bug: b:77637813
Change-Id: I69c146f386405e33d3a0a503f9bf87072d704abe
Reviewed-on: https://chromium-review.googlesource.com/1024804
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553702}

Bug: 733662
Change-Id: I3db2d80a9a8edab1609b12deac96f320a9630273
Reviewed-on: https://chromium-review.googlesource.com/1026848Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jiaquan He <hejq@google.com>
Cr-Commit-Position: refs/heads/master@{#553701}

Bug: 835867, 575305
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I03bd2083fc5df341ce0d4717d0c5af3abe822763
Tbr: kbr@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1028224Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553700}

Replacing it with modern RunLoop+QuitClosure usage.

R=caseq@chromium.org

Bug: 825327
Change-Id: I43e021d3a3c5e76923e77c8d28560931dc3ee866
Reviewed-on: https://chromium-review.googlesource.com/1024445Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553699}

mDelayedInitialTabBehaviorDuringUiInit is a private runnable that is
never set. It looks like it is added here
(https://codereview.chromium.org/2912473003).

Change-Id: Ic612e95340616ab905d594a25471daea62e6fac1
Reviewed-on: https://chromium-review.googlesource.com/1026422Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Mohamed Heikal <mheikal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553698}

This brings things back in sync after a failed branching.

TBR=govind@google.com
NOTRY=true

Bug: 825063
Change-Id: Id141a41135fab3b5b4736746d5b790659a254bf5
Reviewed-on: https://chromium-review.googlesource.com/1028665
Commit-Queue: Michael Moss <mmoss@chromium.org>
Reviewed-by: Michael Moss <mmoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553697}

This reverts commit f09f52a1.

Reason for revert: yet another friendly lesson on the dangers of notry.

Original change's description:
> Add mac_window_server_killers to browser_tests data on Mac.
> 
> TBR=ellyjones@chromium.org,liaoyuke@chromium.org
> 
> Bug: 828031
> Change-Id: Ie98ee83cee2d4c98c29a2ac1290728da5b87c4a7
> No-Try: True
> Reviewed-on: https://chromium-review.googlesource.com/1028482
> Reviewed-by: John Budorick <jbudorick@chromium.org>
> Commit-Queue: John Budorick <jbudorick@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#553626}

TBR=ellyjones@chromium.org,liaoyuke@chromium.org,jbudorick@chromium.org

Change-Id: Ida00d9ae602b301008a0bdaab46255c2361c6107
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 828031
Reviewed-on: https://chromium-review.googlesource.com/1028491Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553696}

This adds Network.takeResponseBodyForInterceptionAsStream, which returns
a stream handle that can be used with IO.read/IO.close.
Note this is only supported with the Network Service currently, the
legacy URLRequestJob based interception support will be added later.

Bug: 831887
Change-Id: Ibc5a43e86824f0c86397f200b5a6852171705f0e
Reviewed-on: https://chromium-review.googlesource.com/1026692Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553695}

Bug: 836187
Change-Id: Id072e00ca0d6e4f278a43f34deea6880d2aa0536
Reviewed-on: https://chromium-review.googlesource.com/1026039Reviewed-by: Timothy Loh <timloh@chromium.org>
Reviewed-by: Jenny Zhang <jennyz@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553694}

This class can be useful for any classes to implement/support multiple
versins of library CDM interface. Hence, move it out of clear_key_cdm
folder. In a later CL, I'll use them for a mock library CDM
implementation.

Bug: 836046
Test: No functionality change.
Change-Id: I7567e405de0251ddce3718eb76d102f07ff8f33e
Reviewed-on: https://chromium-review.googlesource.com/1026970Reviewed-by: John Rummell <jrummell@chromium.org>
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553693}

https://pdfium.googlesource.com/pdfium.git/+log/ac19439e28b6..d9da586dd3db

$ git log ac19439e2..d9da586dd --date=short --no-merges --format='%ad %ae %s'
2018-04-25 npm Roll third_party/freetype/src/ 26ad1acbc..2157d8fa6 (21 commits)

Created with:
  roll-dep src/third_party/pdfium


The AutoRoll server is located here: https://pdfium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=dsinclair@chromium.org

Change-Id: I22f771416c8dde47fd823191cb2b196499d9dfdd
Reviewed-on: https://chromium-review.googlesource.com/1028475
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#553692}

R=cmasso@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Icd4046545efb94a6a54de3a5452ac085fee311fa
Reviewed-on: https://chromium-review.googlesource.com/1028657Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553691}