GitLab

Previously, if a 300x300 flex item got a 700 main size after flexing,
we'd assign a 300px cross size. LayoutReplaced doesn't pass the flexed
size (delivered in one of the Override sizes) through the aspect ratio,
so just add this logic directly in flex.

There's a regression, external/wpt/css/css-flexbox/align-items-007.html
that we'll have to fix before shipping, but I suspect the new behavior
might be right.

This CL adds a blink runtime flag, FlexAspectRatio, because this is the
first of a few aspect ratio fixes I want to ship at the same time. The
flag is set to experimental: enable-experimental-web-platform-features
users will see this fix in Canary right away. I will set the flag to
stable probably in time for M87.

Bug: 721123
Change-Id: Ie01f8da1a95eb940f20ba3e9bbf960bd4624c71b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2333530
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795227}

* 680px width in narrow mode if search is shown (matches settings rows).
* 80vw width in extreme narrow mode so that search input is not cutoff.
* The burger menu icon will not be hidden in narrow or extremely narrow.
* Magnifying glass further away from edge of narrow OS settings window.

Videos:
https://nimb.ws/UzWsaG
https://nimb.ws/ehD7iA

Fixed: 1110200
Change-Id: I33ec3b42108c84b60cb27aac9914b759b9a6a627
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2337277Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Regan Hsu <hsuregan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795226}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/10ee7644..4f52dde7

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

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

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

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

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

https://android.googlesource.com/platform/external/perfetto.git/+log/9a43f48ed4cd..f52572f002a6

2020-08-05 aninditaghosh@google.com Add noop rule to BUILD to import init file correctly on g3

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

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

StyledLabel eats event, probably because it has to handle links.
Explicitly sets this to false will fix hover issue.

Refer to b/161754148 for before and after view.

Fixed: b/161754915, b/161754148
Change-Id: I244814076c9afcc10d772301ed5780ac1e650ba4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339649Reviewed-by: Darren Shen <shend@chromium.org>
Reviewed-by: My Nguyen <myy@chromium.org>
Commit-Queue: My Nguyen <myy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795223}

Bug: None
Change-Id: I6dbc46ce4fb6162904a5026d284cc20954ad0f8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339791Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795222}

Failing bot: https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Linux%20MSAN

Bug: chromium:1113314
Change-Id: If00935628d5ef204be4d4ecfec58ae7991d9de61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339657Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795221}

For an Ad metrics project, we would like to gate adding an observer to
a subclass of V8PerFrameMemoryRequestAnySeq on there being an ad frame
detected on the page. Hence, we need to be able to check whether we
added this observer so that we can safely remove it in the destructor.
This CL adds a public bool method for checking whether the observer is
there before we try to remove it.

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

Bug: 973674
Change-Id: I235a1a95ebf760d175dc9800e041f0a1fd955036
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336305Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795219}

Instead of storing a ScrollTimeline that may be nullptr, store an
AnimationTimeline that's already been determined to either be a
ScrollTimeline or a DocumentTimeline.

There should be no behavior change in this CL. It's a preparation that
will make subsequent work on dynamically updatable @scroll-timeline
rules a bit smoother.

It's also needed in the future to differentiate between animation-
timeline:auto and animation-timeline:none.

Note: Apparently inspector_css_cascade_test.cc previously depended on
some header transitively included via css_animation_update.h.

Bug: 1074052
Change-Id: Ic9704f3a08859244163fd911b65bef98bc0b2d74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2332618Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795218}

Extends
  History.InMemoryURLHistoryItems
Removes
  History.InMemoryURLWords
  History.InMemoryURLChars
  History.InMemoryURLCacheSize

Bug: 1104944
Change-Id: If7cc4fa350ae543f02f7d0b5c2c87558c257313f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2337633
Commit-Queue: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795217}

This CL adds the 3 dotted menu shown per profile. The menu currently
supports deleting a profile and the remove confirmation action menu
shown afterwards. The remove confirmation has a warning message, profile
statistics and remove confirmation button.

Screenshot:
https://drive.google.com/file/d/1jjYRgjXEcNArNvLdEkRDa3XMV-r87DTY/view?usp=sharing
https://drive.google.com/file/d/1k20VUvBPysAVZrqbcXVtPgHsV6uAQZIm/view?usp=sharing
https://drive.google.com/file/d/18spWU68LxO6KzuPc-PZi7NHeRv62I25c/view?usp=sharing

Bug: 1063856
Change-Id: I06714382cd85d2142caae717ae526e7ee08e8e8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2329890
Commit-Queue: Monica Basta <msalama@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795216}

