GitLab

This CL ensures we update the visibility of the CustomTabBar when tabbed
PWA windows switch tabs.

Before: https://bugs.chromium.org/p/chromium/issues/attachment?aid=444139&signed_aid=nl_zCuHmhPys4eSWxjVDmQ==&inline=1
After: https://bugs.chromium.org/p/chromium/issues/attachment?aid=444368&signed_aid=6ab3-VByQm9JLc76qLpHDQ==&inline=1

Bug: 1076721
Change-Id: Ib4957e721e6c08f42df7297ddd397bac01e9f728
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2175696
Commit-Queue: Alan Cutter <alancutter@chromium.org>
Auto-Submit: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Joel Hockey <joelhockey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765421}

Remove console.logs I left in crrev/c/2174019 oops.

Change-Id: I85b95956b87a978229c9ed00c21cabd68eb1047d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181349
Auto-Submit: David Lei <dlei@google.com>
Commit-Queue: Trent Apted <tapted@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765420}

This change reduces the size of the isolates generated for builds
on all platforms by only generating minimal symbols useful for
generating stack traces.

What we lose are the following:

- Full fidelity for core dumps in perf builds.

- Full debug information when stepping through a perf build.

What we gain though is much smaller binaries to download and test with.

R=agable@chromium.org, johnchen@chromium.org

Bug: chromium:1076723
Change-Id: Idd5198fe2a7afb9121c76bc1583a824174b8e737
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2174105
Commit-Queue: Dean Berris <dberris@chromium.org>
Auto-Submit: Dean Berris <dberris@chromium.org>
Reviewed-by: Aaron Gable <agable@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765419}

https://skia.googlesource.com/skia.git/+log/6d2febd632a2..0ce0fd07a6df

git log 6d2febd632a2..0ce0fd07a6df --date=short --first-parent --format='%ad %ae %s'
2020-05-05 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 040e4f6fcf54..41f7bcce04a8 (14 commits)
2020-05-05 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader b798cfa374eb..c4bbd378e95b (1 commits)
2020-05-05 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 06a27cbe..abf0e59f (412 commits)
2020-05-05 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/dawn ccc40f6ffaa6..07328ba0bbce (6 commits)
2020-05-05 bsalomon@google.com Revert "Support large kernels on GPU in matrix convolution effect"

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

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 bsalomon@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-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
Bug: None
Tbr: bsalomon@google.com
Change-Id: I91a6f48aeb02f649da7f5909f4296f5fa7255a56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2182262Reviewed-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@{#765418}

It is unused anyway.

Bug: 860581
Change-Id: Ibe26101d7a08f7547b15c74ed98c4e400ab44661
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181350
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765417}

This CL Adds a new Location Provider that uses the Core Location
API to determine Location.

Bug: 1035290
Change-Id: I7cff4285ba10163b7fcc6657c1c8705872526606
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152105
Commit-Queue: James Hollyer <jameshollyer@chromium.org>
Reviewed-by: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765416}

The code uses std::bitset, but does not include header declaring it. It
works when using bundled copy of libcxx, but fails when using system
libstdc++ on Linux.

Change-Id: I8a88078e110b27623b3cdea38c94012ba4050ee7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2179123Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Piotr Tworek <ptworek@vewd.com>
Cr-Commit-Position: refs/heads/master@{#765415}

The former name was too generic for a method in the blink namespace.

Bug: 973801
Change-Id: Ic93d94773e42c9171884896af178689917062ef6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181580Reviewed-by: Asanka Herath <asanka@chromium.org>
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765414}

This introduces a describer that allows annotating FrameNodes with their
full internal state in the chrome://discards/graph view.

BUG=1077305

Change-Id: Ibad88a2a4c4961a445c02e96c8c186f63831fd81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2176285
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: dpapad <dpapad@chromium.org>
Reviewed-by: Joe Mason <joenotcharles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765413}

This CL moves TextInputClientMsg_FirstRectForCharacterRange to
LocalFrame and TextInputClientReplyMsg_GotFirstRectForRange to
TextInputHost.

