GitLab

The ControllerDelegate was renamed to InputDelegate to reflect
that it handles more than just the controller raw input.

Bug: 875291
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I7415806cf7ba52a7e49899843dcf93079333c8d3
Reviewed-on: https://chromium-review.googlesource.com/1213874
Commit-Queue: Aldo Culquicondor <acondor@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590522}

Based on https://codereview.chromium.org/2897463003/.

Test: Run update.py --force-local-build, remove https://cs.chromium.org/chromium/src/build/config/fuchsia/BUILD.gn?l=41 and referenced files, and rebuild some Fuchsia binaries
Test: Run package.py and verify the .a's are included.
Bug: 724204
Change-Id: If1492138829846a0f970d034f28a84d517554401
Reviewed-on: https://chromium-review.googlesource.com/1211879Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Scott Graham <scottmg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590521}

A code path enabled by the butter experiment was calling some
methods on the sync_service_. However, it can be null in
certain situations.

I updated the methods to handler the case where sync_service is null.

Bug: 883048
Change-Id: I64b4d52a5fc897381a99ad1502c0e6dbb937e447
Reviewed-on: https://chromium-review.googlesource.com/1220708
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Reviewed-by: Fabio Tirelo <ftirelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590520}

Bug: 880737
Change-Id: I2c455762066d424a3cde4e91dc70eacfc1b4fb7c
Reviewed-on: https://chromium-review.googlesource.com/1217033Reviewed-by: Esmael El-Moslimany <aee@chromium.org>
Commit-Queue: Scott Chen <scottchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590519}

This CL is adding events to help investigate crbug 882982.
We are observing strange interaction with the SamplerThread and the
Browser main thread.

We suspect the thread to be suspended for a longer period than expected.

This code is temporary to investigate sampler profiling issues.
Should be reverted in a few weeks.

R=wittman@chromium.org, ssid@chromium.org

Bug: 882982
Change-Id: I4aa1d733ea06100c64e884e014222b04d97b3492
Reviewed-on: https://chromium-review.googlesource.com/1220174Reviewed-by: Siddhartha S <ssid@chromium.org>
Reviewed-by: Mike Wittman <wittman@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590518}

The NavigationStateChangeObserver interface was renamed to
NavigationEventObserver in a previous CL. This CL finishes up the
rename by changing the file name too.

Change-Id: I6e1d17d7aadceb1736541be6bf4b8f8c40d7e81e
Reviewed-on: https://chromium-review.googlesource.com/1217515Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590517}

This is a very small set of machines, which have been exhibiting
- rendering artifacts when GPU compositing is enabled
- severe rendering artifacts when GPU raster is enabled

Bug: 875891
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: Ie49a9111b9723977a2b8758f824bba7843238d32
Reviewed-on: https://chromium-review.googlesource.com/1220180Reviewed-by: ccameron <ccameron@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590516}

This CL disables the MediaLauncherActivityTest tests that are flaking
due to a race condition.

TBR: mlamouri@chromium.org
Bug: 882938
Change-Id: I61ba23d0e4ed4a8890db8bcc0219ab4ea3804184
Reviewed-on: https://chromium-review.googlesource.com/1220701Reviewed-by: Tommy Steimel <steimel@chromium.org>
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590515}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll

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.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: Ie42fe469a9a86e83f9ce14cb428df1a792d427b5
Reviewed-on: https://chromium-review.googlesource.com/1220707
Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#590514}

Make --test-launcher-filter-file support multiple filter files separated
by ';'.

Bug: 881438
Change-Id: Ibe17d1e8443cbb490a2d1b8942bb003c96a79525
Reviewed-on: https://chromium-review.googlesource.com/1213866
Commit-Queue: Chong Zhang <chongz@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590513}

The controls sometimes disappear depending on the mouse interactions
with the window. For example, when the controls disappear automatically,
the controls should reappear when the user moves around the window.

Bug: 882615
Change-Id: Ic4c0a391d81ec6ea475d19be6cd60b40cb0ba277
Reviewed-on: https://chromium-review.googlesource.com/1217719
Commit-Queue: apacible <apacible@chromium.org>
Reviewed-by: CJ DiMeglio <lethalantidote@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590512}

