GitLab

Using wpt-import in Chromium 92ce1bbe.

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

NOAUTOREVERT=true
TBR=smcgruer@google.com

No-Export: true
Change-Id: I69e5b8d9b83fadd871b89c78e3e7cbe4a25a3f84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275104Reviewed-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@{#784254}

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

To facilitate assessing the impact of intensive throttling on a page,
this CL exposes an option in chrome://flags to enable intensive
throttling as soon as a page is hidden.

Bug: 1075553
Change-Id: I2507674186294f1ec8e23a9d93f17c5d23a7e2bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276294Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Auto-Submit: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784252}

This class adapts Media Foundation IMFContentDecryptionModuleSession
to a class that uses Chromium CDM types. It also handles setting session
ID which isn't available when the session is created. This makes it
easier for MediaFoundationCdm (to be uploaded in the next CL) to manage
multiple sessions.

NOPRESUBMIT=true

Bug: 999747
Change-Id: Id966915d8bebb97406a412c4d2e958f2e2529576
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2265099
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: John Rummell <jrummell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784251}

This CL saves the last AverageDuration() value from DecoderStream on the
correct thread, to be used in IsBeforeStartTime(), which can be called
from a different thread.

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

https://chromium.googlesource.com/external/github.com/google/EarlGrey.git/+log/f971ef807cdc..b0d1c3d5f6ac

$ git log f971ef807..b0d1c3d5f --date=short --no-merges --format='%ad %ae %s'
2020-06-30 tirodkar Fix UITouch compilation issues on iOS 14+ in GREYTouchInjector.

Created with:
  roll-dep src/ios/third_party/earl_grey2/src

Bug: 1101083
Change-Id: Ic74eb69f613e289aa5d5ebc76004ae7d5ea8c30a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275470Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784249}

Code was removed in r544472.

Fixed: 1089534
Change-Id: I344e62c88f92c7ae1aa71b13177e020f75315215
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275141Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784248}

ChromeOS has an	"old" video decoder and	a "new"	VideoDecoder. ToT has
two flags to decide which one to use:
1. A chrome:flags kChromeosVideoDecoder.
2. A command-line flag kForceDisableNewAcceleratedVideoDecoder passed by
the ChromeOS command line builder.

After careful deliberation we think the "new" should be called "direct"
because it implements the media::VideoDecoder interface directly, as
opposed to the "old" VideoDecodeAccelerator, that needed an adapter (the
trusty VdaVideoDecoder).

This CL refactors these flag names to:
- A chrome:flags kUseChromeOSDirectVideoDecoder, intended for user
debugging/finching (equivalent to 1. above, but renamed for clarity).
- A kPlatformDisallowsChromeOSDirectVideoDecoder passed by the ChromeOS
command line builder (equivalent to 2. above, renamed for clarity).
- A new kUseAlternateVideoDecoderImplementation that is used by the CrOS
Tast test infra to instruct Chrome to use the "other" video decoder
implementation. This is needed to have a set of tests verifying the new
decoder implementation pre-launching.

All these flags only apply to OS_CHROMEOS, otherwise we should not use
the direct video decoder (see crbug.com/1099172). The first two flags
also only exist when BUILDFLAG(USE_CHROMEOS_MEDIA_ACCELERATION). (Note
that those two only overlap partially: USE_CHROMEOS_MEDIA_ACCELERATION
can be enabled on e.g. Linux and Chromecast).

TBR=alemate@chromium.org for chrome_restart_request.cc trivial rename.

Bug: b:159825227
Change-Id: I3b9878abed1fd71a2f435d348256e713d800404f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268540
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784247}

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-win-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: If4b0eff33d6e2f5f526f18d74273b61857c715f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276615Reviewed-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@{#784246}

Setup the event.relatedTarget when creating drag drop test events that
will be sent to the target element.

The browser initializes the event.fromElement from that .relatedTarget
value (use the source element) and is only really needed for dragenter
events to better simulate a dragenter event. Use null for the dragover
and drop events (just like chrome).

Bug: 1062902
Change-Id: I899e704f3026cc1f1cdbce2ed7436fc14be2e74e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274885
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Auto-Submit: Noel Gordon <noel@chromium.org>
Reviewed-by: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784245}