Like [1], it adds GetFirstRectForRange to frame.mojom with
'is_mac' and replies with TextInputHost::GetFirstRectForRange
which runs on IO thread.

GetFirstRectForRange checks the caret bounds from the focused
plugin when it has ENABLE_PLUGINS. If it's disabled, it gets
the rect from the current frame selection.

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

Bug: 1007365
Change-Id: Idb4b3b77a1c660679b1e09a46497ffd5ac462917
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111254
Commit-Queue: Julie Kim <jkim@igalia.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765412}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/9e99f7c84e3d..f828cf36a3bf

git log 9e99f7c84e3d..f828cf36a3bf --date=short --first-parent --format='%ad %ae %s'
2020-05-05 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).

Created with:
  gclient setdep -r src/third_party/depot_tools@f828cf36a3bf

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC agable@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: None
Tbr: agable@chromium.org
Change-Id: I0b78797ecf73aa9c19c3092d7f91822dee9e6133
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2182087Reviewed-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@{#765411}

These calls were missed by the CQ because they are device-only. Fix
these calls by adding base::ios namespace and proper include.

TBR=sczs@chromium.org, eugenebut@chromium.org

Bug: 1078165, 1078140
Change-Id: Ib932e867b178809133b2e02ba439374a237022c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2182269Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765410}

ArrayBuffer has no size so files that were renamed had 0 bytes.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer

Also check the contents of the file in the RenameIPC test to prevent
this regression in the future. In doing so we update
FakeFileSystemHandle to be writable.

I don't think b/152832337 & b/152832025 are problems anymore with
this change and changes to loadFile in crrev/c/2174095.

Bug: b/155359417, b/152832337, b/152832025, 996088
Change-Id: I3ba74c5666d4b72f25fe23189fa2bd50f3d90e43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2174019
Commit-Queue: David Lei <dlei@google.com>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765409}

No change to logic. This extends a histogram because it's currently used
to track an API behavior change in Android R.

Fixed: 1077839
Test: None
Change-Id: I1cef1172d2b939ef46a107a8b57e638651bdfb5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2179931
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765408}

Remove redundant virtual test expectations because now we can fallback
to base expectations.

Add [ Pass ] for virtual tests that are expected to pass while the base
tests are expected to fail.

Add a lint rule to check for redundant virtual test expectations.

Bug: 1072015
Change-Id: I39ba834cd3a7af8124fe72c64f47b932c7800ad5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2178172
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765407}

Fix: OnWebAppInstalled must not be called on web app manifest update.

Test added.

This CL fixes the code which is disabled behind
kDesktopPWAsWithoutExtensions flag. No behavior change in ToT.

Bug: 860581
Change-Id: I06673f13b493f4f96aadce7ab8ba4457846210fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2172150
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765406}

According to the H264 specification (8.2.4.2.4, item 3),
initialization of the reference picture list for B slices in
fields,  the third list should contain long term frames.
Nonetheless, the current code appends short term refs. This patch
fixes it, adhering to the spec.

Change-Id: I224799bb7bc73ea314fb324219ee213813d2c102
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2166196
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765405}

https://android.googlesource.com/platform/external/perfetto.git/+log/c6e57b7fb88b..cd43ce1ed4ed

git log c6e57b7fb88b..cd43ce1ed4ed --date=short --first-parent --format='%ad %ae %s'
2020-05-05 treehugger-gerrit@google.com Merge "perfetto-ui: Fix update localTime bug"

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

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

Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel
Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: I5a1f99f3936bf85ca9feec2736c290f26f878ea7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2182077Reviewed-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@{#765404}

This prevents the special translations package from being added to APKs,
since it's not necessary there. In a follow up, I would like to add a
test that different languages work for both WebLayer and WebView as
bundles. It looks like that may be a bit complicated as there isn't a
way to install language splits in tests yet.

Bug: 1075704
Change-Id: Ifedd86818208320683a42b9d3218409d20d90891
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181199
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765403}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/509eb2aa10c8..01e605aad1f8

