GitLab

The document element is always contained in LayoutView. The subsequence
for LayoutView and the early return in full-cached situation in
GraphicsLayer::PaintWithoutCommit() (for pre-CompositeAfterPaint) make
the subsequence for the document element useless.

This CL avoids paint chunks that were forced for the document element
by the subsequence. These paint chunks are useless for layerization in
CompositeAfterPaint because they should be always merged into the
scrolling contents layer of the LayoutView, but had overall drawback on
raster invalidation.

Many paint invalidation web tests have raster invalidation clients and
reasons. Some tests progress with less raster invalidation because of
stabler paint chunk ids.

paint/invalidation/css-grid-layout/grid-item-z-index-change-repaint.html
regresses with more raster invalidation when the document element's
negative-z-index children becomes positive-z-index, which is rare and
acceptable.

This is also a preparation of crrev.com/c/2070688 which will fix
transparent background hit test in CompositeAfterPaint, to avoid
extra paint chunks that would otherwise be created for the document
element in that CL.

Change-Id: Ic72c4ad4c1e0ce6cd967973b1158965f549580e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083380
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746070}

- The deliver window should be within notification expiration config.

Bug: 1057272
Change-Id: Ib859870d16a53f937ac8849d7cc989d08b86975e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079270Reviewed-by: Xing Liu <xingliu@chromium.org>
Commit-Queue: Hesen Zhang <hesen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746069}

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll
Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
Tbr: cr-fuchsia+bot@chromium.org
Change-Id: I027ec43ea634324fab49339dd5e2eef0cc0eaf8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2082608Reviewed-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@{#746068}

This CL moves the FileTypePolicies and associated code to
components/safe_browsing/core. This is useful for fixing our measurement
of the download warning CTR. In a future CL, I will refer to this code
from components/download to record click throughs based on the UMA
value for the download.

Bug: 1053772
Change-Id: I47708b0395eee9997ebdaf01435993107e23b687
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076416Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Bettina Dea <bdea@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746067}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ff1896a1..93969500

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Ic99b55b6a34a039e41177c56299edd7f101989bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083651Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#746066}

... in the chain of URLLoaderFactory proxies. This ensures that DevTools
network interception is closer to network and intercepts preflight
requests produced by CorsURLLoader.
The implementation relies on URLLoaderFactoryOverride introduced
by crrev.com/c/1928100.

Bug: 1027011, b/132267312
Change-Id: I9b5f629d5d92048d6d763ba743e3967f646b5d52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2073146Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746065}

This is a reland of 334077c8

Original change's description:
> Vulkan: support Android devices without Android hardware buffer
> 
> Some Android P devices don't support vulkan extension
> VK_ANDROID_external_memory_android_hardware_buffer. For those devices,
> chrome will fallback to ExternalVkImageBacking which uses
> VK_KHR_external_memory_fd extension or pixel copy for GL and Vulkan
> inerop.
> 
> Bug: 1049864
> Change-Id: I101a4c83a2dbfcfdbade29084a863e7563f631e6
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067290
> Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
> Reviewed-by: Michael Spang <spang@chromium.org>
> Commit-Queue: Peng Huang <penghuang@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#743931}

Bug: 1049864
Change-Id: I8bfa463e06ee510203be1f66fbef1e7d46865869
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078594Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746064}

This new notification is originated when the attached power adapter does
not supply enough power.

BUG=b:147843861
TEST=deploy_chrome # Notification displays when power adapter is
connected

Change-Id: Ibb3852c584375d0ffa4ed99eb788fa1522fef80c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078905Reviewed-by: Polina Bondarenko <pbond@chromium.org>
Reviewed-by: Mattias Nissler <mnissler@chromium.org>
Commit-Queue: Daniel Campello <campello@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746063}

... now that the legacy IPC BeforeUnloadACK is no more.

This CL is a follow up of [1], were dtapuska@ asked to
move away from using the ACK terminology, now that it became
a mojo completion callback.

