GitLab

This change allows Mojo client processes to connect to a new process
network if disconnected from a previous one. Prior to this change, a
process could only belong to one network for its entire lifetime.

This new behavior is useful in cases where a client process may outlive
its original broker process (for example, if the broker crashes) and
should be able to continue operating normally when a new broker process
is established in the system.

Bug: 813112
Change-Id: Ifb5f16f1b39127cf7b469ee798f2d3da159fa432
Tbr: jam@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821743Reviewed-by: Wez <wez@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#700414}

This bug was introduced by my previous CL (https://crrev.com/c/1811183).
In that CL, calculating the edge padding was put before the update of
layout strategy. In this CL, replacing the check on layout strategy with
calling CanFitAllAppsWithoutScrolling.

Bug: 1006379
Change-Id: I74b6e0f85662d1c5c31cdbe0d1139357000a3321
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1828060Reviewed-by: Manu Cornet <manucornet@chromium.org>
Commit-Queue: Andrew Xu <andrewxu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700413}

https://skia.googlesource.com/skia.git/+log/49c073257022..be4787124940

git log 49c073257022..be4787124940 --date=short --no-merges --format='%ad %ae %s'
2019-09-26 mtklein@google.com hsw::S32_alpha_D32_filter_DX
2019-09-26 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2019-09-26 csmartdalton@google.com Remove the resolve rect and resolve types from GrRenderTarget
2019-09-26 ethannicholas@google.com Revert "Revert "remove 'in uniform' support from GrSkSLFP, make rules more clear""
2019-09-26 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2019-09-26 kjlubick@google.com [canvaskit] fix null terminator on drawText
2019-09-26 bsalomon@google.com srgb texture format cleanup.
2019-09-26 michaelludwig@google.com Improve subpixel coverage calculation for thin quads
2019-09-26 bsalomon@google.com Check support for each GL format independently.

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

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 bungeman@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
TBR=bungeman@google.com

Bug: chromium:1007154,chromium:1003481
Change-Id: I122e5d54c189ccf2434831f7b6c77939654e7054
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1826935Reviewed-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@{#700412}

Change RenderWidgetScreenMetricsEmulator API back into RenderWidget to be
specific to the properties being changed. Then it won't need to take as
input the whole VisualProperties in the future. And now it doesn't need
to construct a VisualProperties object.

Also make turning off the emulator explicit rather than having to destroy
it and having the destructor call back into the RenderWidget. We will
continue to remove RenderWidget re-entrancy with the emulator in future
changes.

R=avi@chromium.org

Bug: 1006052
Change-Id: Ie751a57117aa52205216b78190fec96777088e9c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825318
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700411}

Until now the |AssistantServiceManager::State| enum did not distinguish
between the state in which libassistant was started (but not ready yet)
and in which it is ready.
That distinction is needed to be able to add tests using libassistant,
as they have to wait until it is ready.

So now there are 4 states:
    - STOPPED: It has not started/it has been stopped (this is the same
    as the old STOPPED state).
    - STARTING: |AssistantServiceManager::Start| has been called and the
    libassistant |AssistantManager::Start| call has not finished yet (this
    is the same as the old STARTED state).
    - STARTED: the libassistant |AssistantManager::Start| call has
    finished, but libassistant has not signalled it is ready yet (this
    is the same as the old RUNNING state).
    - RUNNING: libassistant signalled it is ready (this state is new).

As this CL also introduces the first unittests for
|AssistantServiceManagerImpl|, it also contains a bunch of fake/dummy
classes used for the unittests.

This CL increases test coverage in //chromeos/services/assistant from 28%
to 41%.

Change-Id: If38a6b70e22e6392537b6658e5f39eebf6dd9099
BUG: b/141264108
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1810019
Commit-Queue: Jeroen Dhollander <jeroendh@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700410}

