GitLab

R=caraitto@chromium.org

Bug: 1108942
Change-Id: I2bd72849d79a64d85cb9b61e87efe226d48a0cbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366662
Auto-Submit: Asanka Herath <asanka@chromium.org>
Reviewed-by: Caleb Raitto <caraitto@chromium.org>
Commit-Queue: Asanka Herath <asanka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800263}

The fallback dialog passes its dismissal runnable to be called on a
successful image_editor installation.

Bug: 1117675
Change-Id: I08a536b77ec459741940d20082b270aa4e900f1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363813
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Reviewed-by: Tanya Gupta <tgupta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800262}

This adds a histogram MediaRouter.PresentationUrl.BySink that records
the types of URLs passed into the Presentation API and what types of
sinks (screens/devices) they are rendered on.

This is to help assess the real-world usage of various scenarios and
inform the future roadmap of the API.

Note that the kExtension bucket will exclusively capture Google Meetings
by the time this hits the beta channel; however, I'm naming that bucket
kExtension for consistency with MediaRouteProviderId.

Bug: 1112866
Change-Id: Idc21cf0fff6d3b3984a21163ec26a01f4ed929df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350840
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800261}

https://dawn.googlesource.com/dawn.git/+log/7f265d1d4074..ab4e4feb01ac

2020-08-20 jiawei.shao@intel.com Workaround Intel Mesa driver issue about T2B copy with stencil aspects
2020-08-20 cwallez@chromium.org Remove MapRead/WriteAsync and CreateBufferMapped
2020-08-20 tommek@google.com Refactoring Queue::WriteTexture implementation

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/dawn-chromium-autoroll
Please CC cwallez@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
Bug: None
Tbr: cwallez@google.com
Change-Id: I0a5c4f8dc9b34357cdd11b38559de3736c81483d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367392Reviewed-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@{#800260}

This patch limits the selection of priority candidate to focused
elements with editable style. That is, previously we would consider
any focused element as a priority scroll anchor. Now, this is only
true if the element is editable.

This should be a middle ground that allows most cases in referenced
bug to be fixed (> 30 stars, multiple merged bugs). However, it would
also preserve the layout stability when editing forms with text
input.

R=chrishtr@chromium.org

Fixed: 1102229
Change-Id: I7341f0e513b70f8a4d836cebb68b931f2518534f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363079
Auto-Submit: vmpstr <vmpstr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800259}

The runtime flag remains for the legacy API, which
will continue as an origin trial and will be removed
later.

Intent to ship:
https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/XFO4OXrdSRA

Intent to experiment for legacy API:
https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/LLtmsTDMnXg

Bug: 1059912
Change-Id: I65d3ecf490fb6b0e229b7ee4c153c2f541a3c6c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367063Reviewed-by: Rick Byers <rbyers@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800258}

Bug: 1108940
Change-Id: I1ed44c12ebddb2a156b2677afb62add26c9221a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367027Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Solomon Kinard <solomonkinard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800257}

Adds fetching that is not automatic selection
and instead uses which feeds a user has picked.

BUG=1053599

Change-Id: Ib1c16d0efa409354c68845472484bfd33bf5145c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362997
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800256}

Bug: 973801
Change-Id: I7f50ede21dd71a63702b3b9e478f7c37bae2d01b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362869
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800255}

There is no change in behavior.
ui::ImageModel should be preferred to gfx::ImageSkia.

Bug: 1100034
Change-Id: I7ccd38bbcc1eb72112d7efdb0a0b84490d037887
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346087
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800254}

Bug: 1116579
Change-Id: Ifd4958aa53824914335715df58bd8a8d89913ad9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363401
Commit-Queue: Eric Orth <ericorth@chromium.org>
Reviewed-by: Dan McArdle <dmcardle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800253}

BUG=b:163526303

Change-Id: I2ff2dbbf66dbf380d13cf163c1376278aa947649
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353489Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Tao Wu <wutao@chromium.org>
Reviewed-by: Meilin Wang <meilinw@chromium.org>
Commit-Queue: Jeffrey Young <cowmoo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800252}

When SAML user is sent through online login the sync token may need to
be updated locally. This CL introduces logic analogous to token sync
on lock screen implemented in InSessionPasswordSyncManager: when new
session is started after online SAML flow we fetch a token from
sync token API and save it in local settings.