Basically, signature changes from OnBeforeUnloadACK() to
BeforeUnloadCompleted().

[1] https://crrev.com/c/2010920

BUG=1042800
R=arthursonzogni@chromium.org
TBR=kinuko@chromium.org

Change-Id: Id4c5b41648d2f799a35ceb689660fefff6ee16ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079096Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Cr-Commit-Position: refs/heads/master@{#746062}

The current implementation of VA-API encoder follows static/hard-coded
approaches to set the EntryPoint for the decode/encode/vpp pipelines.
It shouldn't be a problem for decode & vpp since only one type
of EntryPoint has been supported by the VA-API based UMDs.
But it will mess up the logic of encoder pipeline. For eg: Some of the
IA platforms (eg: KBL) support both VAEntryPointEncSlice and
VAEntryPointEncSliceLP for H264(AVC). On the other hand newer platforms
may only support VAEntryPointEncSliceLP. Upcoming TGL devices are
perfect examples where we will only have the VAEntryPointEncSliceLP for VP9
encode. With out this proposed patch, the current chromium vaapi code base
will only check the support of a VAEntryPointEncSlice for any non-JPEG encode
profiles during the early stages of vaapi configuration and that will
leads to software fallback and related issues.

This patch tries to generalise the Entrypoint selection.

For generic methods like GetSupportedProfiles (which will usually get
invoked even before Initializing the accelerator so that upper level can
switch between software and hardware encode), we query the driver for
each profile+entrypoint combo and keep the order of EntryPoints as returned by
the User Mode Driver. Selection of actual EntryPoint to be used for the
encoding will happen later on, during the VaapiWrapper initialization.

BUG=1057196
TEST= Manually, Run the H264 encoder applications on different platforms like
Kabylake, Broadwell etc with VaapiLowPowerEncoder enabled.
Kabylake should be utilizing the low-power encode(VAEntrypointEncSliceLP) and other older
platforms should fall back to dual-pipe-encoder (VAEntrypointEncSlice).
Check the VLOG,DVLOG outputs to ensure the entrypoint. Also run the VP9
encoder application on a platform where there is only
VAEntrypointEncSliceLP support (eg: ICL, TGL) for the accelerated vp9
encoder and make sure the chromium media encoder pipeline is not falling
back to the software.

Change-Id: Ic80ad7a3dee0e32dd8de2a6a0f0094a3d28f40c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2075899
Commit-Queue: Sreerenj Balachandran <sreerenj.balachandran@intel.com>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746061}

Before crrev.com/c/1899420, bluez informed Chrome each time an
advertisement was received, even if nothing had changed about the
advertisement from its previous instance. Once that CL landed,
bluez switched to only informing Chrome of an advertisement when
it was first found during a scan, or when metadata of the
advertisement changed (i.e., RSSI, which can remain unchanged
for several seconds). This CL accounts for that new behavior
by informing observers an advertisement has been received on
the DeviceAdded() event.

I ran an Instant Tethering scan 50 times without this patch, and
50 times with it, and recorded time taken to find an expected BLE
advertisement (found in chrome://histograms):

* Without patch:
  * Mean:             4436 ms.
  * Median:           1680 ms.
  * 75th percentile: 11135 ms.
  * 95th percentile: 12185 ms.

* With patch:
  * Mean:              636 ms.
  * Median:            522 ms.
  * 75th percentile:   895 ms.
  * 95th percentile:  1838 ms.

Fixed: b:149945805,1051769
Change-Id: I73dc1d5678d166a6ce443ddfda76c34212aa92aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2071377Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746060}

Add a new device command to send a command to an existing
diagnostic on the platform and get back an update from the
diagnostic.

Bug: chromium:1049762
Test: DeviceCommandGetRoutineUpdateJobTest.*
Change-Id: I011c320ef242304a403dfb200e0a15b92f0db45a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076521
Commit-Queue: Paul Moy <pmoy@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746059}