The test drag and drop test helper sends a 'dragEnd' event but nothing
responds to that event in files app, nor is it defined in the spec.

Make it spec-conformant: change 'dragEnd' => 'dragend' and the browser
will properly handle it and files app will correctly process it.

Bug: 1062902
Change-Id: I3ed0ba7c7e5f586132dcb88f34e5537ff7587a08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276163
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Auto-Submit: Noel Gordon <noel@chromium.org>
Reviewed-by: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784244}

In canvas, we are trying to move tests from perf_tests/canvas to
rendering benchmark so that our tests can take advantage of the existing
rendering benchmark infrastructure. I moved tests in this cl,
https://chromium-review.googlesource.com/c/chromium/src/+/2214750.
And now I would like to delete them from perf_tests/canvas directory.

Bug: 1077148
Change-Id: I3fa3a1aa7bb46316fce698950fbdf0747e718e26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268397
Commit-Queue: Yi Xu <yiyix@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784243}

This CL converts base::Bind to base::BindRepeating in the
bookmarks/ folder.

This is a code health CL, no behavior change.

Bug: 1007635
Change-Id: I67cb9491fa8bc275e4df16221a428a8e226f0711
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274159
Auto-Submit: Xida Chen <xidachen@chromium.org>
Commit-Queue: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784242}

I am uploading minor fixes in parallel.

Change-Id: If4ff1a5047f4b652249c83cba28073a7a9e30b1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276707
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784241}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/64b2c2e83ae6..947260e25933

2020-06-30 fawazm@google.com Enable adding of authenticators

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:1034663
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: If9228577ce094f5f9a19ada45ecf0840c9e398b1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2277019
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#784240}

Bug: 1068400
Change-Id: I8bc8108bd79ba098b9221ee275890702163faae3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2256845
Commit-Queue: Ilia Samsonov <isamsonov@google.com>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784239}

CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-chrome
TBR=chrome-os-gardeners@google.com

Change-Id: Id239923d74d88eddac5c06339c91fea6faff4c30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276482Reviewed-by: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#784238}

This CL adds all of the existing DevTools actions to the
DevToolsKeyboardShortcutAction enum so that we'll get a clearer picture
of which shortcuts are being used. The corresponding frontend enum is
updated in this CL: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2276745

Custom shortcuts design doc: https://docs.google.com/document/d/1oOPSWPxCHvMoBZ0Fw9jwFZt6gP4lrsrsl8DEAp-Hy7o/edit#

Bug: 174309
Change-Id: I203bc9364c571685f92b770e6de7bcf0ebc7e0ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276498
Commit-Queue: Jack Lynch <jalyn@microsoft.com>
Reviewed-by: Brandon Goddard <brgoddar@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#784237}

These tests were disabled for various reasons, but passed 3000
iterations on bots for all platforms.

Note that sub-tests that checked for permissions failures were
removed, since the <all_urls> permission is now needed for this
API, and that was added to the manifest for other tests that
weren't disabled.

Bug: 80212, 117927, 367695
Change-Id: I074f78626cac1fa4c8be6e020ea77b7e8ca3d65c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2267929Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784236}

Restoring the session should obviate the need for retaining
the initial url argument.

Also remove the flag switches and their sentinels, because
the flag switches will be added by Chrome on restart.

Bug: 964541
Change-Id: I70d32c630565ce6f636d18e09b784016eef14d92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2249379
Commit-Queue: David Bienvenu <davidbienvenu@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784235}

Textures that are uploaded as GL_LUMINANCE_ALPHA, GL_LUMINANCE, or
GL_ALPHA, are, on some platforms, emulated using glTexParameteri with
GL_TEXTURE_SWIZZLE_R/G/B.

The call to glTexParameteri needs to be done after the glTexImage2D call
that uploads the pixel data. Do this.

Remove swizzle from the common parameters because GLImages don't support
the formats that require swizzles. Add a DCHECK in case we're trying to
do that anyway.