Bug: 1090341
Change-Id: Iee64115a1950a14a6cbcccbaf0d0607fbca1ba2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359998Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Maciek Slusarczyk <mslus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800251}

https://android.googlesource.com/platform/external/perfetto.git/+log/56d9df4fa53f..77419b0f04e8

2020-08-20 lalitm@google.com Merge "ui: implement quantization for thread state tracks"

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

Release_Notes:http://go/help_app-x20/relnotes/Nightly/help_app_nightly_202008200800_RC00.html

https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/help_app/app/+/ATO87Kt3GVbWvrrrePqcpzq_uVeSNAO_zG5viw3VGvUC

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll
Please CC help-app@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

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: b/162466284,b/165378070
Tbr: help-app@grotations.appspotmail.com
Change-Id: I28eec59880ba576a35f8c2f6c0d851e3a7efc9a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366819Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#800249}

Remove everything related to the "default" socket pool that is
completely unused.  Also simplify the DnsSocketPool interface for the
remaining much simpler usage of the class.

Also delete dns_session_unittest.cc since it was really only testing
that allocated sockets were properly freed in the pool, but that no
longer matters and it wasn't worth maintaining the mockability and hooks
in the pool needed for the test.

Bug: 1116579
Change-Id: Ib322bffb653e85a9c33a4b3835f4067fd8d29530
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357615
Commit-Queue: Eric Orth <ericorth@chromium.org>
Reviewed-by: Dan McArdle <dmcardle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800248}

This is the chromium/src side of the change.
It introduces a getViewType() API in ListContentManager,
and implements it.

This CL fixes a secondary bug: if a native view is added, removed,
and then added again to the FeedListContentManager, we would previously
try to wrap the view multiple times, which throws an exception. Now,
we wrap a view at most once.

Bug: 1119516, b/165317997
Change-Id: I2163c0e159c6d434329ea34f0449356a561a0c96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364965Reviewed-by: Dan H <harringtond@chromium.org>
Reviewed-by: Cathy Li <chili@chromium.org>
Commit-Queue: Dan H <harringtond@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800247}

Considering Mojo is used so heavily in Chromium, even such a small
change might bring us some perf improvement overall.

Bug: 896419

Change-Id: I9f4729fee0e3eed3ffb0448d4d0ac80a71997b19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362083
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#800246}

Bug: 1117626
Change-Id: I24af96b8149565d111950d82e4d3919470b5ff9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366559Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800245}

This CL makes sure that we don't start a check before we can be sure
that all preconditions are fulfilled:
* saved passwords are loaded
* first set of compromised credentials is displayed
* scripts are fetched (if necessary)

To prevent a third boolean value, this CL stores all applicable
preconditions as flags.

Bug: 1119366, 1092444
Change-Id: I81bf4577185709bd14b99cc0e878c5d38fbc4ebb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366759
Commit-Queue: Ioana Pandele <ioanap@chromium.org>
Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800244}

Implement the new UI for the audio device picker in global media
controls. As part of this change, the MediaNotificationBackground will
draw a gradient between the device picker and notification artwork if
the picker is availabile.

Screenshots of this updated UI will be posted on the crbug.

Change-Id: Ic7186c770102663b08e85b56eeddfbfa13833c3c
Bug: 1117160
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358512
Commit-Queue: Noah Rose Ledesma <noahrose@google.com>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800243}

WebCompositorInputHandler is no longer exist in the code base.

Bug: None
Change-Id: I3562b09949bdc87b4f6bdb36cc4b5514dd862e4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367437
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Reviewed-by: Changwan Ryu <changwan@chromium.org>
Auto-Submit: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800242}

These tests have been failing for a long time. Adding them can
ease rebaselines for disable-layout-ng and speed up the bot.

Bug: 591099
Change-Id: I531f4578e1a78cf788ce28d7cbe73b04fdad5211
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367452
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800241}

R=dschinazi@chromium.org

Change-Id: Ie82dfb2c4945403efc0dcddaa46aed6332e9c07c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367194
Commit-Queue: Ian Swett <ianswett@chromium.org>
Commit-Queue: David Schinazi <dschinazi@chromium.org>
Auto-Submit: Ian Swett <ianswett@chromium.org>
Reviewed-by: David Schinazi <dschinazi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800240}

