GitLab

This records RTC event logs for the duration of each session. This data
is kept in a memory buffer, and limited in size to avoid the buffer
growing indefinitely.

Followup CLs will add the ability to send the recorded log to the
client.

Bug: 1122798
Change-Id: If32a1ea65d93a53ee5cf6e74cd7dbea151fb1214
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380961
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804397}

Since webview_power_usage.sql now calculates power usage distribution by
core type, this change updates the corresponding tbmv3 metric
to output these values.

Bug: b/159154263
Change-Id: I1e1d3cbfe5843bdb61191d2356f40ef019532931
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378810Reviewed-by: Mikhail Khokhlov <khokhlov@google.com>
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804396}

Updates the requirements for changing the layout axis to display on
a vertical axis when the user turns on "Larger Accessibility Sizes".

Bug: 1110243
Change-Id: Ib4eb3c915298a8cae3606e41c0ea63a2ff1ae062
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390913Reviewed-by: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Commit-Queue: Nohemi Fernandez <fernandex@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804395}

https://chromium.googlesource.com/angle/angle.git/+log/999c85ee8215..b6b9cffaf3bc

2020-09-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll VK-GL-CTS from 3b3f93c206dc to 5e85f689b911 (7 revisions)

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 cwallez@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/+doc/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;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: None
Tbr: cwallez@google.com
Change-Id: Id5d1caf70b3edcac1e94f4ad1f190a48a7b6d72d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392729Reviewed-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@{#804394}

Roll Chrome Mac PGO profile from chrome-mac-master-1599112620-f359a51daebae2f754df062494b1fdebe13ff3bd.profdata to chrome-mac-master-1599155892-629b4d0dfe6acef6eef58d4607669a58bfb33fb6.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium
Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: chrome/try:mac-chrome
Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com
Change-Id: I85b0d9d806d533f9cc2a704d9995b14011ef0051
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393037Reviewed-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@{#804393}

https://skia.googlesource.com/skia.git/+log/f8823b572600..00b2fdbc3c6f

2020-09-03 herb@google.com move blur and path attributes to key
2020-09-03 robertphillips@google.com Revert "Create cpu-side blurred RRect mask when recording DDLs"
2020-09-03 robertphillips@google.com Create cpu-side blurred RRect mask when recording DDLs
2020-09-03 johnstiles@google.com Add is<T> to IRNode types.
2020-09-03 johnstiles@google.com Use erase-remove idiom for dead-declaration removal.
2020-09-03 kjlubick@google.com [infra] remove SkottieWASM CPU job
2020-09-03 kjlubick@google.com [canvaskit] Add drawRect4f as example 'fast path' API

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC michaelludwig@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Cq-Do-Not-Cancel-Tryjobs: true
Bug: chromium:1108408
Tbr: michaelludwig@google.com
Change-Id: I0efe05c9cdb3401e5e1fb7eb3ad8a2e413e01ed7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392728Reviewed-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@{#804392}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2e32d90fa6b3..c81f39950ebf

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC btolsch@google.com,nicolaso@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: chromium:1093353,chromium:1099917
Tbr: btolsch@google.com,nicolaso@google.com
Change-Id: I7193727c0adf01659ac7dd9ca79197bd1b5e682b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392727Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#804391}

Bug: 1049826
Change-Id: I35a51c669e413c4b1cdf0b756239b3b3e0066ea1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391422Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: My Nguyen <myy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804390}

This addresses the linked bug where the search provider logo would
sometimes disappear on the Android NTP under certain conditions
(device rotated while the logo is scrolled off-screen). A lot more
context on the bug is in this thread (googlers only, sorry):
https://groups.google.com/a/google.com/g/clank-dev/c/IWxWjz6qc90

One of the posts in that thread suggested changing the width of the logo
in the XML, and since doing so I have not been able to repro the bug, so
I believe this should fix the blocking issue.

Bug: 1122928
Change-Id: Id4503fa5a1131a83a43b7dbb083e7253f7e8138d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392751Reviewed-by: Tommy Martino <tmartino@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Tommy Martino <tmartino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804389}

This CL add an new API to CustomViewBinder#getPixelHeight which allow
each custom view can return their height individually. The height is
based on the layout file related to the custom view.

This CL also add padding before and after the divider line, and render
test for it.

Bug:1114611

Change-Id: I5e104dd5cdcdcf4acf20beeab6a682b4d4bba152
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2387542
Commit-Queue: Gang Wu <gangwu@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Sinan Sahin <sinansahin@google.com>
Cr-Commit-Position: refs/heads/master@{#804388}

When auditing dependencies, a fundamental information is in which build
target the outbound or inbound dependency is.

Change-Id: I55513f18b76e6bad01d7a2f68aad5e56b256d49c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391651
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Reviewed-by: Mohamed Heikal <mheikal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804387}

SkiaOutputDeviceGL can sometimes look in the wrong place for a texture.
It is using a deprecated system (MailboxManager) to find a texture based
on a mailbox (which is just an opaque id), because existing Windows
video overlay code still used the old GL texture system so the mapping
is stored there.

This CL adds code to look in the new shared images system to lookup a
texture from a mailbox and it will be required when upcoming changes in
"Zero-Copy Camera Capture Optimizations on Windows" [1] lands to ensure
that Skia rendering also works with these new changes. The upcoming code
uses the new system, so the mapping is stored there.

Note that, the changes in this CL will not have any effect until the
work in [1] lands in Chrome.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1120900

Bug: 1120900
Change-Id: I09b5f0b06ff7539a9448a5b28bbfef89b3666331
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391236Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Henrik Andreasson <henrika@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804386}