Bug: 1096361
Change-Id: I0b58a7ccb803108d0b3b0c43a68a6709d869aea8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276578Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784234}

In the spec[1], a new decoder is created unconditionally on each call
to decode() unless the previous call passed {stream:true}, but in the
real world that requires an allocation of a TextCodec object.

Since the previous TextCodec would be flushed by the previous decode()
call *unless* {stream:true} was passed, then we don't need a new
TextCodec to match the spec behavior.

On a simple test (64k strings, length 16-32, 50 iterations), the
change showed an 11% performance improvement (with a standard
deviation of 1.3% over 10 runs).

[1] https://encoding.spec.whatwg.org/#dom-textdecoder-decode

Bug: 1092582
Change-Id: I815a3e4c2885397aaf24ef790b7470c7ed761ada
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2271061
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784233}

Only use red font when the currently selected destination is a local
Chrome OS printer since only local Chrome OS printers display status
errors.

Bug: 1059607
Change-Id: Ie0462f57f09b8651735bb6c9878946090198ddb7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274184
Commit-Queue: Gavin Williams <gavinwill@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784232}

In https://crrev.com/c/2250945, we will stop swapping
BrowsingInstances on eligible browser-initiated navigations when the
affected RenderFrameHost has not committed a navigation, since this is
wasteful and prevents the spare process from working correctly with NTP.
This affects expectations for some tests which had been relying on this
behavior implicitly on Android.  This CL adjusts these expectations.

Bug: 1094088
Change-Id: I8db951b0194a80c2c9059a0ed81f4570ed4cedb6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275146Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784231}

- Polymer3 does not require html files in its build resources.
- Streamlined adding new resource files for print management.

Bug: 1053704
Change-Id: If9c993aec0380315058296cfc83f90623e5b5871
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2259137
Commit-Queue: Jimmy Gong <jimmyxgong@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784230}

This CL also moves the AssistantOnboardingMode enum to be consistent
with ConsentStatus.

Bug: b:157510970
Change-Id: Ib92e56850cd2f62a073e1927eb9eaadfd390cc0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2262452
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784229}

The following 6 stories are consistently failing on perf waterfall:
* v8.browsing_desktop-future/browse:tools:gmail-labelclick:2020
* v8.browsing_desktop-future/browse:tools:gmail-openconversation:2020
* v8.browsing_desktop-future/browse:tools:gmail-search:2020
* v8.browsing_desktop/browse:tools:gmail-labelclick:2020
* v8.browsing_desktop/browse:tools:gmail-openconversation:2020
* v8.browsing_desktop/browse:tools:gmail-search:2020

This CL disables those stories for now.

Bug: chromium:1100138
Change-Id: I372b37eca788aa55a4fa351927fc12fe8931a95e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276299Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Wenbin Zhang <wenbinzhang@google.com>
Cr-Commit-Position: refs/heads/master@{#784228}

https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/d5b5215a888d..8d3f3b7dac48

2020-06-30 johnkslang@users.noreply.github.com Merge pull request #2302 from KhronosGroup/fix-texture-precision

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

Cq-Include-Trybots: luci.chromium.try:android_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64
Tbr: radial-bots+chrome-roll@google.com,ianelliott@google.com
Change-Id: I98dd45347e8ae3bc39d3d65e82b10fe119ab1a52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2277022Reviewed-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@{#784227}

Unlike the old implementation, this one leverages Polymer bindings
to hide/show toolbar children, while the document transitions from
loading to loaded.

Fixed: 1100430
Change-Id: I0d54c69c45687295ad309c9215a6b7d38dcbfd05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274861
Commit-Queue: dpapad <dpapad@chromium.org>
Reviewed-by: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784226}

Match the rule used in other Google open source projects described
at https://opensource.google/docs/thirdparty/documentation/#owners:
the first lines in the OWNERS file are

* Two committers, OR
* A file: directive pointing to another OWNERS file in //third_party

(Copied by jrn@ from an internal CL making the same change; fleshed
out the commit message.)

Change-Id: I4e031684941e90a5d9257d053ca0d36d7da6f67f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276813Reviewed-by: Dirk Pranke <dpranke@google.com>
Commit-Queue: Dirk Pranke <dpranke@google.com>
Cr-Commit-Position: refs/heads/master@{#784225}

Bug: internal b/144557463
Bug: 1101110
Test: Build
Change-Id: I39549934fb7234b58c664337acd05232d60d0875
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2265434
Commit-Queue: Junbo Ke <juke@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784224}

Object attributes on text, such as text-align, margin-left, and
text-indent allow JAWS to know what the current indentation level
is in VSCode. Firefox already exposes them. This CL is part of an
effort to expose these object attributes.

AX-Relnodes: Expose text-align object attribute to IA2.

Bug: 1090995
Change-Id: I88d3ff47e74a9f9d267c952348c655678b72c919
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2264456
Commit-Queue: Abigail Klein <abigailbklein@google.com>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Adam Ettenberger <Adam.Ettenberger@microsoft.com>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784223}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/d014422b2085..af04ef2a7d2e