Using ImageEncoder will allow for further customization of options.
Additionally, as mentioned in [1], we should delete the ui/gfx image encoder,
so moving from this encoder may streamline future deletion.

No intended functional change.

[1]: https://codereview.chromium.org/2891373002

Bug: 1004867
Change-Id: I97ec05b40996f4130dad834d79228dda91d4c14e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827244Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700409}

This change converts InstalledAppProvider mojom interface client in blink
to use BrowserInterfaceBroker.

Bug: 936482
Change-Id: Ic31986ceb75b86691c0db1bed163bd2b7bfd8a7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1820878Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Cr-Commit-Position: refs/heads/master@{#700408}

Adds the necessary Chromium-side changes to fix stack symbolization for
non-browser crashes in GPU Telemetry tests on Android. Specifically:

1. Makes the GPU tests use GetStackTrace() on Android instead of
   LogSymbolizedUnsymbolizedMinidumps(), as this is currently the only
   way to get stack traces through Telemetry on Android.
2. Adds a --breakpad-dump-location argument to ChromeCrashReporterClient
   that is functionally equivalent to the existing
   BREAKPAD_DUMP_LOCATION environment variable, but necessary for
   Android since we can't set environment variables before launching
   Chrome on Android.
3. Moves the dump location override to ChromeCrashReporterClient::Create
   instead of whe retrieving the crash dump location in order to avoid
   issues with Android calling blocking functions in a scope that does
   not allow blocking functions.

Bug: 949321
Change-Id: I9be2446a73a2359157cd94c889bf34951b78c86b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825719
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700407}

This was used in AndroidVideoDecodeAccelerator previously and has been
obsolete.

Bug: 789435
Change-Id: I870507c35be3856a412217b51a325de12d5fff84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825483
Auto-Submit: Xiaohan Wang <xhwang@chromium.org>
Commit-Queue: John Rummell <jrummell@chromium.org>
Reviewed-by: John Rummell <jrummell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700406}

https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/db4083fd7f19..432efa25b347

git log db4083fd7f19..432efa25b347 --date=short --no-merges --format='%ad %ae %s'
2019-09-26 apodtele@gmail.com * src/base/ftstroke.c (ft_stroker_outside): Speed up clipped miter.

Created with:
  gclient setdep -r src/third_party/freetype/src@432efa25b347

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/freetype-chromium
Please CC bungeman@google.com,drott@google.com,thestig@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_chromium_msan_rel_ng;luci.chromium.try:linux-blink-rel;luci.chromium.try:mac10.12-blink-rel;luci.chromium.try:mac10.13_retina-blink-rel;luci.chromium.try:win10-blink-rel;luci.chromium.try:win7-blink-rel
TBR=bungeman@google.com,drott@google.com,thestig@google.com

Bug: None
Change-Id: I039893046df97f0a52890a5cd2c725e28f1d1892
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827759Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Reviewed-by: Ben Wagner <bungeman@chromium.org>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Ben Wagner <bungeman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700405}

If omnibox result details are empty, the app list search box should
display the provided search result title instead of empty details.
(if the details are empty, the target URL is provided as result title)

BUG=1007030

Change-Id: Ia9f18a8375eaa562b3e63dd548905f1a7005e579
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816147Reviewed-by: Jenny Zhang <jennyz@chromium.org>
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700404}

Avoid using generic names such as "base pose" or "transform", and try to
always specifically say which two spaces are connected by transforms.

Use the B_from_A naming convention where possible, so that transforms
can be chained naturally.

Bug: 1008102
Change-Id: I74988f89340375197017f9f518f69d4fd03e7d76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825585Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700403}

Also, deprecate sendMessageToTarget.

Bug: 991325
Change-Id: Ic29e941f0131adb00165dfde8380c4bb1c4ab982
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827674Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Johannes Henkel <johannes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700402}

Settings entry to switch sync accounts has been removed,
so this CL removes dialogs that are no longer used.