https://webrtc.googlesource.com/src.git/+log/ae92244054c4..f52d3ed084e3

git log ae92244054c4..f52d3ed084e3 --date=short --first-parent --format='%ad %ae %s'
2020-03-02 srte@webrtc.org Adds transport overhead to route changes in scenario tests.

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: None
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: I0df7beef79e7aeda475e8868868992a2465e4a07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083618Reviewed-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@{#746058}

This CL converts base::Bind and base::Callback in //ppapi/thunk to Once
or Repeating

Bug: 1007819
Change-Id: Ib46aaf7a3465a0e9e55b73d58e73e6ed905cabac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078906
Commit-Queue: Jun Cai <juncai@chromium.org>
Reviewed-by: Bill Budge <bbudge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746057}

Allow checking for an array of values rather than a single value. This
clears up the situation where different UAs support different (and
disjoint) sets of values for a property. In this case 'image-rendering'.

Also adjust assertPresentationAttributeIsNotSupported(...) such that
the assert description makes more sense by adding a negation.

Bug: 1056055
Change-Id: Ibe5cddb09f242754f02aa96b4bc8571f2aabecf1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2082557Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#746056}

Change-Id: I5b56232b66fff49739500a171a28615be96f0b78
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079458
Commit-Queue: Yulun Wu <yulunwu@chromium.org>
Auto-Submit: Yulun Wu <yulunwu@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746055}

This fixes an inverted boolean: I meant to workaround bad cookies for
apps targeting < R, not apps targeting >= R.

Bug: 1052058
Test: Manual - log the value and launch com.discoverfinancial.mobile
Change-Id: I3d0007fdabcf366ec91739673883e9cffd335fcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2081362
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746054}

We never called Delete on the temporary directory created for this test.
Added delete call on teardown.

Change-Id: I186a798e63545daa55c4c196219202951e24bc43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2082881Reviewed-by: Min Qin <qinmin@chromium.org>
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746053}

Some of tests in chrome_public_test_apk requires play store to be installed.
The rest of test suites will stick with google_apis images,
as some of them need root permission to run tests.

Bug: 1057150, 1048781, 922145
Change-Id: I210b7b69ca5e5827abca0fd0ba90a89ddcb9d6f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2072408Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Haiyang Pan <hypan@google.com>
Cr-Commit-Position: refs/heads/master@{#746052}

The fix consists to let the SyncAuthManager do a retry to fetch the access token when the first request is canceled.

Bug: 1050313
Change-Id: I173830f5b28b9fe2ec2a2d67032b52fc2eef344e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062294
Commit-Queue: Vincent Boisselle <vincb@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746051}

In browser tests, remove using profile based theme provider. Also, the
previous ThemeIntegration test didn't seem working as intended, fix that
as well.

BUG=1056758

Change-Id: I8c9abb7289a739d91ed836d012a20ec149c8124e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2044433
Commit-Queue: Wei Li <weili@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746050}

As discussed @ https://groups.google.com/a/chromium.org/g/scheduler-dev/c/xQkcxeoMuyw

This is blocking migration of
base::PostTaskAndReplyWithResult(FROM_HERE, {BrowserThread::UI, ...);
to
content::GetUIThreadTaskRunner({})->PostTaskAndReplyWithResult(FROM_HERE, ...);

Tests copied from task_runner_util_unittest.cc.
Will migrate callers in a follow-up.

R=ajwong@chromium.org

Bug: 1026641
Change-Id: I6fe1b29238a23001d02b9d86da142dd071b39128
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076423Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Auto-Submit: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746049}

This CL moves chromeOS strings for settings Device display page strings
from settings_strings.grdp to os_settings_strings.grdp. It continues
the process of moving all chromeOS specific strings.

Bug: 967883
Change-Id: I24390ff6687cd0b66600913e7f862a97ae7f389c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067323
Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746048}

This reverts commit 783ef8ee.

Reason for revert: Rolling back to open tree