2020-06-30 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2020-06-30 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2020-06-30 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).

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

Bug: None
Tbr: agable@chromium.org
Change-Id: I7d50d2f726e5b8d812c8eb5c74a7dce3375fcfce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2277020Reviewed-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@{#784222}

ServiceWorkerCacheWriter doesn't use
ServiceWorkerResponse{Reader,Writer} any more. Update mock reader/writer
to remove implementations for old reader/writer. Mock reader/writer
are renamed to ServiceWorkerResource{Reader,Writer} as these only
implements new reader/writer.

Bug: 1055677
Change-Id: I77c12eeb370e5a84a82431b034b580b8dd913324
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275372Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784221}

Onboarding mode will be wired up to the feature in a follow up CL.

Bug: b:157510970
Change-Id: Ifec0007db64361b00c2cb3451cc579a1aa884431
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252926
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Jeroen Dhollander <jeroendh@google.com>
Cr-Commit-Position: refs/heads/master@{#784220}

Reporting will regularly need to do exponential backoff on failed
requests. This CL creates a standard BackoffEntry object for managing
failed requests.

Bug: chromium:1078512
Change-Id: I51e9ac33a344e200e283731a9f98430e86920461
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276632Reviewed-by: Leonid Baraz <lbaraz@chromium.org>
Commit-Queue: Zach Trudo <zatrudo@google.com>
Cr-Commit-Position: refs/heads/master@{#784219}

This will be used by Assistant to present different onboarding
experiences based on policy.

Actual client-side usage will be wired up in a follow up CL.

Bug: b:159069105
Change-Id: I52fae64681f5ae4113d6b58b0e5d5ecb1bbdaccb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250587
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Bartosz Fabianowski <bartfab@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784218}

In order to implement Drag & Drop, extend the abstract base class
NativeFileSystemTransferToken with an implementation that's not tightly
coupled to an origin. When exchanging this token for an
NativeFileSystemFileHandle/NativeFileSystemDirectoryHandle, a caller
should pass in a BindingContext and the NativeFileSystemManager will
lazily create the handle.

Bug: 1080811
Change-Id: If6daaf628ec27d2e23339901d3db22d9c0386e08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2243997Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Darwin Huang <huangdarwin@chromium.org>
Commit-Queue: Hazim Mohamed <hazimmohamed@google.com>
Cr-Commit-Position: refs/heads/master@{#784217}

This CL converts base::Callback in the bookmarks/ folder.

This is a code health CL, no behavior change.

Bug: 1007635
Change-Id: I5a1564ef948a5f1fb90117906918e65e0c8dc602
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274157
Auto-Submit: Xida Chen <xidachen@chromium.org>
Commit-Queue: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784216}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/6685f320c0ae..c75547d598c4

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 davidbienvenu@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: None
Tbr: davidbienvenu@google.com
Change-Id: I39db9499e9398d938e9a97a437396a54f44743a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276550Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Reviewed-by: David Bienvenu <davidbienvenu@google.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#784215}