This allows checking for potential data quality issues.
See b/112853960

Change-Id: I4d361cbc18dde8589d6da23026bbfa8d4db547cb
Reviewed-on: https://chromium-review.googlesource.com/1182291
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590511}

It appears to have enough bots. Will bump more if needed.

TBR=jbudorick@chromium.org

Bug: 646404
Change-Id: I4046177c2adb2916ec293cc1961753577739e4c9
Reviewed-on: https://chromium-review.googlesource.com/1220703Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590510}

Bug: 828468
Change-Id: Ib604bfe647900d3afca46ca6fdcdb5f365d25198
Reviewed-on: https://chromium-review.googlesource.com/1220572Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#590509}

It might? be the cause of a perf regression.

Bug: 882471,680657
Change-Id: Iec34a348426ccfdf5864a3b2cbe0c377da20ac0e
Reviewed-on: https://chromium-review.googlesource.com/1220468
Commit-Queue: Chris Palmer <palmer@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590508}

Disabling all tests in ProxySettingTest class as they can't be run on
Android platforms.
These tests require multiple sessions which is not supported on Android.

Change-Id: I6bf6cfbe8ba9f74b67d7beb84f68d79ee0a53966
Reviewed-on: https://chromium-review.googlesource.com/1220698Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590507}

Fix a bug in which AppListView crashes when layout()
is called. This is because
|app_list_background_shield_mask_| may not be
initialized when layout() is called.

Bug: 882553
Change-Id: I582be13c4998c262de89cc9c46543bbdcb9c9801
Reviewed-on: https://chromium-review.googlesource.com/1220033Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Daniel Zhang <oxyflush@google.com>
Cr-Commit-Position: refs/heads/master@{#590506}

This follows the page's logic of only interrupting for
some of the debugger commands.

To achieve this, we switch from running a tight loop with
only inspector tasks to a nested message loop (again, similar to
the main frame). This requires making some operations respect
PausableObject semantics, noticeably worker's ResourceFetcher,
post message and evaluating initial scripts.

WorkerInspectorProxy now either posts a regular task or
interrupting task similar to how DevToolsSession does it.

This is a preparation to unifying workers and page debugging
experience and implementation.

Bug: 775132
Change-Id: I1c8ccd98c2c9a35fa7ab0b91017b924a81a297b1
Reviewed-on: https://chromium-review.googlesource.com/1205802
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590505}

Aids with the integration of Contextual Search with Unified Consent by
recording whether the user was previously undecided when their
preference gets changed due to Unified Consent, and whether to throttle
for every request and when throttling is in effect.

BUG=829597

Change-Id: I28c10e10faee25dd6741243c4560d9ed74fa75ef
Reviewed-on: https://chromium-review.googlesource.com/1214402Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Donn Denman <donnd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590504}

BUG=800033

Change-Id: I9e9b1904004b0f4e82806b53b0fa53e8abfea396
Reviewed-on: https://chromium-review.googlesource.com/1220551
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590503}

This reverts commit 65103ba6.

Reason for revert: A proper fix was sent to clank downstream by jbudorick@ (https://chrome-internal-review.googlesource.com/c/clank/internal/apps/+/670069), so this is no longer needed.

Original change's description:
> [Autofill] Bring back isAutofillEnabled and setAutofillEnabled
> 
> The functions are still used by Clank downstream and will be removed
> once only the new preferences are used by it.
> 
> TBR=mathp@chromium.org
> 
> Bug: 879384
> Change-Id: Ibee61db92a2bd3cd8b4124b79fc1c0d747d401d1
> Reviewed-on: https://chromium-review.googlesource.com/1198453
> Reviewed-by: Fabio Tirelo <ftirelo@chromium.org>
> Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#587912}

TBR=ftirelo@chromium.org

Change-Id: I415c94a269e97637774af17289f7699215ed9a4f
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 879384
Reviewed-on: https://chromium-review.googlesource.com/1199564Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590502}

Resources are only explicitly returned from OnDraw. This means it's
possible for resources to be stuck in RenderThreadManager
returned_resources_map_ indefinitely, if OnDraw stops.

Post a task with roughly 2 frames of delay to return these resources to
ensure that they don't get stuck indefinitely.

Bug: 881957
Change-Id: I2a6331b9251b4057125761eb9fb0aaf29c881eeb
Reviewed-on: https://chromium-review.googlesource.com/1214700Reviewed-by: Tobias Sargeant <tobiasjs@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590501}

Histograms will be logged starting with M-71, so add an
expiration date of M-76 (five releases or a bit over
six month).

Bug: 881250
Change-Id: I73fb44340755f3fb1afbf2d01e34c5068dc49da9
Reviewed-on: https://chromium-review.googlesource.com/1219233Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590500}

Demo mode is mainly implemented in //chrome, but there're some
initialization needed in //ash. Currently they are placed in
|SessionController::SetIsDemoSession|, we should consider creating
a demo_mode_controller in //ash if the logic becomes complex later.

Bug: 882700
Test: Manual, with/without Mash feature
Change-Id: I945d003875b0cf3864f5796810d09c83e30b76ea
Reviewed-on: https://chromium-review.googlesource.com/1220179Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590499}

Change-Id: I55bc9e154abd300804d44988b35725c3c452011f
Reviewed-on: https://chromium-review.googlesource.com/1220038
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590498}

