GitLab

These events indicate that network activity indicator has started or
stopped spinning. These logs are not very useful, but take space.

Bug: 1046231
Change-Id: Ifef0cc43fc0ce8cf84299265482e5ab2004b38ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029328
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Auto-Submit: Eugene But <eugenebut@chromium.org>
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736997}

This will encrypt / decrypt messages sent via WebRTC with Web Push
encryption. SenderID is preferred with a fallback to vapid. We only
support sending via FCMChannelConfiguration (remote device will receive
the message via FCM) and not ServerChannelConfiguration (remote is a
server endpoint). This means Sharing messages via WebRTC need to be
initiated via Chrome and not server side.

Bug: 1045406
Change-Id: Ida249ca1cdd44a4552d85700c857c8288d598ec4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011925
Commit-Queue: Richard Knoll <knollr@chromium.org>
Reviewed-by: Alex Chau <alexchau@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736996}

The DevTools Performance Timeline tool with 'Advanced paint instrumentation' enabled captures layer trace events, which includes compositing reasons. This change adds compositing_reason_ids to the trace information, so that we can localize the compositing reasons in the client (i.e. DevTools frontend).

Bug: 946860
Change-Id: Ibb9b655c739947898b857489d5f8d727a40ef19b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031528Reviewed-by: Mandy Chen <mandy.chen@microsoft.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Lorne Mitchell <lomitch@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#736995}

The new MIME types are
* application/pdf
* The types listed in firefox.desktop

R=thestig

Fixes: 1046912
Change-Id: I23e314694a08677f13cee8c1399ae68b58f1aab7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031865
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736994}

Change-Id: Id268acba620b57196e06cc1160d95a7d2b036a17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028861Reviewed-by: Darwin Huang <huangdarwin@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736993}

Bug: 1011441
Change-Id: I990c53761f39003a9dfea21274c61e881dcb00ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031304Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736992}

These are the shell-specific changes from
019a8580 with some
adjustments to make sure the viewpoint doesn't change size
(as changing the viewport size affected perf test outcomes).

Bug: 1038415, 1045609
Change-Id: I1c74c1326a5541de23eb1d1c1a2f383b26466ae6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025875Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736991}

This is a precursor CL for https://crrev.com/c/1992341 which creates
the TabContentManager pre-native, and splits its creation into
creation + post-native initialization.

In this CL, we refactor TabContentManager::getTabThumbnailWithCallback
to use a tab ID instead of Tab which can't be created in pre-native.

Bug: 1041865
Change-Id: I8a0c82e40b5e0f05974a66bceb7cc96d2e4bcf5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003433Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736990}

This CL disables
PictureInPictureWindowControllerBrowserTest.SurfaceIdChangeDoesNotMoveWindow
due to flakiness.

TBR=odejesush@chromium.org
NOTRY=true

Bug: 1002489
Change-Id: Ia0da98a68c4d9e669cff36ab7a55bee220da66ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031598Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736989}

jacoco (Java code coverage tool) requires turning off strict mode
since it writes the coverage data to files.

AwStrictModeTest enables strict mode and therefore it currently
causes strict mode violation (in a flaky way).

Unfortunately, we are disabling this in one of the main tryservers
(android-marshmallow-arm64-rel) which enables jacoco, but
android-pie-arm64-rel in CQ and 5 other bots run this
continuously, and such violations will be locally reproducible.

        test can be run, check tryserver result

Bug: 1021403, 1045270
Tested: change use_jacoco_coverage value in build gn and see if
Change-Id: I95b41f82906f6d7f0ec32a353203928f831079a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029327Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736988}

Bug: 1045114
Change-Id: Ifd1a1cac094daab05e2d2330d393c3bdfc0d75b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020425Reviewed-by: Victor Costan <pwnall@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736987}

Using wpt-import in Chromium da66c880.
With Chromium commits locally applied on WPT:
9f06cfff "ConvolverNode channel count and mode can be changed"


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:
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools

NOAUTOREVERT=true
TBR=robertma

No-Export: true
Change-Id: Id3f84583fa727ec08ee057c0451a4f42e53d780e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031085Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#736986}

