GitLab

This CL is making the TtsPlatformImpl instance a leaky
instance since the singleton is alive for the whole
duration of the process.

The use of WeakPtr is no longer required.

Bug: 1133813
Change-Id: Iceeb676cd23a1867132255b51c4fb3439e049985
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441674
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812791}

This will be used to show or hide a separate set of settings for
pointing sticks. For now, the visibility logic is modified to show mouse
settings if either a mouse or pointing stick is connected, to preserve
existing behaviour.

To test, you can use a Python script [0] to create a fake pointing
stick with uinput.

[0]: https://gist.github.com/HarryCutts/e17783d9475e45abcc4b73b9e7aabb7a

Bug: 1114828
Test: check `hasPointingStick` value with and without a pointing stick

Change-Id: I917c8ead69a126280752a9a1a4b4bea609c7e33c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427888
Auto-Submit: Harry Cutts <hcutts@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812790}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/11b196b0c0c6..124ea2073720

2020-10-01 engeg@google.com gclient: override special DEPS file for P0
2020-10-01 chrome-bot@chromium.org Update config settings by config-updater.
2020-10-01 ahassani@chromium.org paygen: Add default source_version
2020-10-01 bpastene@chromium.org cros_chrome_sdk: Fetch SDK components in parallel on two threads.
2020-09-30 pprabhu@chromium.org cbuildbot: Bump skylab tool version
2020-09-30 lamontjones@chromium.org cros_branch: allow multiple checkouts of the manifest.

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/chromite-chromium-autoroll
Please CC chrome-os-gardeners@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:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel
Tbr: chrome-os-gardeners@google.com
Change-Id: Ie11ace58584c4604324d96184cd37c0631869308
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441741Reviewed-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@{#812789}

Hide promo and modules until both are loaded.

Fix issue with promo that is not shown until resize. The promo is hidden
using "display: none" when the "hidden" attribute is set. This needs to
be updated before emitting the loaded event. The handler needs the
bounding rect of the element to be set to determine if it overlaps with
the most-visited tiles. This is only a concern for when modules are
disabled.

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

- No change in functionality

Bug: 1125150
Test: browser_tests --gtest_filter=DiagnosticsApp*
Change-Id: I7a91fb6f2f012859bf457de44503864cbc64151e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441110
Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812787}

Move ChromeVersionInfo and ChromeVersionConstants into it.

Leave a ChromeVersionInfo in the .chrome.browser package and in the
chrome_java build target not to break downstream.

Bug: 1131982
Change-Id: Iea505fc24b46abbadcc45b0aa94ebc1d95663cc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429444
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812786}

We'll use the same component for the blocklist & sorting-lsh files.

Implemented the SortingLSH service, renamed the floc component
installer, re-configured the relevant paths and updated the format key
so old versions will be skipped.


Bug: 1062736
Change-Id: I4cde3e5850b4d2c5aca1804f7ca302ae3fc4a35f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425327
Commit-Queue: Yao Xiao <yaoxia@chromium.org>
Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812785}

Currently, bookmark suggestions are limited to title & URL matches. E.g
the input 'planets jupiter' won't suggest a bookmark titled 'jupiter' in
a directory 'planets'.

This is the 1st of 3 CLs implementing bookmark-paths which will allow
inputs to match bookmark paths (without contributing to the bookmark
suggestion's score).

This CL creates 4 params that will support 5 planned UI variations:
1) Title - URL (current behaviour)
2) Title - Path
3) Title : Path - URL
4) Path/Title - URL
5) Title - Path|URL (either path or URL depending on which matched the
input; favor path if both or neither matched the input)

Bug: 1129524
Change-Id: Iba575d8fc7db2fcb8ec9bd9b8c384dac83eaba1e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416931Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812784}

Privacy doc: http://shortn/_tLQoix3T1o

Bug: 1129505
Change-Id: I65602b089afc0881d431ad76f9204c38ce785835
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422187Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812783}

By default, there is no timeout on individual TCP connect attempts (handshakes) other than that enforced by the host OS's network stack.

This change introduces the "TimeoutTcpConnectAttempt" feature, which when enabled will cause slow attempts to fail sooner with ERR_TIMED_OUT.

The time permitted for an individual attempt is a function of three feature parameters, and the estimated network speed:

  clamp(Param("TimeoutTcpConnectAttemptMin"),
        Param("TimeoutTcpConnectAttemptMax"),
        estimated_rtt * Param("kTimeoutTcpConnectAttemptRTTMultiplier"))

In other words, the timeout will be between "TimeoutTcpConnectAttemptMin" and "TimeoutTcpConnectAttemptMax", depending on how fast we think the network is.

Bug: 1123197
Change-Id: Ibfcf8b26b5b424bf9d12f5604294d7a99950f10f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436349
Commit-Queue: Eric Roman <eroman@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812782}

Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202010010800_RC00.html