Original change's description:
> bind-gen: Implement V8DOMConfiguration::InstallConstants
> 
> Implements V8DOMConfiguration::InstallConstants for context-
> dependent property installation.
> 
> Bug: 839389
> Change-Id: I3f67010e247ff4b1719cafec37b0865c9e05aa75
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2081729
> Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
> Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#745959}

TBR=peria@chromium.org,yukishiino@chromium.org

Change-Id: I30c5534c7b41786c5982ab80a4e0995ff3682d46
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 839389
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083435Reviewed-by: Jeffrey Cohen <jeffreycohen@chromium.org>
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746047}

This reverts commit ead9dd18.

Reason for revert: The added builder doesn't work

Original change's description:
> add 'linux-rel-swarming' builder using chromium-swarm-staging
> 
> This adds copy of
> https://luci-milo-dev.appspot.com/p/chromium/builders/ci/linux-rel-swarming
> but use chromium-swarm-staging.appspot.com.
> 
> I don't have confidence whether this builder runs correctly at first,
> but let me try to see what happens.
> 
> Bug: b/144318226
> Change-Id: I3fba44f82619e6303fa2685063658eafbcbdf3b7
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989300
> Auto-Submit: Takuto Ikuta <tikuta@chromium.org>
> Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com>
> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#745826}

TBR=maruel@chromium.org,yyanagisawa@google.com,yyanagisawa@chromium.org,tikuta@chromium.org,jwata@google.com

Change-Id: I54ecad5adecb7283e309458a4edad4996bee7250
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: b/144318226
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083733Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746046}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/5f96597ad93d..23ee1aad0a5d

git log 5f96597ad93d..23ee1aad0a5d --date=short --first-parent --format='%ad %ae %s'
2020-03-02 mathias@chromium.org Reconfigure lint rule w.r.t. quotes
2020-03-02 almuthanna@chromium.org Remove duplicated function from helper
2020-03-02 jacktfranklin@chromium.org Extract `collapseWhitespace` into StringUtilities

Created with:
  gclient setdep -r src/third_party/devtools-frontend/src@23ee1aad0a5d

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: chromium:1050549,chromium:1057042
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I36e6802b3449df78abe93f67dfcd5ea2730d4218
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083226Reviewed-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@{#746045}

https://chromium.googlesource.com/angle/angle.git/+log/73034dfdf4b0..35785308a451

git log 73034dfdf4b0..35785308a451 --date=short --first-parent --format='%ad %ae %s'
2020-03-02 wangra@google.com Vulkan: reserve extra varyings

Created with:
  gclient setdep -r src/third_party/angle@35785308a451

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC ianelliott@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

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-asan;luci.chromium.try:win_optional_gpu_tests_rel
Bug: None
Tbr: ianelliott@google.com
Change-Id: Ic6f8e81a509e1721ff958ebbc8c79cdfe8d227ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083334Reviewed-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@{#746044}

This is the first of a series of two CLs expanding the Fetch API, when
the runtime-enabled feature "TrustTokens" is enabled, to include a new
experimental parameter `trustTokens` denoting a request to execute a
Trust Tokens protocol step (https://github.com/wicg/trust-token-api)
alongside the fetch at hand, by adding request headers and processing
corresponding response headers. This is an experimental interface
planned to be used in an origin trial.

This CL implements the network service side of the data flow, by
creating a Mojo struct representing the new Fetch parameter and adding a
member of this type to ResourceRequest. The second, concurrent, CL
(crrev.com/c/2036648) adds code to Blink to implement the JS binding
and pass the data from the binding to the network::ResourceRequest
field.

Notes:
- URLLoader will inspect requests' trust_token_params members and
destinations, using these to make a decision about whether to execute
Trust Tokens logic against the request.
- The Mojo struct is "flat" (no pointer members) in order to be
trivially copyable, since ResourceRequest requires this property of its
members.

serialization/deserialization of the mojom struct.

Test: Expands URLRequestMojomTraits unit tests to test
Bug: 1043118
Change-Id: Icc49ca2fe4a215330c8a9efdb36f4e050d41d05f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067803Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746043}

BUG=None
TEST=try

Change-Id: I167add5ffa3833387b0f246f6ffc497e80959209
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083050
Commit-Queue: Yury Khmel <khmel@chromium.org>
Auto-Submit: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746042}

SuperSize uses .map file only for native code analysis. However,
previously it requires .map file always, even if native code analysis
is skipped (via --java-only). This CL removes the restriction: So when
using SuperSize to diagnoise Java size changes, one no longer needs to
specify "generate_linker_map = true" in args.gn.

Change-Id: I9cd36c16d4efe45fcee2ae7e6cea88511fa2b56c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2082895Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746041}