Some of the tests started flakily timing out in December, with no change
in the SimpleURLLoader code.  Given that Chrome still seems to be
working and updating, and there's no obvious problem in the wait loop
of the code, my guess is the tests are just running slower than they
used to.  This CL is an attempt to test that theory.

Bug: 1035127, 1046745
Change-Id: I46bec60e001a21afd76ea66b92f864f8ffbddece
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031544Reviewed-by: Maksim Orlovich <morlovich@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736985}

This reverts commit 9d43bcbd.

Reason for revert: I pressed the wrong button; CL is not ready.

Original change's description:
> [DevUI DFM] Fix crash-on-install caused by stale navigation states.
> 
> Previously, if a failed DevUI DFM install attempt (leading to the error
> page) is followed by a successful install, then the following problems
> arise:
> (A) chrome.send() is unavailable for the loaded DevUI page.
> (B) Addition refreshes trigger CHECK() and crashes browser.
> It seems that between showing the error page and showing the DevUI page
> (after successful install), some stale state persisted so that the
> active instance of NavigationRequest has bindings() holding a value
> without BINDINGS_POLICY_WEB_UI, so that chrome.send() would not load,
> leading to (A). Then (B) is triggered as an after effect.
> 
> This CL is a work-around for the bug for the DevUI DFM. On initial
> DevUI DFM install, instead of resuming navigation to the intended
> DevUI page, we visit a small shim page that self-refreshes, so that
> stale states are cleared.
> 
> This is not a full fix, since state staleness problem (and crash on
> refresh) still exists for error pages (in history or other tabs) other
> than the one that successfully triggers DevUI DFM install.
> 
> Bug: 1046159
> Change-Id: I775491ee165e7d2a809d93d334f93ae4bbf72cb6
> Fixed: 1046159
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028363
> Commit-Queue: Samuel Huang <huangs@chromium.org>
> Reviewed-by: Andrew Grieve <agrieve@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#736836}

TBR=creis@chromium.org,huangs@chromium.org,agrieve@chromium.org

Change-Id: I7ff5e5fd7f86ac189bafc4b45ad4e4ade5c61410
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1046159
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031536Reviewed-by: Samuel Huang <huangs@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736984}

https://chromium.googlesource.com/external/github.com/google/shaderc/+log/9f95ca93ba65..6d9f753c1d15

git log 9f95ca93ba65..6d9f753c1d15 --date=short --first-parent --format='%ad %ae %s'
2020-01-30 rharrison@google.com Add documentation for Vulkan 1.2 and SPIR-V 1.5 (#980)

Created with:
  gclient setdep -r src/third_party/shaderc/src@6d9f753c1d15

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/shaderc-chromium-autoroll
Please CC radial-bots+chrome-roll@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: radial-bots+chrome-roll@google.com
Change-Id: I5b89d459edbc7dfa4d52093f9fd6ef12105905ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031628Reviewed-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@{#736983}

This way, the cq makes sure that we run all the bots we want to run
(as long as we use the upload script), which is less error-prone.

This doesn't work for internal chrome/try bots yet, so these stay on
the old system for now.

Bug: 1047347
Change-Id: Iedecf56d4cfa5f6e923b716b927147ac3c28dedc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016844
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736982}

Bug: 1044139
Change-Id: Ia5e9514d197799631d60cfc1c420a7c2436cc451
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029237
Commit-Queue: Ian Wells <iwells@chromium.org>
Reviewed-by: Dan H <harringtond@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736981}

Ran into this issue when trying to write a tast-test. The main way is
to press the home button which we can use an accelerator for, but its
still helpful for tests to do this, and you can still you minimize and
fullscreen accelerators in tablet mode with a keyboard.

Added a test and formatted the file.

Test: added test, manual
Bug: 1045185
Change-Id: Iead7516d133929b93452bf4f29e24e462e728a8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025967
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Mitsuru Oshima (slow in TOK) <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736980}

AR Module I2S:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/BXxS2U5EaN0

Hit Test Module I2S:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/QyIz793UdGs

This CL also moves the legacy (promise-based) hit test API to be gated
by WebXRIncubations flag.

