GitLab

The previous tweak did not disable all possible webview browsers like,
e.g., android-webview-google.

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

Bug: 865947
Change-Id: I82057800a73057435e8ad11c64ba2374e2ef3210
Reviewed-on: https://chromium-review.googlesource.com/1219608
Commit-Queue: Ivan Šandrk <isandrk@chromium.org>
Reviewed-by: Drew Wilson <atwilson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590354}

https://android.googlesource.com/platform/external/perfetto.git/+log/1f658fe0d651..56de9d6b2972


git log 1f658fe0d651..56de9d6b2972 --date=short --no-merges --format='%ad %ae %s'
2018-09-11 taylori@google.com Merge "trace_processor: Fix parsing bug"


Created with:
  gclient setdep -r src/third_party/perfetto@56de9d6b2972

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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.


TBR=perfetto-bugs@google.com

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

If condition used pending_navigation_params_ that is always false there.
Usage might have been corrupted during refactorings without being noticed,
or was never working.

Skip was removed, CHECK added as well as a TODO to reintroduce the
functionality.

Bug: 882800
Change-Id: I0cafc9dda082a395d48783cac03ec0d25a1ec73e
Reviewed-on: https://chromium-review.googlesource.com/1202462Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Arthur Hemery <ahemery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590352}

Bug: none.
Change-Id: I28b7355d1a7d5cde785fbab40250ae2040c2ff65
Reviewed-on: https://chromium-review.googlesource.com/1212144Reviewed-by: Justin Schuh <jschuh@chromium.org>
Commit-Queue: Justin Schuh <jschuh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590351}

* Emit checked state changed events for checkboxes and radio buttons.
* Emit pressed state changed events for toggle buttons.
* Emit indeterminate state changed events for tri-state widgets when
  their state becomes "mixed."
* Remove checkable state for toggle buttons.

R=dmazzoni@google.com

Bug: 866341
Change-Id: I10e08330408c6f783e202d2c81c6c70d19309d08
Reviewed-on: https://chromium-review.googlesource.com/1219726Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Joanmarie Diggs <joanmarie.diggs@gmail.com>
Cr-Commit-Position: refs/heads/master@{#590350}

This CL changes SyncAndServicesPreferences to make
UnifiedConsentServiceBridge.isUnifiedConsentGiven a source of truth when
updating prefs. Before, mUseSyncAndAllServices was used in some places,
leading to inconsistencies when UnifiedConsent state can't be changed
(for example, because of a custom passphrase).

Bug: 882884
Change-Id: Ie9be1b73284a7a818c21d702c47712b787d52846
Reviewed-on: https://chromium-review.googlesource.com/1219927Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590349}

This reverts commit 6e2e384b.

Reason for revert: Not sure why, but seems a pretty clear culprit for crbug.com/882832

Original change's description:
> Update bundled Chrome app icon for MD compliance
> 
> - Update chrome_app manifest to support 32 and 192px icons.
> - Use 192px icon as window icon for Chrome browser.
> - Move all resource handing related to chrome_app under
>   OS_CHROMEOS ifdef.
> 
> Bug: 879618
> Test: manual
> Change-Id: If3e9fb396424159ea0bf7f2cf61febfd89838b62
> Reviewed-on: https://chromium-review.googlesource.com/1210943
> Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org>
> Reviewed-by: Lei Zhang <thestig@chromium.org>
> Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#589771}

TBR=kaznacheev@chromium.org,oshima@chromium.org,thestig@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 879618
Change-Id: Idd28ce462ab64d417e4c6137a8ecbc7966975f42
Reviewed-on: https://chromium-review.googlesource.com/1219908Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590348}

Currently this methods works as O(N*M), where
N = size of imported_resources_ in the provider
M = number of resources being received by the provider

That is because each received element is removed individually from the
imported_resources_ set, and each removal will cost O(N).

Instead, sort the incoming resources, then walk through the two
sets of resources in parallel, which is O(N+M). During this walk,
replace resources to be removed from imported_resources_ with resources
that we are keeping as we walk, which is O(1). Then erase the empty space
created by this process at the end of the loop, which is O(N). This
makes the complexity O(2N+M) = O(N+M).

This is similar to the std::remove_if() algorithm, except that we have
to write it ourselves to avoid O(M) work at each step, and instead walk
the received resources in parallel.

We also sort the returned M resources as a prelude, to ensure we can do
the walk in parallel. This costs O(MlogM), making the whole thing
O(N+MlogM).

Similarly, for ClientResourceProvider::ReleaseAllExportedResources()
stop removing elements individually. In this case we can use
base::EraseIf to iterate through the set, act on each element, and
return true if it should be erased.

R=piman@chromium.org

Bug: 881295
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I94522eb07e2f09b20a10d8f254faa63fd2ab9d0e
Reviewed-on: https://chromium-review.googlesource.com/1211908
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590347}