* Add a function StartScan to the lorgnette_manager_client API that
  allows scanning images using lorgnette's StartScan function.
  - Clients of the API can pass a RepeatingCallback<void(int)>, which
    will be invoked whenever the scan progress has updated.

* Implement StartScan for fake_lorgnette_manager_client.
* Update document_scan_api and unittests to use StartScan instead of
  ScanImageToString.

Bug: b:158504381
Change-Id: I6ca9e7645dc47a72d517d3d7480ea0f12e840e0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2332852Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Jesse Schettler <jschettler@chromium.org>
Commit-Queue: Fletcher Woodruff <fletcherw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795215}

This is so WebLayer can reuse this code to support NoStatePrefetch.

Bug: 1096088
Change-Id: Iead866201c684f3e349c67703171630508eb6c6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336599
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795214}

Bug: 1113202
Change-Id: I63ad3e451b5421b2d4398731405d6b151e558506
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339354Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Auto-Submit: Maksim Sadym <sadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795213}

This adds a flag, which defaults to enabled, which causes
the H264Decoder to assume that a DecoderBuffer contains a complete
picture and will output the frame to the accelerator after
processing the DecoderBuffer, rather than waiting for a signal of
EOS/AUD or the next picture in the bitstream.

The flag is temporary so we can verify if this breaks anything.

BUG=chromium:1105268
TEST=Verified decode latency is reduced with chrome tracing in apprtc

Change-Id: I864337be34634960eacdeaa26d2811d21b8e142d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2335338
Commit-Queue: Jeffrey Kardatzke <jkardatzke@google.com>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795212}

When the feature is turned on, replaces the two screenshot related tools
in the palette bubble. This uses the existing palette tool histogram
recording. Removes some unused functions. Screenshot in linked bug.

Test: manual
Change-Id: I145dd875fac579955b17531c63b5bed2d2e48305
Fixed: 1113014
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2333824
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795211}

https://crrev.com/c/2337734 was landed without the promised fixups
because of user error. These are the fixes that were promised.

Bug: 1112998
Tbr: ellyjones@chromium.org
Change-Id: I3442658b2016e0b772a2201d1ded10c7da383a39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339720Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795210}

When gfx::MultiAnimation exceeds its cycle time and isn't running
continuously, it calls Stop(), but doesn't first call
AnimationProgressed(). This means that the final animation state
might not be reached, i.e. AnimationProgressed() is not guaranteed
to run with a current value of 1.0. I've fixed that quirk in this CL
by calling AnimationProgressed() before stopping the animation.

This allows me to delete some code that was hacking around this quirk
in the omnibox simplified domain field trial implementation.
OmniboxViewViews::ElideAnimation was forcing the final frame to run
by calling AnimationProgressed() from AnimationEnded(). This hack was
causing a DCHECK failure when the simplified domain elision animation
was cancelled after the underlying RenderText text contents changed.
In other words, because ElideAnimation::Stop() really meant "run the
final frame and then stop", there was no safe way to cancel the
animation when its state had become stale. Now, with this
MultiAnimation fix, MultiAnimation ensures that the final frame runs
before the animation finishes, and ElideAnimation::Stop() just
stops the animation without running any frames.

Bug: 1103738

Change-Id: Idbf55bc2f326d3eaa9bf97a288e3ab467097953e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2330613
Commit-Queue: Emily Stark <estark@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795209}

The Event Page-based versions of these tests aren't flaky.

Bug: 1111337, 1111536
Change-Id: I8201a26f74d0990d47591a370b9c9ac6c2de6bb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339701
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795208}

This includes:
(1) Adding to BetterTogetherDeviceMetadata Proto.
(2) Adding to Mojo type.
(3) Adding to C++ RemoteDevice and RemoteDeviceRef classes.
(4) Updating tests.

Note that this field is not yet set during enrollment; a follow-up CL
will do this.

Bug: 1106937
Change-Id: I859efa86a7a57cff6eea185e2945a9201d14d508
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318685
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Josh Nohle <nohle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795207}

A shortcut has been added to check/uncheck nodes in the filter on
double-click in the visualization. The behavior is the same as clicking
the button manually on the node details panel.

Bug: 1106106
Change-Id: Idd08b152d956216c250657d0062c920507297f41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2333446
Commit-Queue: James Long <yjlong@google.com>
Reviewed-by: Samuel Huang <huangs@chromium.org>
Reviewed-by: Mohamed Heikal <mheikal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795206}