Bug: 1007331
Change-Id: I368b2115404696b41d355997ae297f921347b7af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821612
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Alex Ilin <alexilin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700401}

Now that Blink no longer needs to toggle GPU rasterization, we can
remove a bit of code.

This change pulls out the gpu rasterization viewport trigger logic
from Blink and CC.

Because the UI compositor still needs a way to control gpu
rasterization on platforms that have not enabled it for UI, we add
a new layer tree setting, |gpu_rasterization_disabled|.

Bug: 899399
Change-Id: I0dccc5ec6c90e4cff9a703d9cb629e2193ae3e57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1804183Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Reviewed-by: Nik Bhagat <nikunjb@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700400}

Bug: 1005779
Change-Id: I915eac43a06592cf2e196632408b4736b4f75f30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827823Reviewed-by: Ian Clelland <iclelland@chromium.org>
Commit-Queue: Charlie Hu <chenleihu@google.com>
Cr-Commit-Position: refs/heads/master@{#700399}

AXTree::RelativeToTreeBounds has some logic that tries to avoid
returning an empty bounding rect. If the current node has zero size,
it tries to compute the size either from the union of that node's
children, or if that fails, from the bounds of that node's nearest
ancestor with a size.

There was a subtle bug in this logic if a node has a position but
zero size. In a case like this:

root (0,0) size (800x600)
  window (100,100) size (400,300)
    button (120, 120) size (0,0)

The algorithm was returning a position of (220,220) incorrectly.

The fundamental problem was trying to fix a bounding box with zero size
at the same time as it was trying to walk up the ancestry to turn relative
positions to absolute positions.

The new algorithm just does it in two passes: first convert relative to
absolute, then if the bounds has no size, find the nearest ancestor with
a size and expand the current node as much as possible within that
ancestor's bounds.

Bug: 1005977
Change-Id: Ib4963fa98dabf958be49d3e13d6d932280b01b1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1815257
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Anastasia Helfinstein <anastasi@google.com>
Cr-Commit-Position: refs/heads/master@{#700398}

This CLs makes sure that GL Context made current inside
SwapBuffers and SetEnableDCOverlays to prevent potential crashes
inside DirectCompositionChildSurfaceWin.

Bug: 1007919
Change-Id: Ib28bd2a72405ea9f11fcbfecea50cecfb4d40760
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827484Reviewed-by: Jonathan Backer <backer@chromium.org>
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700397}

This modifies the viewport rect passed to OnDraw() to exclude the origin
if it's non-zero, since otherwise this adversely affects the compositor
clip rect. The non-zero value of the origin is captured in the adjusted
transform.

Bug: 1007012
Change-Id: I614b8ea3f14219d3dba54ad0a552b3e34145500e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827639Reviewed-by: James MacLean <wjmaclean@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700396}

This CL changes SkImage pixel upload logic inside WrappedSkImage to
support ETC1 and other format when they are not renderable.

Bug: 906794
Change-Id: Ica7da0e7ce4a5feee7dc5286af51a239ae3257f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1810759
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700395}

ANGLE creates a child window when using X11. The Expose events from this
child window need to be forwarded to Chrome's parent window for the
window to be properly redrawn.

Bug: 991577
Change-Id: Ibba1ad07110953dc46b7bd1939b03471a316f798
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1822721
Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700394}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/6384e38b..e4371bf3

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,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I4413320e16bd47ed48e2a858db25c95070f35fd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827897Reviewed-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@{#700393}

crashpad_main defines the native entry point for the JNI call used to
launch Crashpad from CrashpadMain.java. This dependency was mistakenly
removed in:
https://chromium-review.googlesource.com/c/chromium/src/+/1824018

Bug: 1008383
Change-Id: I20c27a14191611eba8155affb404370ca6523c3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827825
Commit-Queue: Joshua Peraza <jperaza@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700392}