Fixed: 1047050
Change-Id: I1d522323c4cbf8656e59ff949e600f955768841c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026627Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736979}

The DCHECK on prediction metrics is to assert predicted event is later
than the real event. However, because we are using frame_time - 5ms as
the predicted time, it is possible that the predicted event is actually
prior to the first real event when the input frequency is high.
It's not likely to happen in real device as the input frequency is
120Hz, but it may happen on emulator.
Therefore, we should return instead of DCHECK this case.

Bug: 1040654
Change-Id: I61990cea0f7e7f7679e7f5b28db22b37a78865ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031550Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736978}

We were already making this assumption a few places.

Change-Id: I0f39a9f98f47196211f996e00adaead883c45cc2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028771Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736977}

Partially reverted CL:2002917

Fixed: 1047215
Change-Id: I4627b5753711abecc3443944aeb83d1c38c8f2f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030947Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736976}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0b3f3f156be2..b2f79dd4c2c7


Created with:
  gclient setdep -r src-internal@b2f79dd4c2c7

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 jbudorick@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.chrome.try:linux-chromeos-chrome
Bug: chromium:1041820
Tbr: jbudorick@google.com
Change-Id: Ie07e0a507361be9f21d844c6c3442cea870b5d6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031605Reviewed-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@{#736975}

https://webrtc.googlesource.com/src.git/+log/c31a4ec66af2..670af2692e5d

git log c31a4ec66af2..670af2692e5d --date=short --first-parent --format='%ad %ae %s'
2020-01-30 danilchap@webrtc.org in RtpSenderVideo add support for writing DependencyDescriptor header extension
2020-01-30 danilchap@webrtc.org Add extra input validation to RtpFrameReferenceFinder for codec-specific cases

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

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: chromium:1046995,chromium:1047024,chromium:1047095,chromium:1047165,chromium:1047190
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: Ie6c340af20b9d7e02069e5373d7a03f360e5012c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031604Reviewed-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@{#736974}

Rebaseline fast/css/css2-system-color-expected.html with updated rgb
color values for MacOS 10.14. Rebaseline several other tests by
explicitly specifying text colors.

Bug: 1046986, 1028242
Change-Id: I815469a852d5c0808bc7df6d9876c29941bdf714
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029998Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736973}

Several changes in realtimeapi.proto are made in this CL:

1. The old cache_expression field is renamed to
cache_expression_covering_match, this is to avoid breaking
old clients that are using this field.

2. Add a new enum named cache_expression_match_type,
if this field is not set, ignore this entry; if this field
is set to EXACT_MATCH, this entry is applicable for exact
url matching; if this field is set to COVERING_MATCH, this
entry is applicable for host-suffix path-prefix matching.

3. Add a new cache_expression field, this field will be
used as the cache expression for new clients.

For details, see go/chrome-protego-cache-matching-field.
Server-side change: http://cl/292004484

Bug: 1041675
Change-Id: I5a40babdb9be0ebad8661361a93194daa445f479
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008080Reviewed-by: Varun Khaneja <vakh@chromium.org>
Commit-Queue: Xinghui Lu <xinghuilu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736972}

Bug: 884928
Change-Id: I3692c3d9093d67572336c6d6270ff3370bc2683e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994274
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Reviewed-by: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736971}

https://chromium.googlesource.com/angle/angle.git/+log/ee07cb317579..d9884d3e7123

git log ee07cb317579..d9884d3e7123 --date=short --first-parent --format='%ad %ae %s'
2020-01-30 jmadill@chromium.org Vulkan: Don't dirty index/vertex buffers on each syncState.

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

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 tobine@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: tobine@google.com
Change-Id: I9b52c29cc57f9983207a4508da2fe47259d877ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031444Reviewed-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@{#736970}

It watches the Profile create/delete event to create ExtensionRequestObserver
for each Profile.

Bug: 1006899
Change-Id: I19a89427a957813d41f843b4e92256bfff0d1edd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028456
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736969}