For details, please see https://docs.google.com/document/d/1yh_-ayeaFV0EjuR51U641zbrPAB0Baqj6UrC9bT9iqQ/edit#heading=h.7qo26jlhd6ob

BUG: 874113, 874629
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I0762229d550bb7b06518f22657113b4a52e3da6b
Reviewed-on: https://chromium-review.googlesource.com/1199858Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Luna Lu <loonybear@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590346}

Bug: 878388
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Ic68969370562563a90159167bada0b822893ff8b
Reviewed-on: https://chromium-review.googlesource.com/1212983Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Commit-Queue: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590345}

This CL makes different WebShareTargets a reason to generate an update
for a WebAPK. Presently, updating the share_target doesn't trigger an
update.

This CL originally from ckitagawa@'s CL: https://crrev.com/c/1185522.

Bug: 795165
Change-Id: Ie08cf9edaff4cdfbf2e7148aead03c8d92c20f68
Reviewed-on: https://chromium-review.googlesource.com/1190422
Commit-Queue: Xi Han <hanxi@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590344}

Move Set/GetNativeWindowProperty to the browser-side
BridgedNativeWidgetHostImpl. Also, change from using a NSDictionary
attached to the NSWindow to just using a std::map -- these properties
do not actually need to be attached to the NSWindow.

Move Set/RemoveAssociationForView and ReorderChildViews to the
browser side, because that's where the views::View hierarchy is
stored. Compute the appropriate NSView->rank map and then send that
to the BridgedNativeWidgetImpl (in the future, this will be a
handle->rank map, when crossing process boundaries).

Bug: 859152
Change-Id: I142ec9eb180a81a9e456957bc9f42f32ab7de792
Reviewed-on: https://chromium-review.googlesource.com/1217450Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590343}

https://skia.googlesource.com/skia.git/+log/bd6595544171..2473d9472049


git log bd6595544171..2473d9472049 --date=short --no-merges --format='%ad %ae %s'
2018-09-11 halcanary@google.com SkPDF: allocate for single Canvas
2018-09-11 michaelludwig@google.com Base Gradient FP Refactor


Created with:
  gclient setdep -r src/third_party/skia@2473d9472049

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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=master.tryserver.blink:linux_trusty_blink_rel;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
TBR=caryclark@chromium.org

Change-Id: Iffd7bb86c8a54dd52a06872e50182a1905bba396
Reviewed-on: https://chromium-review.googlesource.com/1219986Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#590342}

If a technology gets left in the 'enabling' (or any other) list
but becomes unavailable, it should not be provided as an available
technology. Also, 'prohibited' technologies are correctly prioritized.

This CL also modernizes the technology list iterators and only signals
a change when the list actually changes.

Bug: 809940
Change-Id: I9aa60ea5027f74b52d831e3a872c8ce7ffccb863
Reviewed-on: https://chromium-review.googlesource.com/1186097Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Alexander Hendrich <hendrich@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590341}

DRM_FORMAT_ARGB8888 (which is B,G,R,A in memory order) matches the used
GL internal format and is also more widely supported by minigbm drivers.

Bug: 882825
Change-Id: I909ceb04172e4c7a97c97e9c94a36f3bb467053a
Reviewed-on: https://chromium-review.googlesource.com/1219387Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590340}

Add an exit code for zip archiver sandbox to report unexpected sandbox disconnection.

Bug: crbug.com/881988
Change-Id: Ib38a8cd85876fc8dc186e0c62a377f51d22f5ea2
Reviewed-on: https://chromium-review.googlesource.com/1216025Reviewed-by: Chris Sharp <csharp@chromium.org>
Commit-Queue: Che-yu Wu <cheyuw@google.com>
Cr-Commit-Position: refs/heads/master@{#590339}

This experiment is already done, so remove these two lines.
As long as all bots are green, this should be saefe.

TBR=pdr@chromium.org

Bug: None
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ie27fa10cdde06cb9938cb0d7b5d55ad6fe9946fd
Reviewed-on: https://chromium-review.googlesource.com/1219782Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590338}

https://webrtc.googlesource.com/src.git/+log/7cd0e15faf17..375d35e01b11


git log 7cd0e15faf17..375d35e01b11 --date=short --no-merges --format='%ad %ae %s'
2018-09-11 sprang@webrtc.org Make ilnik@ owner in video/ and modules/video_coding/


Created with:
  gclient setdep -r src/third_party/webrtc@375d35e01b11

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng

BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

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

BUG=

Change-Id: Id8b068f4524181e85ab483ec74a300b06a116334
Reviewed-on: https://chromium-review.googlesource.com/1217542Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590336}

That arg has been shown to cause the browser to crash on cros VMs.

Bug: 876494
Change-Id: I217451ce65a78b62a947a8b2b77618875e83dd7f
Reviewed-on: https://chromium-review.googlesource.com/1217913Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590335}

Add metrics for ImageFetchTabHelper::GetImageDataByJs to check if fetching
image data by JavaScript methods works very often. If not, remove the JavaScript
methods that are not likely to succeed.

Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I22a1bc9f16575d40836b7ed020a1e81a8c6a1b1e
Reviewed-on: https://chromium-review.googlesource.com/1213146
Commit-Queue: Yi Su <mrsuyi@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590334}