We should aim to have these checks around the API "border" and then
prevent certain actions when it is true (like scheduling frames). This
hoists the check in UpdateAnimationsAndScheduleFrameIfNeeded(...) out
into its callers adds TODOs where it seems we shouldn't need to check
(per the previous sentence).

Bug: 998526
Change-Id: I782a41033c33dba38b4923e96e84531858675c0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827422Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#700391}

Bug: 995916
Change-Id: Ic874d6287e224da3277cff98457604617f5a64dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1814919
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700390}

Copied from email thread:
EnableRequireVoiceMatchVerification option is intended to be used
independent of whether or not the user has speaker id models on-device
(i.e. Libassistant ignores that option if user has no SID model).
The downside of conditionally enabling it would be: If the speech
pipeline is already running when that option is set, the change won't
take effect until next Speech pipeline restart (b/120241931).

Bug: b/120241931
Test: Manual Test
Change-Id: I0deef204ef5c6dd9ee36acbb5074d1a2e47731c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824676Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Yue Li <updowndota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700389}

https://webrtc.googlesource.com/src.git/+log/b4ffe881cdd7..ee8ee2f10366

git log b4ffe881cdd7..ee8ee2f10366 --date=short --no-merges --format='%ad %ae %s'
2019-09-26 henrika@webrtc.org Avoids update of WebRTC.Audio.SourceMatchesRecordingSession for Android < N
2019-09-26 sprang@webrtc.org Prepares RtpSenderVideo for batch forwarding of generated packets
2019-09-26 nisse@webrtc.org Report payload byte counts in PC-level quality tests

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

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

TBR=webrtc-chromium-sheriffs-robots@google.com

Bug: chromium:None
Change-Id: I38b2436719273b6b081cb43f6f6fbc54be6fd3d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1826866Reviewed-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@{#700388}

A device policy which controls the select to speak accessibility feature on the
login screen.The policy can be applied as a recommended or mandatory policy.

Test:
1. Set the login_screen_select_to_speak_enabled policy to True, open System
Tray => "Accessibility", check that "Select-to-Speak" is displayed with a green
check in the login screen.
2. Set the policy to False, open System Tray, check that "Select-to-Speak" is
not displayed in the login screen.

Bug: 552439
Change-Id: I86bfea61ccf3cac74934f17181c260d5649e04c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816558
Commit-Queue: Amr Aboelkher <amraboelkher@google.com>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700387}

Using wpt-import in Chromium 045ed7eb.
With Chromium commits locally applied on WPT:
561a338c "Convert SensorProvider client to use BrowserInterfaceBroker"
b5630d76 "Convert NFC client to use BrowserInterfaceBroker"


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=robertma

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

https://android.googlesource.com/platform/external/perfetto.git/+log/d58b3ef67609..8f223cdf4c24

git log d58b3ef67609..8f223cdf4c24 --date=short --no-merges --format='%ad %ae %s'
2019-09-26 lalitm@google.com Merge "trace_processor: add help command about json metrics being supported"
2019-09-26 fmayer@google.com Merge "Fix segfault in StackProfileTracker."
2019-09-26 lalitm@google.com Merge "trace_processor: optimize bitvector implementation"
2019-09-26 lalitm@google.com Merge "trace_processor: add better unittests and more benchmarks for bitvector"
2019-09-26 lalitm@google.com perfetto: fix formatting nit for internal code style

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

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

TBR=perfetto-bugs@google.com

Bug: None
Change-Id: I118a4bc40f20a9e24c3ba447adb0d402fb8e6871
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827493Reviewed-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@{#700385}

Change scrub bar color to #8AB4F8, 100% opacity for played,
30% for remaining track.

Bug: 1008228
Change-Id: I1cbc1c80bb3bcdd2bf450bfde90be3b07007c382
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825792
Commit-Queue: Jazz Xu <jazzhsu@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700384}

This is necessary to allow migrating the PDF viewer from Polymer2 to Polymer3,
since the latter uses generated files.