This CL breaks down a single boolean expression into separate,
explicit if statements.  This helps to improve the readability
of the function and add more comments that target individual
if statements (i.e. parts of the old boolean expression).

This CL has no intended behavior changes.

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

The share button is not sent for doodles that should not be shared.

Fixed: 1113160
Bug: 162949376
Change-Id: I833d6c536cc46fa9fa1db04149a45077a08809d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339759
Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org>
Commit-Queue: Alex Gough <ajgo@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795204}

This reverts commit 50136be2.

Reason for revert:

This also fails consistently on Linux Trusty:

https://ci.chromium.org/p/chromium/builders/ci/linux-trusty-rel/14445

Sample failure:

[ RUN      ] CpuAffinityTest.SetThreadCpuAffinityMode
../../base/cpu_affinity_posix_unittest.cc:114: Failure
Value of: SetThreadCpuAffinityMode(thread_id, CpuAffinityMode::kLittleCoresOnly)
  Actual: false
Expected: true
Stack trace:
#0 0x55b884c793f3 base::CpuAffinityTest_SetThreadCpuAffinityMode_Test::TestBody()

../../base/cpu_affinity_posix_unittest.cc:119: Failure
Value of: SetThreadCpuAffinityMode(thread_id, CpuAffinityMode::kDefault)
  Actual: false
Expected: true
Stack trace:
#0 0x55b884c797da base::CpuAffinityTest_SetThreadCpuAffinityMode_Test::TestBody()

Original change's description:
> Reland "base: Add API to restrict thread affinity to little cores on Android"
> 
> This is a reland of 027aa92e
> 
> Relanding but disabling test on CrOS devices (some of our CrOS devices
> seem to have asymmetric CPUs that aren't covered by the test).
> 
> Original change's description:
> > base: Add API to restrict thread affinity to little cores on Android
> >
> > Adds functions that facilitate setting the CPU affinity of a given
> > thread or process to all little cores on the system.
> >
> > We intend to use this API to run a power experiment.
> >
> > Bug: 1111789
> > Change-Id: I6c3d32c2338e9f00464e8b6a8c96af93658a3ae2
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2335176
> > Commit-Queue: Eric Seckler <eseckler@chromium.org>
> > Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> > Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#794998}
> 
> TBR: dcheng@chromium.org
> Bug: 1111789
> Change-Id: I59315ec0e9a1727986278a04fa5bde409143dfb5
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339416
> Reviewed-by: Eric Seckler <eseckler@chromium.org>
> Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
> Auto-Submit: Eric Seckler <eseckler@chromium.org>
> Commit-Queue: Sami Kyöstilä <skyostil@chromium.org>
> Commit-Queue: Eric Seckler <eseckler@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#795126}

TBR=dcheng@chromium.org,skyostil@chromium.org,eseckler@chromium.org

Change-Id: I3be932b56d8b42e10a7179e5310d041c1b687c28
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1111789
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339395Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795203}

This moves some duplicate code to CoreFaviconService where it can
be shared.

BUG=1076463
TEST=none

Change-Id: I0f6a26221acf189e57cd12a16d2624bd598917b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339388
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795202}

The caBLEv2 authenticator will need to use the network in the future. In
order to avoid a dependency cycle from //chrome/browser to the feature
module, and back to //chrome/browser (for getting the system network
context), this change injects the Mojo object into the module.

This involves moving the wrapper class
(CableAuthenticatorModuleProvider.java) into chrome/browser/webauthn.

BUG=1002262

Change-Id: I0240d3b05e1d51f7fe492eea5ad4e64af4111356
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2330930
Commit-Queue: Adam Langley <agl@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795201}

TBR=rogerta@chromium.org

Bug: 1113127
Change-Id: I646148022f66e257186bceac2eb38843221b99bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339933Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795200}

We don't have search available for now.

Change-Id: I7c363ead61f46af56c03d7f73f1f25e436517d09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339283Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795199}

The CL that previously addressed this problem only allowed pressing
the toggle button to enable/disable reverse scrolling, when the entire
row can be clicked in order to enable/disable reverse scrolling
(except for the learn more link).

Fixed: 1109966
Change-Id: Ica6eb360f2ac22770ff130f57b4cae5e58df2000
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339603Reviewed-by: Regan Hsu <hsuregan@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Regan Hsu <hsuregan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795198}

Extend the following histograms:
- Memory.BackgroundTask.Browser.PrivateSwapFootprint.*
- Memory.BackgroundTask.Browser.SharedMemoryFootprint.*
- Memory.BackgroundTask.OfflinePrefetch.Browser.PrivateSwapFootprint.*
- Memory.BackgroundTask.OfflinePrefetch.Browser.ResidentSet.*
- Memory.BackgroundTask.OfflinePrefetch.Browser.SharedMemoryFootprint.*