This should not change deep scanning behaviour with Connectors.

Bug: 1103390
Change-Id: If7562ef39a94680397b6dc48ee9cf7c41cf86988
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2388202
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804385}

The extension installation process reports times at various stages
in the process. Till now, we are just checking if an entry for the
time is getting recorded in the histogram. This CL additionally
verifies that the time recorded in the histogram is as expected.

Bug: b:162855564
Change-Id: I5c2d7e5c9b93df98c9e899d13e779adafc84563d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391145
Commit-Queue: Saurabh Nijhara <snijhara@google.com>
Reviewed-by: Swapnil Gupta <swapnilgupta@google.com>
Cr-Commit-Position: refs/heads/master@{#804384}

Currently the execvp fails for a launch process it does not give
much diagnosis. This change reports the errno reason why the execvp
failed. This has been useful in finding simple naming errors.

Change-Id: Ifcc33c87931535019d8509234818c9d995fa4b9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383292
Commit-Queue: Peter McNeeley <petermcneeley@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804383}

This is a mechanical conversion from the original HTML page to markdown
doc with few typo fixes, link fix and reformatting.

See http://go/clank/engineering/android-webview/java-bridge for the
original doc.

Fix: 948816
Test: Upload to gerrit > open file > click "gitiles"
Change-Id: I503c964bc6445ce26b8d9aea3cfd03bf77667c73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391771
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804382}

Pseudo element was renamed. Use the same crbug issue and reintroduce the
expectation line in the same place it was removed from.

Bug: 1086855
Change-Id: Ib9a258d8f2a494bdfc791d406a1f3eed5073e505
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390915
Auto-Submit: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804381}

Bug: 1120109
Change-Id: Icbe6f8f000d4ff1db68445ffdabf931a6ce19aa9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368136Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804380}

This CL changes NOTREACHED() to LOG(FATAL) in context lost handling on
RenderThread. WebView currently will intentionally crash in
HardwareRendererViz::OnViz::DisplayOutputSurfaceLost, but it happens on
viz thread later and has no useful information.

Bug: 1112841
Change-Id: I2548c06c32897d586e9d51d143d1dbd2f3fdfc6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392411Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804379}

Prior to https://crrev.com/802829, PDFExtensionClipboardTest used
polling to detect clipboard changes. As such, test cases took the
following steps and there was no alternative:

A1) Fire asynchronous input event.
A2) Poll the clipboard repeatedly for changes.

This has an inherently race risk, as (A1) can potentially finish before
(A2) starts. With the straight-forward ClipboardMonitor replacement in
https://crrev.com/802829, the test cases do less work by not polling,
but the race risk remains:

B1) Fire asynchronous input event.
B2) Start monitoring for clipboard changes.
B3) Wait until the clipboard changes.

Since the tests are no longer polling, it is now possible to improve
reliability by reordering the steps:

C1) Start monitoring for clipboard changes.
C2) Fire asynchronous input event.
C3) Wait until the clipboard changes.

To do this, change CheckClipboard() and CheckSelectionClipboard() to
take an additional base::OnceClosure for the input event action. Then
run the closure at the appropriate time.

Also update remaining comments that still mention polling.

Bug: 1121446
Change-Id: I2a29ef1ef3b08cf7567318d098f5b527ec9f53bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391582
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: K. Moon <kmoon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804378}