git log 509eb2aa10c8..01e605aad1f8 --date=short --first-parent --format='%ad %ae %s'
2020-05-05 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS.

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

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: I51d9224bd066a72a29a273a5152922e47a970478
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2182076Reviewed-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@{#765402}

Bug: 1066831
Change-Id: I81cd6edb71705e2372fffc144b95e6f36e6399b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2137321Reviewed-by: Yifan Luo <lyf@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Yifan Luo <lyf@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765401}

The rationale is the same as for crrev.com/c/2150527 "Move some
JSONParser tests to JSONReader tests".

Bug: 1069271
Change-Id: If66fbae083dff178f4e381ffaabb20e4710dce62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2175702Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Nigel Tao <nigeltao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765400}

The COSE Key structures in our unittests were not in the correct format.

Change-Id: Ib2a7a914beaf3fdb4cd851076c49eae969810f44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2177189
Commit-Queue: Adam Langley <agl@chromium.org>
Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Cr-Commit-Position: refs/heads/master@{#765399}

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

Previously after aZxHandleWatchController is finished or stopped it was
not possible to re-use for a new handle. That restriction is unnecassary.
This change updates the DCHECK to remove the restriction.

Also replaced mxio->fdio in two stale comments.

Bug: 1077837
Change-Id: I34af04abb9b5e9f6636cf90de40a80bf5d77f017
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2179766
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Auto-Submit: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765397}

Bug: 1000989
Change-Id: I6d15008bcee143dd926fe342cdf15a3d13fe290b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2176576
Commit-Queue: dpapad <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765396}

This functionality is now contained within the help app.

Bug: b/149634001
Change-Id: Ifed722f9b2e0fda2fe9295c0c18153e40aca86a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2169526
Commit-Queue: Rachel Carpenter <carpenterr@google.com>
Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765395}

Currently CdmService remotes are stored in a global static std::map that
is never cleared. This is fine since we only have one CDM |guid| used in
production so the size of the map should be at most one.

We plan to have multiple CDM processes (CdmService remotes), e.g. for
each origin. In that case, we should clear the CdmService remotes after
it's disconnected. Otherwise, the map size could keep growing.

Bug: 1077390
Change-Id: Ie294a8248c9e5ce05eb88c11022eb207fcbad464
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2177217Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765394}

This change should be safe as it should just make CrostiniRestarter
appear to be slower. In situations where we do not want restarters to
run any more (e.g. removing crostini), we have code to abort all
restarters so the "delay restart" behavior will not happen.

Notes
=====

Restarter shutdown observer registration
----------------------------------------
CrostiniRestarter now registers vm shutdown observer in Restart()
instead of the ctor. This is to correctly handle the case when there are
multiple restarters for the same vm: all restarters will wait for the vm
to shutdown without being terminated, and only the first restarter,
whose Restart() has been triggered, will kick off the restarting process
in OnVmShutdown().

This will cause a subtle behavior difference in a rare situation where
1) there are multiple restarters, 2) the first restarter is aborted just
before it gets OnVmShutdown(). The old behavior is that all restarters
will be terminated (because all of them get OnVmShutdown()), the new
behavior is other restarters will survive and one of them will be called
on Restart() by CrostiniManager::OnAbortRestartCrostini(). Note that if
the first restarter is not aborted, all restarters will still be
terminated by the FinishRestart() in OnVmShutdown() of the first
restarter.

CrostiniManager::OnStopVm()
---------------------------
CrostiniManager::OnStopVm() does not call OnVmStoppedCleanup() any more.
This is because when the VM is stopped, CrostiniManager::OnVmStopped()
will be invoked, and it already calls OnVmStoppedCleanup(). Removing
this avoids CrostiniRestarter::OnVmShutdown() to be called twice for the
same shutdown.