Fix a few bugs related to back gesture:
- If we have a top active window that can perform back before entering
tablet mode, then when entering tablet mode, we should show the nudge
above the window.
- Fix an issue that if switching to an existing tab that can perform go
back operation, the nudge does not show up. We should trigger the
navigation status change when active tab changes.
- Also fix a crash happens when shutting down chrome when nudge is in
animation.
- Also use DidFinishNavigation() instead of NavigationEntryCommitted()
to inform observers when a navigation happens inside of the current
active webcontent.

Bug: 1009005b
Change-Id: I3caf166e6681cad7b3d9b88fa9fe32f2482f62bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2081518Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746040}

As part of frienly settings, we have added a new feature to display the
sWAA state in |chrome://settings/syncSetup|. The goal is to record if
the user clickes on the external link to open Activity controls page to
control their sWAA state.

Bug: 1050070
Change-Id: Ic2ab6955e4004acbef1187964a8289e5da8ada00
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066749Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Monica Basta <msalama@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746039}

This reverts commit 54ff0ea1.

Original patch created a problem around properly switching themes,
because of timing of switching observer to a new tab (previously
available with a hint only.

Bug: 1056586, 1054072
Change-Id: Iec9267e6eadd87725bf4609117b8d4d31a2fd24e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080692
Commit-Queue: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746038}

Bug: 1007815
Change-Id: I6b234a1e341f77b9d9a366d7931bcb6a76c3a41d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2082558Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Anna Malova <amalova@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746037}

Add tests to check whether the infobar is shown for different errors. This
cl also registers SyncErrorInfoBar as a ProfileSyncService state change
observer to ensure that the infobar is dismissed as soon as the user resolves
the issue from settings.

Render tests will be added in a subsequent cl.

Bug: 1031632
Change-Id: Ifb6b64e187ddce6129a43b0a7be1d76d8ff26ace
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033244Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Commit-Queue: Tanmoy Mollik <triploblastic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746036}

This patch updates some usage of |BluetoothDiscoverySession::Stop|
in BluetoothBlueZTest to just destroy the session and removes some
tests that are irrelevant after we get rid of the callbacks for
|BluetoothDiscoverySession:Stop| params

Bug: 991682
Change-Id: Id90d60790e4bb8654eca49d4f98fe5ce09fd646e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076422Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Commit-Queue: Phillis Tang <phillis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746035}

Adds a simple Media Feeds service and feature
flag so we can start working on the feature.

BUG=1056766

Change-Id: I74fe15de8ea6e3ee1c73dbb1ebe467ae9f195144
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079265Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Tommi <tommi@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746034}

Bug: 1007815
Change-Id: If81fbff53dd3d6dd1256e83b0c537d59a38aca8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083321Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Anna Malova <amalova@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746033}

Bug: 1007815
Change-Id: I0ff57980ab4420b8a3b8619dba3e4a3113159498
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080259Reviewed-by: Asanka Herath <asanka@chromium.org>
Commit-Queue: Anna Malova <amalova@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746032}

Callback is used multiple times to match URLs.

Bug: 1007815
Change-Id: I828043de1cff402912b34b168b18106aff3012fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083173Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Anna Malova <amalova@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746031}