This CL uses ScopedBlockingCall to mark blocking calls in /chrome/browser/memory_details_android.cc.

This CL was created by replacing calls to AssertBlockingAllowed()
with instantiations of ScopedBlockingCall(MAY_BLOCK).
I kindly ask the reviewer to make sure of the following:
  - ScopedBlockingCall is instantiated in a scope with minimal CPU usage.
    If this is not the case, ScopedBlockingCall should be instantiated
    closer to the blocking call. See scoped_blocking_call.h for more
    info. Please let me know when/where the blocking call happens if this needs
    to be changed.
  - Parameter |blocking_type| matches expectation (MAY_BLOCK/WILL_BLOCK). See
    BlockingType for more info. While I assumed MAY_BLOCK by default, that might
    not be the best fit if we know that this callsite is guaranteed to block.
  - The ScopedBlockingCall's scope covers the entirety of the blocking operation
    previously asserted against by the AssertBlockingAllowed().

This CL was uploaded by git cl split.

R=dtrainor@chromium.org

Bug: 874080
Change-Id: I26104d2e0bc7817b955152a60a8ee4c97b033079
Reviewed-on: https://chromium-review.googlesource.com/1191418Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Siddhartha S <ssid@chromium.org>
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590497}

The FusedLocationProvider API determines which location providers to use
based on a priority mode specified in the API call. In
PRIORITY_BALANCED_POWER_ACCURACY mode, the request will never cause
power-intensive providers like GPS to be used unless another app
requests it. Instead, the network provider is preferred.

If Android is configured to disable network location providers but to
enable sensors (like GPS), then elevate the priority of the request to
improve the likelihood that GPS sensors will be used to acquire a
location.

BUG=620003

Change-Id: Ia11b7d367b0bdf89631a3e0ccfc696daf1d238a3
Reviewed-on: https://chromium-review.googlesource.com/1182289
Commit-Queue: Matt Reynolds <mattreynolds@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590496}

The root scroller is also known as the outer viewport and is not always the
root frame's LayoutView. If the root scroller is a child of the root frame,
the clips between the child and the root frame should not apply to the root
scroller. Previously, this was implemented by disabling clipping on the
ancestor GraphicsLayers of the root scroller. This patch changes the behavior to
adjust all ancestor clips in LayerTreeHostImpl::UpdateViewportContainerSizes.
This should be safe because of the restrictions on what can be a root scroller.

Bug: 879610
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-gen-property-trees;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I1974ae6b2a2f130cc2ce4a4d90e3dea1c9d64340
Reviewed-on: https://chromium-review.googlesource.com/1217509
Commit-Queue: Philip Rogers <pdr@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590495}

It is an update of required version number of the component.
The current version number of the package is 1.6.23.2 .

BUG=chromium:869939
TEST=Tested on nautilus with the autotest platform_PrinterPpds

Change-Id: I4c16d960640cb7e8e30e49653451bce0ff51c517
Reviewed-on: https://chromium-review.googlesource.com/1212445Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Sean Kau <skau@chromium.org>
Commit-Queue: Piotr Pawliczek <pawliczek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590494}