Bug: 1075731
Test: unit tests and manually testing (including removing linux with multiple delayed restarters)
Change-Id: Ic34e5333d544a2ff849079a085f342e669ed9523
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2172187Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Joel Hockey <joelhockey@chromium.org>
Reviewed-by: Nicholas Verne <nverne@chromium.org>
Commit-Queue: Jason Lin <lxj@google.com>
Cr-Commit-Position: refs/heads/master@{#765393}

Javascript and testing improvements.
Addressing hsuregan and khorimoto's comments on previous CL (see bug).

Fixed: 1077314
Change-Id: I007ab73e223f57f1ab1115fd5ecfc97aaf4db91e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2178555
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Regan Hsu <hsuregan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765392}

This log will show up whenever there is no file exists, causes noise in
logs in the bots.

BUG=853604

Change-Id: I0c9905d5f460c3b36bc1b62b2198ca890c1428ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181692Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Maggie Cai <mxcai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765391}

- deleted .style.yapf files in subdirs
- added root .style.yapf file
- reformat *.py files

Bug: 1051750
Change-Id: Ia50551d302bff115600bb4e532e29cc9ca5a9d5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2165727Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765390}

Bug: 1078101
Change-Id: I79afddab741466ad971e24ecd5b5f74b373f2b12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181036Reviewed-by: Tim Song <tengs@chromium.org>
Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765389}

Adds a new histogram Translate.Translate.AMPCacheURL reported
at same point that Translate.Translate is reported.


Bug: 797328
Change-Id: I0a3ff68f4fa47da4b866714fd575789ad34844e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2176318Reviewed-by: Megan Jablonski <megjablon@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Doug Arnett <dougarnett@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765388}

Adds traces to measure the duration until the theme is set and the
background image is loaded. Since the background image is loaded in an
iframe, the load event is sent back to the NTP via a postMessage and
logged there. If we logged the background image load time in the iframe,
the event would be logged with respect to the iframe's load time and,
thus, wouldn't be comparable to other NTP traces.

Bug: 1061078
Change-Id: Iaf5ceec2c6ee44e0f838cf25ae2c1cbbe0f03a58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181522
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765387}

If the retransmittable_on_wire_timeout is set to non-zero, but no custom
FLAGS_quic_max_aggressive_retransmittable_on_wire_ping_count is
provided, default set it to 200 which ensures that aggressive pings will
stop and falls back to 15s pings until forward progress is made on the
string. This helps mitigate data usage and battery usage if upstream
leaks long standing idle streams.

Bug: 1005610
Change-Id: I5b5072aaa13583ca8f1d76fea63ecfc04cb46591
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181577Reviewed-by: Nick Harper <nharper@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765386}

In this cl, we add model params path for unibuild models.

Bug: 881215,1062070
Change-Id: I0dafba8a870741e87e2ac1bb99e4721b6beb6f9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2160672Reviewed-by: Thanh Nguyen <thanhdng@chromium.org>
Commit-Queue: Jia Meng <jiameng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765385}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/0f47d332f161..9e99f7c84e3d

git log 0f47d332f161..9e99f7c84e3d --date=short --first-parent --format='%ad %ae %s'
2020-05-04 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).

Created with:
  gclient setdep -r src/third_party/depot_tools@9e99f7c84e3d

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC agable@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: None
Tbr: agable@chromium.org
Change-Id: I2d15b13bf624a3818f85a8c5daf8b7a3088e9764
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181720Reviewed-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@{#765384}

R=calamity@chromium.org

Change-Id: Id70ede3e2f6fc11dc94a74d0c04ff442e76fea0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181578Reviewed-by: calamity <calamity@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765383}

This adds kEncodeConstantQuantizationParameter to
VaapiWrapper::kEncode to configure how a VA-API driver controls
bitrate on video encoding, Constant Bit Rate (CBR) or Constant
Quantization Parameter (CQP).

In CBR, VaapiWrapper relies on the driver to produce a bitstream
following a specified bit rate. In CQP, VaapiWrapper caller
computes and provides an appropriate quantization parameter every
frame.

This CL introduces the new CodecMode and thus doesn't change
either functionality or behavior.

Bug: 1060775
Test: video.EncodeAccel.*
Change-Id: I3bf0b1eab142089ba6e945ff4b6e6dcc3b9651f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159178
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765382}