https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/NmnsodASCDlnL1R0fAI_q3in9QdwqYpagivmAet3MhcC

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll
Please CC media-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;luci.chrome.try:linux-chromeos-chrome-easwa
Bug: b/152809957
Tbr: media-app@grotations.appspotmail.com
Change-Id: I019596acc7614f8909107c5c3ad4140c5ecad2d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443031Reviewed-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@{#812781}

This updates the strings and removes the link to the help center, as
there is no separate section on signing in. All references and
screenshots have been updated.

Tbr: khorimoto@chromium.org
Change-Id: I06e748283d6560cc14098eba969dd4814bac53e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442627Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Richard Knoll <knollr@chromium.org>
Commit-Queue: Peter Beverloo <peter@chromium.org>
Auto-Submit: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812780}

This reverts commit aafb0b22.

The failing media tests were fixed by bbb9f524
so they can be re-enabled.

Bug: 1131181
Change-Id: Ieb18d5fd79a3b4353858eb321dd8eda4f4ea7514
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442770Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Reviewed-by: Haiyang Pan <hypan@google.com>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812779}

chrome://extensions/ supports inspect views for the background page.
This CL adds the capability to inspect views for an inactive service
worker.

Bug: 1107596
Change-Id: I2b021659c60b07dbc455c1ed046fa4738bea8ffb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425191
Commit-Queue: Ghazale Hosseinabadi <ghazale@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812778}

This avoids polluting your checkout when running run_wpt_tests.py
locally.

Bug: 1132436e
Change-Id: I1bbdb91e9f34b8634913e5e9d56d97f42e67e954
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441124Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812777}

Grant Kaleidoscope and it's subframes autoplay by
default.

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

Fixes typo in histogram name in AccountPickerDelegate, which was
recording "Signin.AndroidAccountConsistencyPromoAction" instead of
"Signin.AccountConsistencyPromoAction".

Bug: 1134177
Change-Id: I58bd063ffff39877b0be8db77e7730c983b6fed8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443012
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Auto-Submit: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812775}

This adds interactive UI tests for all ways of terminating a
snoozeable promo:
* User clicking the snooze button
* User clicking the dismiss button
* Closing the promo through FeaturePromoController
* Directly closing the promo's widget (as if the user pressed ESC)

The tests verify the snooze profile prefs are set correctly after
these operations.

Bug: 1121399
Change-Id: I5ab462d51abc771edc0d27afb5093d756e7e3ccd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441115
Auto-Submit: Collin Baker <collinbaker@chromium.org>
Commit-Queue: Wei Li <weili@chromium.org>
Reviewed-by: Wei Li <weili@chromium.org>
Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812774}

https://android.googlesource.com/platform/external/perfetto.git/+log/f01bf538a4ff..bce69fefbe63

2020-10-01 fmayer@google.com Merge "Pull heapprofd simpleperf into output directory."
2020-10-01 hjd@google.com Merge "Revert "ui: Add gn rule to copy protobufjs light""
2020-10-01 hjd@google.com Merge "ui: Improve track names"

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

Allows clients to implement the BatteryChargeStatusObserver interface
and register themselves as an observer in order to receive updates about
battery charge status.

Bug: 1128204
Change-Id: I7a6d87c44248de132e8318ca77a83ce20263df95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427424
Commit-Queue: Bailey Berro <baileyberro@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812772}

So that the inline size gets correctly calculated inside a flex box.

R=ikilpatrick@chromium.org, mstensho@chromium.org

Bug: 1083010
Change-Id: Idcdab256e134dfe2c344ee94a27d24e287d0a085
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442629
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812771}

Enable Destination Dialog printer status flag by default.

Bug: 1123754
Change-Id: If39c5de9b1ba7a33ac6b0a7fe2a3fb4a2223f4ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443070
Commit-Queue: Gavin Williams <gavinwill@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812770}

When the server closed a server-initiated bidirectional stream, Blink
would send a reset. Fix it by tracking state in BidirectionalStream so
that we don't send a reset after receiving a fin.

The state tracking is adequate to fix known bugs but is not yet
comprehensive. A followup CL will make the state machine robust.

BUG=1123772

Change-Id: I5679c0fc1a07c674486f6c7f9901ab962f06fef9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2440087
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812769}

The default unset state is now an in-between state where TLS 1.0 and 1.1
fail, but the error is bypassable. (In the future, the minimum version
will truly be set to TLS 1.2.)

Bug: 1128976
Change-Id: I664b6279789cdc79a358cfe3e241e921d236da58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441656
Commit-Queue: David Benjamin <davidben@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812768}

During selector parsing, whenever we encounter :is or :where, we set a
flag which disallows ShadowDOM v0 selector features (/deep/, ::content
and ::shadow). And conversely, whenever we encounter a ShadowDOM v0
feature, we disallow :is and :where.

Bug: 568705
Change-Id: If11d20b4fe93c82519e2a6ee780e68f62d3f4789
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438989
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812767}

The cache-add.https.html WPT tests became flaky after landing
crrev.com/c/2429308.  The flakes were due to crashes accessing a vector
element beyond its length.  I believe this is due to:

  DCHECK(!blob_list_[index]);

Which is performed before we check to see if we are already stopped.
Since we clear this vector when stopped this DCHECK will crash if a
completion comes in right after aborting.