TabRedirectHandler can be null when swapped out for VR mode change,
for which it should not be put into UserDataHost when restored.
This CL adds the missing null check to prevent crash upon exiting
VR mode.

Bug: 882977
Change-Id: I67f740eceffb2ad2acde12501d142583a10d052b
Reviewed-on: https://chromium-review.googlesource.com/1220407Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590493}

Using wpt-import in Chromium 5954a8c7.
With Chromium commits locally applied on WPT:
d3406a52 "Add more WPT tests for mixed-content check in workers/worklets (2/2)"


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/24555

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
cbiesinger@chromium.org:
  external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/flexbox

NOAUTOREVERT=true
TBR=lukebjerring

No-Export: true
Change-Id: I9f1bcec6bcabe0724d0f15995ac1d69344436c52
Reviewed-on: https://chromium-review.googlesource.com/1219997
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590492}

There is no logic change - this just move the code around for
optimization.

This CL specifically fixes verification errors around field access.
Also, it avoids extra type conversion which was causing another
verification error.

See crbug.com/838702 for more information about run-time verification
issue.

Bug: 868250
Change-Id: I00c593e9526ddc3766d0c5b203ed38816c5c6da0
Reviewed-on: https://chromium-review.googlesource.com/1218522
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590491}

https://chromium.googlesource.com/catapult.git/+log/b7f5c6989122..6333b6741efe


git log b7f5c6989122..6333b6741efe --date=short --no-merges --format='%ad %ae %s'
2018-09-11 eakuefner@chromium.org Revert "[TBMv2] Support Chromium commit positions in legacy_json_converter"
2018-09-11 eakuefner@chromium.org [TBMv2] Support Chromium commit positions in legacy_json_converter


Created with:
  gclient setdep -r src/third_party/catapult@6333b6741efe

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll

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.

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

BUG=chromium:843643,chromium:843643
TBR=sullivan@chromium.org

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

Adds an option "emulate page focus" that stops blur listeners from
firing on the page. Useful for debugging focus issues.

Change-Id: I87086715d87514738a68b5b38f4df31693b97546
Reviewed-on: https://chromium-review.googlesource.com/1119257
Commit-Queue: Joel Einbinder <einbinder@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590489}

This patch reomves some obsolete code that was used to transition
theme colors on the tab border in the tab switcher. This feature
has since been removed.

Bug: 882508
Change-Id: Ie63fabb08631f0377721f7057cbe65a4cd3af9a2
Reviewed-on: https://chromium-review.googlesource.com/1217405Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590488}

Bug: 882979
Change-Id: I7c4b717a39da3ee11d62a9bd5d91e7a5b42d6b2e
Reviewed-on: https://chromium-review.googlesource.com/1220469Reviewed-by: Adrienne Porter Felt <felt@chromium.org>
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590487}

https://pdfium.googlesource.com/pdfium.git/+log/7a45d5722c7e..5c86fd4c5110


git log 7a45d5722c7e..5c86fd4c5110 --date=short --no-merges --format='%ad %ae %s'
2018-09-11 rharrison@chromium.org Small optimizations for CBC_HighLevelEncoder::lookAheadTest


Created with:
  gclient setdep -r src/third_party/pdfium@5c86fd4c5110

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

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.



BUG=chromium:881678
TBR=dsinclair@chromium.org

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

R=jbudorick@chromium.org

Change-Id: Ic593c71edc288deb6aa9480b2bf9542722b38f0f
Reviewed-on: https://chromium-review.googlesource.com/1217914Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590485}

Disabling failing Java tests on Android platform.

Change-Id: I0b07e9e2d961aedc8127470e4dc4e8ec16dee6f9
Reviewed-on: https://chromium-review.googlesource.com/1219933Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590484}

Previously, IP address matching for whitelisted-ips options was done by
string comparison, and was unreliable. In particular, it didn't handle
IPv4-mapped IPv6 addresses. To make the matching more robust, we now do
binary comparison using IPAddress object.

Bug: chromedriver:2566
Change-Id: I81430ecef60b44dbc40a976637cdb42ed50acde1
Reviewed-on: https://chromium-review.googlesource.com/1220474
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590483}