With this change, scripts without precondition are not treated as
invalid, but runnable. Also includes a small test
ProtocolUtils::ParseScripts.

Bug: 806868
Change-Id: I6c286b1622bfeb4d635310396cb3b158ffd6933e
Reviewed-on: https://chromium-review.googlesource.com/1219748Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Commit-Queue: Stephane Zermatten <szermatt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590333}

More suitable for DEPS runhooks running.

Bug: 724204
Change-Id: I105a57269b4c4f7b4b05bab80df7a4ef112bdf1f
Reviewed-on: https://chromium-review.googlesource.com/1217850Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Scott Graham <scottmg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590332}

This CL also makes sure that the default base::MemoryPressureMonitor
won't be created when running browser tests.  This helps insulate the
tests from their environment and ensure that the tests behave
deterministically (rather than flakily depending on things outside the
test control, like the overall memory pressure on the bot which runs the
test).  This is accomplished by avoiding creating the monitor if
--browser-test switch is present.

Before this CL, the --browser-test switch would be injected by
ContentBrowserTest::SetUp.  After this CL, the switch is injected by
BrowserTestBase::SetUp - this means that insulation from memory pressure
covers not only content_browsertests, but also browser_tests (and other
tests that subclass BrowserTestBase rather than ContentBrowserTest).

This CL also makes tweaks in memory-pressure-monitoring code to make
sure that things work properly after the changes described above.
In particular, the CL also makes the following changes:

- Move DummyMemoryPressureMonitor from
  //chrome/browser/chromeos/resource_reporter/resource_reporter_unittest.cc
  into //base (renaming the class into FakeMemoryPressureMonitor), so
  that it can be reused by TabManagerTest.OomPressureListener browser
  test.  Note that the FakeMemoryPressureMonitor has to be constructed
  and present early during browser startup (so that TabManager::Start
  detects presence of the monitor).

- Stop incorrect downcasting that used to be made by
  base::chromeos::MemoryPressureMonitor::Get

There are also some opportunistic changes that are not really required
for correctness:

- Rewrite TabManager::OnMemoryPressure to follow most recent
  style guidelines that help enforce that missing a switch/case
  branch will lead to a compile error (thanks to a missing "default"
  branch).

Bug: 852905
Change-Id: I6eb651a4f7a7bc6d1a2138ba31dd248c7e33f2a4
Reviewed-on: https://chromium-review.googlesource.com/1194879
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590331}

Also add new ERROR_IN_ARCHIVER removal status value, and update the
override permissions map to handle it.

Full code and tests to deal with QuarantineStatus will come in a
followup.

R=csharp

Bug: 830892
Change-Id: Ib002f44b8aba6899f54b44148d8645c3c0c7178f
Reviewed-on: https://chromium-review.googlesource.com/1217148Reviewed-by: Chris Sharp <csharp@chromium.org>
Commit-Queue: Chris Sharp <csharp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590330}

TBR=twellington@chromium.org,bsazonov@chromium.org

Bug: 789531
Change-Id: I7ca028d21988508247c3798d8ce5fc1c5eba91f6
Reviewed-on: https://chromium-review.googlesource.com/1219613
Commit-Queue: Dominic Battré <battre@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590329}

Some recent reports indicate that the Sync server might be sending
duplicate client tag hashes. This is considered "invalid data", and is
so far not handled well by the client. These metrics will help us
evaluate how common this case is, and also whether the duplicates are
within a single GetUpdates response, or across multiple responses
(within a full paginated GetUpdates cycle).

Bug: 872360
Change-Id: Id24baa351c80f2eb1ab59f890d50d6603cb89e6b
Reviewed-on: https://chromium-review.googlesource.com/1203935Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590328}

In jumbo builds whole chunks of the code is compiled in the same
translation unit, using the same anonymous namespace. If two
files use the same symbol names they will then clash and that
happened in chrome/browser/extensions between
active_tab_permission_granter.cc and extension_tab_util.cc.

This patch renames GetDelegate() and GetDelegateWrapper to include
the more exact names of the Delegate type, making them unique.