This CL moves the DCHECKs below our stopped check.  It also explicitly
sets the stopped state when successfully complete as well.

Bug: 1134021,1130781
Change-Id: I075f2daca252ac78a93d5e3991f44389adcf9689
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443069Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812766}

https://swiftshader.googlesource.com/SwiftShader.git/+log/5e947adaf26e..02818d1fdd05

2020-10-01 swiftshader.regress@gmail.com Regres: Update test lists @ 5e947ada

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/swiftshader-chromium-autoroll
Please CC swiftshader-team+autoroll@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_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: None
Tbr: swiftshader-team+autoroll@google.com
Change-Id: I624402a84150be5ac74e5d67ade523e4462ab3f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442721Reviewed-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@{#812765}

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll
Please CC cr-fuchsia+bot@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

Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
Tbr: cr-fuchsia+bot@chromium.org
Change-Id: I24e14b24bf1269f77ba6ebe08874c528a6a54a50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443035Reviewed-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@{#812764}

It was possible for the buffer to be zero-sized and initialize an
std::string with a nullptr. Always check the written length before
constructing a string. This matches the logic in other functions such as
glGetShaderSource.

Bug: chromium:1130367
Change-Id: I8f53cbc585ac8b294d657432dfb43c0946f8bb66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441739Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812763}

Since ScopedSVGPaintState no longer creates/sets up a new PaintInfo
there's no need for GetPaintInfo() an more. Replace usage of it with a
local PaintInfo reference where ScopedSVGPaintState is used.
Also drop the return value from ScopedSVGPaintState::ApplyEffects since
it always return true anyway.

Bug: 109224
Change-Id: I9f6448f3c0bedb731ea899d336f7b3ef318b951a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2440526Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#812762}

Bug: 1133063
Change-Id: I60db20876987e3bc9daebb377e0f6e254e7ccc24
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2439640Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Min Chen <minch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812761}

Bug: 1079466
Change-Id: Ie3a333c5c7a6e16a85fe2734165961b84692b0d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442869Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812760}

Native app windows set special window class and role on Linux/X11.  This
CL enables that for all Linux paths so Ozone would benefit too.

Bug: 1121904
Change-Id: I6df54a92453675060b42a866e2b998f5c655b151
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2440592
Auto-Submit: Alexander Dunaev <adunaev@igalia.com>
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812759}

This regressed in crrev.com/c/2417491 when we added edge padding, but
did not update the request new screenshot code. This had users seeing
an extra black region for a couple of updates before the new screenshot
was taken and placed. Added a couple more tests to
RootWindowDeskSwitchAnimatorTest for Update/End Swipe.

Test: added
Bug: 1111445
Change-Id: I787ecd2c2603e5626dc3d15f5f4ca7f2d5ded33f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438572
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812758}

This CL updates the label that is shown if a user is not signed in, but
has compromised credentials that have been found in the past. This
label is located in the bottom of the compromised passwords section in
the Password Check page.
Screenshots of the compromised passwords section in the Password Check
page after changes:
https://bugs.chromium.org/p/chromium/issues/detail?id=1119752#c20

Bug: 1119752
Change-Id: I85038f38a158daf7e69f098c1cc8ca9cc60a97ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2440585Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Commit-Queue: Irina Fedorova <irfedorova@google.com>
Cr-Commit-Position: refs/heads/master@{#812757}

This policy is used for Edu Coexistence feature and can be only
set for Family Link users. It passes current Terms of Service
version to allow renewal of parent consent if Terms change.

Bug: 1133327
Change-Id: I7840623e59c98892aad59fee4e6222a8e6ae54ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2439020
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812756}

Bug: 1133905
Change-Id: I708677b40bf1d0ce104b263eecb0ea4aacd9a157
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441738
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812755}

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context: https://crbug.com/805539

Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.

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

Tbr: gbiv@chromium.org
Change-Id: If83919511f80e61b506f1637bce12d5b73aef1a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443049Reviewed-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@{#812754}

https://chromium.googlesource.com/angle/angle.git/+log/3d5e8c4c466d..64eb64a034cb

2020-10-01 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SPIRV-Tools from fcb22ecf0f7e to 615fbe6cbc78 (6 revisions)
2020-10-01 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from b042f4e70879 to 5e947adaf26e (4 revisions)
2020-10-01 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-ValidationLayers from e2b329a75b6a to 7a78cc629cca (3 revisions)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC jonahr@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: None
Tbr: jonahr@google.com
Change-Id: I0036d6472459f5417826eb4511703926c7e540c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441852Reviewed-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@{#812753}

Discard thumbnail image data for thumbnails that are far from view to
save memory.

The top margin of 500% was selected with the assumption that every
100% height of the thumbnail bar can fit ~4 thumbnails on an average
screen. Along with the 100% bottom margin and the visible area, around
30 thumbnails worth of image data would be kept in memory at any given
time. Metrics also show that ~90% of PDFs are less than 30 pages.

Bug: 652400
Change-Id: I92126374ad715b502fd6e052246e537d65c407e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2439645Reviewed-by: dpapad <dpapad@chromium.org>
Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812752}