This change involves two semantic differences:
1. stable-gitiles-trigger is a poller rather than a scheduled trigger
because it's not possible to generate a scheduled trigger using
lucicfg. With the upcoming branch, this is a change that would need to
be made soon regardless.
2. The notifiers for builders that are scheduled by a trigger now
populate the repository field.

Bug: 1011908
Change-Id: I217089efba52bd6ec92b291f2141a6e36e1477d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031189
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Aaron Gable <agable@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736968}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/096422a54f2c..e702867eed40

git log 096422a54f2c..e702867eed40 --date=short --first-parent --format='%ad %ae %s'
2020-01-30 brgoddar@microsoft.com Update PRESUBMIT.py to print current check running

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

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: None
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I80d15700e0d05ec67f1334cbcda1fe5de54a6321
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031624Reviewed-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@{#736967}

https://pdfium.googlesource.com/pdfium.git/+log/1ac8524b6984..65137d177ac2

git log 1ac8524b6984..65137d177ac2 --date=short --first-parent --format='%ad %ae %s'
2020-01-30 thestig@chromium.org Avoid an integer overflow in OpenJPEG.
2020-01-30 tsepez@chromium.org Comment two POD structs with raw c strings.
2020-01-30 tsepez@chromium.org Avoid raw c-style strings in CPDF_FormField.

Created with:
  gclient setdep -r src/third_party/pdfium@65137d177ac2

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

Bug: chromium:1047097
Tbr: pdfium-deps-rolls@chromium.org
Change-Id: I7a43f0568b471ef9866fc6302db3f81c95c49f51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031626Reviewed-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@{#736966}

The video-frame-size-change.html is flaky because it sometimes finishes
before the pixels have rendered on screen. There are two reasons for
this:
1) We only wait on the second video to finish seeking to end the test.
2) Seeking doesn't guarantee that the frames will be painted on screen.

This CL fixes the issue by waiting for both videos to render on screen,
by using video.rAF calls to end the test as soon as both videos have
painted their frames.

Bug: 993671
Change-Id: I236777bf3fa83fc57e9e4e80560703965602d40c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025581
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Auto-Submit: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736965}

We could have off screen damages that is currently counted as
frame expected. For example, there is a main thread animation outside
of the current viewport, then for each begin main-frame, we
neither report is "no-damage", nor report "submit-frame". In
this case, we treat that main-frame as it caused no damage.

Bug: 1021963
Change-Id: I3d9c37e625b78d6cf275208d77676ffe17b47611
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1987603Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736964}

This flips the feature that enables admins to configure default Crostini
container via user cloud external policy to enabled by default.

Bug: 1000287
Change-Id: I6bec81f759374ff9edad6207e2c2ae70d42b0a23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031031Reviewed-by: Igor <igorcov@chromium.org>
Commit-Queue: Olya Kalitova <okalitova@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736963}

No longer tuning this code, UMA not needed.

Bug: 859757
Change-Id: I6756922422883b8369d2aa63b1ee4f0d2a94f94b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029234
Auto-Submit: Eric Karl <ericrk@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736962}

These were all expired after M77, adding <obsolete> tag and cleaning up
code.

Bug: 691863
Change-Id: Ibf654b78aad2b6bbbf85b2527f55dfe1d51c9f35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029289Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736961}

Bug: 1007802
Test: Modified browser_test passes
Change-Id: I7847afc1c4989e31ebbd46482be1e14765faed13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028929
Commit-Queue: John Rummell <jrummell@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736960}

OptimizationGuideDecider API.

Bug: 1030813
Change-Id: I2d0e73e22ec52f1c09e218e50fe11cd737525d48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029228Reviewed-by: Megan Jablonski <megjablon@chromium.org>
Reviewed-by: Robert Ogden <robertogden@chromium.org>
Commit-Queue: Josh Simmons <jds@google.com>
Cr-Commit-Position: refs/heads/master@{#736959}

R=crouleau@chromium.org, tmrts@chromium.org, ulan@chromium.org

Bug: chromium:1044682
Change-Id: I4c2c564ba47d6822ebe911562ff2488ef2bc32e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016347
Commit-Queue: Will Spaetzel <spaetzel@google.com>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736958}