The Search in Chrome intent wasn't doing anything if Chrome was in
the foreground, because in that case a separate code path is used and
that code path did not check for |searchQuery| in the startup
parameters.

The fix is to have that code path properly check for and handle
|searchQuery|. Because performing a search requires the user's default
search engine, the current BrowserState must now be passed to the
user activity handler.

The code that generates the search URL from the user's default search
engine has been refactored into a reusable function so it can be called
from the foreground code path.

Bug: 1115998
Change-Id: I88899ef8236584b0f69ea58362960abf6924650f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2356669
Commit-Queue: Guillaume Jenkins <gujen@google.com>
Reviewed-by: Justin Cohen <justincohen@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800239}

git grep -l '12a8179i_audio' | xargs sed -i '' \
-e  's/12a8179i_audio/12a8189h/g'
Removed Xcode 12 beta 4 enum from `builders.star` and `mixins.pyl`.

Bypassing CQ as try builders don't take `infra/config` change.

No-try: true
Bug: 1118191
Change-Id: I857fc58d95a0571d90b01ab24ec959e19d5e8580
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366728
Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800238}

This reverts commit 9aa31419.

Reason for revert: Speculative revert for crash seen here:
https://chrome-isolated.appspot.com/browse?namespace=default-gzip&digest=0e2a4602cb1fa392189ea01645e1df7138fc71ea&as=StandardOutputAndStandardError-com.google.gtest.ios-chrome-eg2tests.txt

First failure: https://chrome-swarming.appspot.com/task?id=4e225dd7f44b3a10

https://ci.chromium.org/p/chrome/builders/ci/ipad-simulator/12872?blamelist=1#blamelist-tab

Original change's description:
> [ios] Stops observing FeedView when its VC is removed.
> 
> Bug: 1085419
> Change-Id: I3d2dee5f2241aa244cf1bdc2f5d7d8cf7005908d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365095
> Reviewed-by: Ganggui Tang <gogerald@chromium.org>
> Commit-Queue: Sergio Collazos <sczs@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#799915}

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

Change-Id: I93aec427308f7be16020935af14f00f1106516df
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1085419
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367637Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800237}

With this CL, if a user does not make an explicit yes/no choice and
simply navigates away (but stays on the target domain), we will restart
the lite script such that the prompt is shown again the next time the
user visits the trigger site.

Bug: b/162825227
Change-Id: I0e47834c32b16810b9333fba1da8901de3cde2d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364532
Commit-Queue: Clemens Arbesser <arbesser@google.com>
Reviewed-by: Mathias Carlen <mcarlen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800236}

Extensions manifest and crx would default to net::IDLE priority for download. In order to speed up "task runner" priority of downloads, change priority for manifest and crx resource requests to net::MEDIUM when the active request's fetch_priority is in the FOREGROUND.

Bug: 1095181
Change-Id: I2e81333afb968127126a13956a4d53b6e58cfbe0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274477
Commit-Queue: Mohamadou Bella Bah <bellabah@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800235}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/aef2982079e5..2d664c1b3323

2020-08-20 zhin@chromium.org [third_party] Roll wasmparser 3.1.1

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

This reverts commit 17e2a917.

Reason for revert: Ensure buildtools.py is a no-op on bots.

Original change's description:
> Revert "Add -noverify to build commands to improve runtime (local builds only)"
>
> This reverts commit 132e1deb.
>
> Reason for revert: Android ASAN bot compilation failures: https://ci.chromium.org/p/chromium/builders/ci/Android%20ASAN%20%28dbg%29/26489
>
> Original change's description:
> > Add -noverify to build commands to improve runtime (local builds only)
> >
> > The flag is guarded by treat_warnings_as_errors=false so that it
> > will apply only to local developer builds.
> >
> > Results from //tools/android/build_speed/benchmark.py base_java_sig:
> > With change:
> > base_java_sig: 68.0s avg (68.8s, 67.2s)
> > base_java_sig: 68.4s avg (68.6s, 68.2s)
> >
> > Without change:
> > base_java_sig: 69.4s avg (69.3s, 69.5s)
> > base_java_sig: 69.7s avg (69.7s, 69.7s)
> >
> > time out/Debug/bin/run_base_junit_tests:
> > With Change:
> > real 0m22.741s
> > real 0m23.543s
> >
> > Without change:
> > real 0m23.176s
> > real 0m24.328s
> >
> > Bug: 1117222
> > Change-Id: I4bfd742165468bf9538e6fa0dc8f35daa9e0f23f
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313299
> > Commit-Queue: Andrew Grieve <agrieve@chromium.org>
> > Auto-Submit: Andrew Grieve <agrieve@chromium.org>
> > Reviewed-by: Peter Wen <wnwen@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#799285}
>
> TBR=wnwen@chromium.org,agrieve@chromium.org
>
> Change-Id: I82f411e5dab89c361a30c33e9103bd8561f19765
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 1117222
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362493
> Reviewed-by: Hajime Hoshi <hajimehoshi@chromium.org>
> Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#799471}