Bug: 865947
Change-Id: I46426e8dee715d57acaa3d2385e6dd5b6ac38cf1
Reviewed-on: https://chromium-review.googlesource.com/1219246
Commit-Queue: Daniel Bratell <bratell@opera.com>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590327}

This is consistent with the bug backtrace, but not clearly with it
being a regression.

Also don't rely on sequencing within the same expression when setting up
the map.

Bug: 881905
Change-Id: I50ab04196e06e326d4489325fb5bb8adda786c8c
Reviewed-on: https://chromium-review.googlesource.com/1219806
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590326}

Unfortunately, the previous CL
(https://chromium-review.googlesource.com/1218902) lacked an important
negation.

TBR=sky@chromium.org

Bug: 882545
Change-Id: I730dbab7c05b0d67c11be67437b462ac51afd7b3
Reviewed-on: https://chromium-review.googlesource.com/1219750Reviewed-by: Dominic Battré <battre@chromium.org>
Commit-Queue: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590325}

This CL extends the autofill form upload "vote" proto to include
rich form/field metadata.

Autofill will crowd-source bit-level randomized encodings of the
first 64 bytes of the form's id, name and action as well as each
field's id, name, label, aria-label, aria-description, css-class,
placeholder value, plus a hash of the field initial value (to
detect placeholders that are prepopulated as initial values).
Each uploaded bit will randomly be sent as the true value or as
a random value.

Bug: 850606
Change-Id: I470876e4a04fca6cfabf5482f998573eacf86aa1
Reviewed-on: https://chromium-review.googlesource.com/1213878Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Reviewed-by: Maxim Kolosovskiy <kolos@chromium.org>
Commit-Queue: Roger McFarlane <rogerm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590324}

This CL wires all the parts and enables Manual Fallback, still work in
progress, behind it's flag.

Bug: 845472
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I8bef297135511a1d122dcac0c6199e263f112566
Reviewed-on: https://chromium-review.googlesource.com/1203994
Commit-Queue: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590323}

Storage and Location tests are failing on Android Chromium.
Disabling tests for now.

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

It was already disabled on Win 10, but it was failing on Win 7 also.

TBR=sullivan@chromium.org
CC=kouhei@chromium.org, ksakamoto@chromium.org
NOTRY=true

Bug: 879833
Change-Id: I926a38ef6713a0eaec1eebae71948e6dcc9d49b7
Reviewed-on: https://chromium-review.googlesource.com/1219966Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590321}

https://skia.googlesource.com/skia.git/+log/b42a897819dc..bd6595544171


git log b42a897819dc..bd6595544171 --date=short --no-merges --format='%ad %ae %s'
2018-09-11 brianosman@google.com Remove SkImageCacherator entirely


Created with:
  gclient setdep -r src/third_party/skia@bd6595544171

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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=master.tryserver.blink:linux_trusty_blink_rel;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
TBR=caryclark@chromium.org

Change-Id: I623c92c6ad94f17f97c1e8c15cd2cfd64d584c24
Reviewed-on: https://chromium-review.googlesource.com/1219415Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#590320}

Bug: 873098
Change-Id: Ic349be8e16680b2ccbf08e7ecbdee9dab7987077
Reviewed-on: https://chromium-review.googlesource.com/1176081Reviewed-by: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Commit-Queue: Anna Malova <amalova@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590319}

TBR=sullivan@chromium.org
NOTRY=true
CC=yukishiino@chromium.org, jbroman@chromium.org, haraken@chromium.org

Bug: 882881, 882882, 882883
Change-Id: Id509634ea963f688bc5cc0b761b1430398688ea2
Reviewed-on: https://chromium-review.googlesource.com/1219783Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590318}

Now that we have an ad flag in the browser process, log per resource
metrics for ad resource sizes. Also log new metrics for total ad bytes
per-page and for top-level ads now that this information is
available in the browser process. These metrics are different than the
existing page byte totals as they account for network bytes that went
towards canceled and incomplete resource loads.

Bug: 851543,859080
Change-Id: I2ad863f0fc718f51521269d7ffd1c1bb8d0bf886
Reviewed-on: https://chromium-review.googlesource.com/1199576
Commit-Queue: John Delaney <johnidel@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590317}

The goal is to allow experimentation with different font weights
for primary info for Payment Methods and Addresses suggestions on
the Autofill dropdown.

Screenshots on Windows (Googlers only): https://drive.google.com/open?id=1BhZdvN0l9GTzZv2kvim7_OCE9r9OsOhK

Bug: 882525
Change-Id: I9d1ec9ad662e858bd0d9c85c3b31849f13220b86
Reviewed-on: https://chromium-review.googlesource.com/1217171
Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590316}