Added automated test. Can also verify manually as follows
1) Visit chrome-extension://mhjfbmdgcfjbbpaeojofohoefgiehjai/elements/shared-vars.m.js
2) Should see the contents of the generated file.

Bug: 1005029
Change-Id: I762672a0078f00b62500391f2d880d5e6432befe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1814840
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700383}

In many situations the same GPU on different OEM devices manifest
different behaviors, so it's important to switch from 2-part
identification of a GPU (vendor_id, device_id) to 4-part:
  (vendor_id, device_id, sub_sys_id, revision)

This is the first CL. This adds the fields to GPUInfo and add
the info collection and wire the info to about:gpu page.

BUG=1006960
TEST=gpu_unittests, about:gpu
R=sunnyps@chromium.org,dcheng@chromium.org

Change-Id: Ia8623cdf842ec8eb899a018c26c9267fb9a2c880
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824457
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Alexei Filippov <alph@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700382}

It's possible the AppCacheQuotaClient's callback is holding the last
reference to QuotaManager, which means QuotaManager gets destroyed when
those callbacks are run. This causes AppCacheQuotaClient to be destroyed
when it is still executing code in NotifyAppCacheDestroyed.

Bug: 1003298
Change-Id: I07afe921c10f34c9bdee8c020b7194e659337281
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827490
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700381}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/1ab7b6816f57..983111f039f6

git log 1ab7b6816f57..983111f039f6 --date=short --no-merges --format='%ad %ae %s'
2019-09-26 qyearsley@chromium.org Add `git cl try --retry-failed`

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

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

TBR=agable@chromium.org

Bug: chromium:985887
Change-Id: Ifea864280c2ae2acc8cdfb61d9944c2daaf42f62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827492Reviewed-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@{#700380}

Variables are conditionally set depending on media size.

Bug: 1000606
Change-Id: Iae4ec877910814541cd57c6ce3ffda0620d0a9b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827295Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700379}

TBR=govind@chromium.org

Change-Id: I8bce88cb7d2c28717011452f84c24a3f89beae67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1826650Reviewed-by: Ben Mason <benmason@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700378}

This reverts commit 7df96a78.

Reason for revert: Causing build failure on Linux Builder (dbg)(32):
https://ci.chromium.org/p/chromium/builders/ci/Linux%20Builder%20%28dbg%29%2832%29/121638

Original change's description:
> Remove sorting_context_id from cc::Layer and calling code.
> 
> This code is not used now that BlinkGenPropertyTrees has launched.
> 
> Bug: 993936,1008483
> 
> Change-Id: Ia253725e327c5d115c95e341f7791539e881cc9c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1817318
> Auto-Submit: Chris Harrelson <chrishtr@chromium.org>
> Reviewed-by: Mason Freed <masonfreed@chromium.org>
> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
> Reviewed-by: vmpstr <vmpstr@chromium.org>
> Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#700372}

TBR=wangxianzhu@chromium.org,vmpstr@chromium.org,chrishtr@chromium.org,masonfreed@chromium.org,michaelludwig@google.com

Change-Id: I0145691722859f20dc99aabee84db432caf2cbe7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 993936, 1008483
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827253Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700377}

- Force compositing for backdrop-filters. We probably won't support
  non-composited backdrop-filters because it depends on viz renderers.

- Paint empty display item for backdrop-filter to ensure a paint
  chunk which will create the composited backdrop-filter layer.

Bug: 923429
Change-Id: Ib2afbde2c4ad3a485049b25ee63d6537f675ade6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824317
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700376}

Conversion was done automatically using "2to3 -w -f except".

This is backwards compatible with Python 2.
There are no intended behavioural changes.

Bug: 941669
Change-Id: I00e5acf46cdf0999c5e2f6e8e85e55e2fc611eca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1815871
Commit-Queue: Raul Tambre <raul@tambre.ee>
Auto-Submit: Raul Tambre <raul@tambre.ee>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700375}