Bug: 1117222
Change-Id: Ib43bfe72869def7da43b237360df0e155149a963
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363975Reviewed-by: Peter Wen <wnwen@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800233}

Bug: 1119460
Change-Id: I43a2b33c5977e187d4d17e3bc666431d51d1eae4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364759
Auto-Submit: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Livvie Lin <livvielin@chromium.org>
Reviewed-by: Joe DeBlasio <jdeblasio@chromium.org>
Commit-Queue: Livvie Lin <livvielin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800232}

As part of enabling more lint checks, reducing the number of existing
baseline warnings/errors helps to offset future increases when we turn
on more checks.

Bug: 1116130
Change-Id: Ib06c4a27fb7c37f58e8682bc1bd367cae0a096bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364218
Commit-Queue: Peter Wen <wnwen@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800231}

Bug: 1101491
Change-Id: I589575dbf7f2d551770a11e624149d83a9921882
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366659
Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800230}

We add extensions to WaylandDisplayObserver called
WaylandDisplayObserverExtensions that allow display information to be
sent through other protocols and be followed by a wl_output "done"
event.

WaylandDisplayObserver only reported scale changes to its observers.
Since remote_output needs to know about work area changes as well as
scale changes, we modify WaylandDisplayObserver to report all metrics
changes to its extensions, which can decide if it needs to send any
updates.

BUG=b:165094142
TEST=exo_unittests
TEST=Verify insets are updated in ARC++.

Change-Id: I6577fe15eb5b09527008cf69a26b5eec7a7f1374
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363481Reviewed-by: Jun Mukai <mukai@chromium.org>
Commit-Queue: Prabir Pradhan <prabirmsp@chromium.org>
Auto-Submit: Prabir Pradhan <prabirmsp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800229}

This implements attachment handling for outgoing transfers. It reuses
the key verification step of incoming payloads and sends the
introduction payload to the remote device.

Bug: 1085067
Change-Id: I3534d60e5ad40a09d692278e312fb2d3dd3fb4aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352877
Commit-Queue: Richard Knoll <knollr@chromium.org>
Reviewed-by: Alex Chau <alexchau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800228}

LCD text and raster translation increases runtime cost to achieve sharp
text rendering. They are useless for blink generated drawings, most of
which use anti-aliasing, if there is no text.

Bug: 1119505
Change-Id: I5cb6c11b7f511d992ab29ae5317280a762b2df2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365132
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800227}

Bug: chromium:1115080
Change-Id: Ide2eceb4240d1e6bdf0fa9beaf1058428fab510d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367077Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800226}

This config option controls behavior that doesn't really match the name
or description, and nothing ever sets the option to non-default (false),
making half the controlled behavior dead code.

Bug: 1116579
Change-Id: Ic4c1d4e45b5cb4de74ff5b9cec788e3a1855d0d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357930
Commit-Queue: Eric Orth <ericorth@chromium.org>
Reviewed-by: Dan McArdle <dmcardle@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Auto-Submit: Eric Orth <ericorth@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800225}

The Clank team is reviewing the ownership
of all `/android` directories and adding/updating OWNERS
as part of an effort to normalize code health metrics
across different data sources.

https://docs.google.com/document/d/1wNj7dGIbSyISw1cyVSEnzt7woRydU2CBqVmWvUGTT44

Bug: 1112872
Change-Id: I4d211238862c74c79a897d8d28210fc17df33413
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367433
Auto-Submit: Fred Mello <fredmello@chromium.org>
Reviewed-by: Tommy Martino <tmartino@chromium.org>
Commit-Queue: Tommy Martino <tmartino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800224}