On the official WPT test runner, we can't test reporting at all.
See https://crbug.com/1121605

The "Report-To" header isn't parsed at all, due to an SSL certificate
error.
We are already using "--ignore-certificate-errors", but apparently this
isn't enough, we also need: "--ignore-certificate-errors-spki-list=XXXX"

Where XXX can be generated with:
```
openssl x509 -noout -pubkey -in ./tools/certs/web-platform.test.pem |
openssl pkey -pubin -outform der |
openssl dgst -sha256 -binary |
base64
```

This is adapted from the internal chrome test runner:
third_party/blink/tools/blinkpy/web_tests/port/base.py
(Search for WPT_FINGERPRINT)

Along the way, I found this issue:
https://github.com/web-platform-tests/wpt/issues/24180
which I think might also be fixed by this patch.

BUG=1121605

Change-Id: Ia6e98a5050c8d2513d605a45cd349a52314282cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390748
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804377}

This test is flaky on Win7 x86 32-bit bots.

TBR=nicolaso@chromium.org

Bug: 1124845
Change-Id: I26fc5b231a6aed0af4e5bd3c9e3eb7bfbdf0ba56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392936Reviewed-by: Brandon Tolsch <btolsch@chromium.org>
Commit-Queue: Brandon Tolsch <btolsch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804376}

Change-Id: I7b08012c8e0640a3a1c92fc6e9713f7a5be5cac8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380311Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Megan Jablonski <megjablon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804375}

Measures basic metrics for the fontconfig implementation.

Bug: 1043306
Change-Id: I2499ca9419735f5b2fb739578b6f7f54355e2d02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391516
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Auto-Submit: Olivier Yiptong <oyiptong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804374}

https://804113 changed the test to be parameterized, but forgot to
instantiate it. Fix this so the test actually runs.

Bug: 1120279
Change-Id: I7291a1e7e9c857f2295fa0bb23fb1e2995b2f4db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391334Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804373}

Bug: 1124781,1124757
Change-Id: I36aa26810557cbc876ccf68e1fb458d9a18c00fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392796Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Auto-Submit: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804372}

This patch is a small clean-up to LayoutReplaced logic which is
overly complicated in light of the fact that intrinsic sizing override
can only take place under size containment.

Also removes an obsolete comment.

R=cbiesinger@chromium.org, ikilpatrick@chromium.org

Bug: 1124771
Change-Id: I22c07b01146ee11e8e7adc8c877d90b161a107f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392741
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804371}

This CL introduces FileURLLoaderFactory::Create static method that
allows creating a FileURLLoaderFactory that is owned by its |receivers_|
and will self-delete when the last receiver disconnects.

This CL removes the ability to directly construct and own a
std::unique_ptr<FileURLLoaderFactory>, because this ability means that
the factory can be destructed while receivers bound via the Clone method
are still alive (see the associated bug).  In particular, this CL 1)
stops exposing FileURLLoaderFactory constructor as a public member and
2) stops returning a std::unique_ptr from the
CreateFileURLLoaderFactory public //content API.

AwContentBrowserClient::RegisterNonNetworkSubresourceURLLoaderFactories
needs to be able to provide a FileURLLoaderFactory when
|aw_settings->GetAllowFileAccess()|.  This necessitates tweaking the
ContentBrowserClient::RegisterNonNetworkSubresourceURLLoaderFactories
method to ask for both NonNetworkURLLoaderFactoryDeprecatedMap
(factories to be owned by the caller) and a new
NonNetworkURLLoaderFactoryMap (receivers-owned factories).  The former
parameter type should be eventually deprecated and removed everywhere.

Bug: 1106995
Change-Id: Id710f611c60942d932fd1dc71f7e313f227f5424
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2337411
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804370}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/ed9c15fc40f4..436d8ac8c54e

2020-09-03 patrick.brosset@microsoft.com Don't make NodeText a block element to apply ellipsis in Layout panel
2020-09-03 kprokopenko@google.com Add sources panel link e2e test for Issues tab

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/+doc/master/autoroll/README.md

Bug: chromium:1124250,chromium:1124712
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: Iea9f3b4edd62941c1c6b45b47320e933599a529c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392726Reviewed-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@{#804369}

Bug: webrtc:7660
Change-Id: I6089f8670f46591963de6f2716bcf9d1ba653c3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2387018
Commit-Queue: Gary Kacmarcik <garykac@chromium.org>
Auto-Submit: Niels Möller <nisse@chromium.org>
Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804368}