Bug: 1112399, 1112400, 1112401, 1112402, 1112403
Change-Id: Ifd0c20215f60fe76a092458e28f7cb02f1d71a0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339758Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795197}

https://skia.googlesource.com/skia.git/+log/e7b08e4876fb..4c97814f3adc

2020-08-05 brianosman@google.com Fix SKP serialization when SK_DISABLE_EFFECT_SERIALIZATION is defined
2020-08-05 scroggo@google.com Reland "Add an SkImageGenerator that uses NDK APIs"
2020-08-05 jmbetancourt@google.com get rid of unused include
2020-08-05 robertphillips@google.com Simplify GrSmallPathRenderer::visitProxies
2020-08-05 mtklein@google.com remove overdrawcolorfilter_runtime
2020-08-05 adlai@google.com Remove staging API for SkImage::makeWithFilter
2020-08-05 adlai@google.com Migrate MakeFromAdoptedTexture to GrRecordingContext
2020-08-05 mtklein@google.com add a global may-we-JIT flag
2020-08-05 egdaniel@google.com Don't allow transferring between special queues in vulkan in surface flush.
2020-08-05 johnstiles@google.com Fix out-of-bounds array access discovered by fuzzer.
2020-08-05 nifong@google.com Publish version 0.17.3
2020-08-05 scroggo@google.com Revert "Add an SkImageGenerator that uses NDK APIs"
2020-08-05 bungeman@google.com Use SkUniqueCFRef with CTTypesetterCreateLine
2020-08-05 scroggo@google.com Add an SkImageGenerator that uses NDK APIs

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 herb@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:1108040
Tbr: herb@google.com
Change-Id: Iead65fcd7be9143871ca224de4c3207347268cac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339653Reviewed-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@{#795196}

3d8daa2 Fix sym-upload-v2 whitespace in filenames.

BUG=1021742
R=mark@chromium.org, nbilling@google.com

Change-Id: Iafb23a63ee968024c6de7d5b636724384a6664af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339549
Commit-Queue: Michael Moss <mmoss@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Auto-Submit: Michael Moss <mmoss@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795195}

Bug: b/162891584
Test: manual
Change-Id: I912e7942787b0d2994e85a1570eb5bb1a0171578
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2337681Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795194}

Rename font icon name so it matches go/icons#icon=font_download

Bug: 1112552
Change-Id: I7f3e5d9e70cc67e8fbf7ebfc037a3bea359ac31c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339823Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795193}

This is part of a larger effort, started in Chrome CL
2297920, to separate GPU-backed GrDirectContexts from
DDL-backed GrRecordingContexts and remove the ambiguous
GrContext class.

Bug: skia:104662
Change-Id: I02b437b5925a4b6098c9bb720eb891ca3bb1c1fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2335812Reviewed-by: Robert Phillips <robertphillips@google.com>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: Adlai Holler <adlai@google.com>
Cr-Commit-Position: refs/heads/master@{#795192}

This is needed in order to enable support for extension-based typed
tracing events. For more information, see
https://perfetto.dev/docs/design-docs/extensions

Change-Id: I43bd82ee1c94cf7ae5be0a1fd7db4104cf8ece6a
Bug: 161696674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2332180Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Commit-Queue: Andrew Shulaev <ddrone@google.com>
Cr-Commit-Position: refs/heads/master@{#795191}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/bd6505349012..fb9c1110ef14

2020-08-05 bpastene@chromium.org Revert "ResultDB reporting for bot-triggered builds"
2020-08-05 nguyenmh@google.com Add a newline between commit messages

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 apolito@google.com,ehmaldonado@google.com,sokcevic@google.com,ajp@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

Bug: chromium:1113350
Tbr: apolito@google.com,ehmaldonado@google.com,sokcevic@google.com,ajp@google.com
Change-Id: I12a0093612a0a27fb801b9959fc03ca0e1be2a6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339545Reviewed-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@{#795190}

The first intended use-case of this is use in the CompositingAssignments
update step for overlap testing.

Bug: 1100711

Change-Id: I75e69d0633187fdc80eec71a74811453c6875cef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339384Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795189}

PEImage and PeImageReader are similar classes with slightly different
behaviors. This change updates the comments to clarify how they differ.

Change-Id: Id09868324b93d5a44731f778fb3f7684ca77736f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336303Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Auto-Submit: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795188}