https://android.googlesource.com/platform/external/perfetto.git/+log/c4bfa82e48ed..5383c636752f

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-trace-processor-mac-chromium
Please CC perfetto-bugs@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/+doc/master/autoroll/README.md

Tbr: perfetto-bugs@google.com
Change-Id: Ic56d8fce55c38e1a0fa5980675a2222080ebb8e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390858Reviewed-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@{#804367}

Removing mojolpm.proto copy. Moving generated C++
into fully qualified location.

Change-Id: I27e9a22002506862780258294c4688e5935516d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2388440
Commit-Queue: Clovis PJ <clovispj@google.com>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804366}

cc and viz pixel tests each have constants for which renderer type to
use. Combine them and move them into the viz namespace.

Both test suites also add some GN defines to determine which renderer
backends are available for this configuration. Combine them and convert
to buildflags.

Bug: 1047820
Change-Id: I3226f75feb5e34c205a30b989c545a3aaeb6f283
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390941Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804365}

Diagnosis for crbug.com/1123083:
It crashed when UIsManager tried to access CPRImpl#mClient which is
null after CPRImpl has closed. Since CPRImpl is not supposed to be
used after closed, UIsManager should not use PaymentUIsObserver
(implemented by CPRImpl) after CPRImpl is closed. However, the original
didn't allow CPRImpl to inform UIsManager of CPRImpl's closing, nor
should it because UIsManager is responsible for PaymentUIsObserver not
CPRImpl.

Change:
UIsManager no longer accesses CPRImpl directly. Instead, PRImpl is
used as middle man to handle it. The reason is that since CPRImpl,
PRImpl, UIsManager are structured in layers (low to high), CPRImpl
and UIsManager should not be aware of each other.

Acronyms:
CPRImpl = ComponentPaymentRequestImpl
UIsManager = PaymentUIsManager

Bug: 1123083

Change-Id: Iaafd1827691031c55f30731f1ac7f6bec8ddbe9e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392757Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804364}

This is in preparation for launch. Metrics report:
https://docs.google.com/document/d/1QmvnzeFeFOHx4Bk0MwQCJ261sYSqgrrFFUQUQB4ecUI/edit

Bug: 964049
Change-Id: I5c97ca2dd4c5f00a9340c64261e33fd8213d6b6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391644Reviewed-by: Stepan Khapugin <stkhapugin@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804363}

This policy controls the ability of cross-site images to trigger auth
prompts when a page is loaded. The policy applies only to images, and
applies to all HTTP authentication types (Basic/Digest/NTLM/Negotiate).
This CL updates the policy description for accuracy.

Bug: 1124044
Change-Id: I82f53e5ca644d39506f94e91a2a0442a5682069a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390857Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Eric Lawrence [MSFT] <ericlaw@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#804362}

This CL moves some abort-related PageLoad metrics to be recorded on
ReportAbortMetrics() instead of RecordPageLoadMetrics() because the latter is
called the first time the page becomes hidden, or never if it starts hidden.
Since we use these metrics as filters for our abort metric and our definition
does not exclude pages that start hidden (it only excludes pages that are never
foregrounded), we move these metrics to ReportAbortMetrics() so that we can
reliably use them. The metrics moved are:

* Navigation.PageTransition
* Navigation.PageEndReason2
* Experimental.Navigation.UserInitiated

Bug: 1123972
Change-Id: I7bef04f7d44644b6966595518118633027625562
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390460
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804361}

This test is already flaky and now also times out. Importer tries to add
the timeout as a separate line instead of combining it with the existing
line, which causes a lint error.

TBR=smcgruer

Change-Id: I0046597b917746e5ec8e7110025f1507adf74582
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391205Reviewed-by: Luke Z <lpz@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804360}

These tests were disabled for flakiness. They passed 3000
iterations on the bots without flaking. One test fails
consistently on the LaCrOS bot and is disabled for that
build configuration.

Bug: 69215, 108493
Change-Id: Ie93c5949520c39c7b1ec8439f442722795535fd2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376463
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804359}

We've decided to abandon system modality on non-ChromeOS platforms, so
always use window modality for this dialog instead. Some minor cleanups
of DownloadInProgressDialogView are included in this change.

Bug: 1121132
Change-Id: Ia1e5efaa63a38a0f97608253ee688b08b8a86a8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377989Reviewed-by: Dana Fried <dfried@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804358}