Publish DEPS for 89.0.4389.86

• DEPS[diff]

Incrementing VERSION to 89.0.4389.86

Change-Id: Ibbb69b2c6f4e8e7f7aa69929d2c8f64f4985ef54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740588
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1472}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

[base/allocator] Intercept (v)asprintf() in the shims on Android.

(v)asprintf() allocates internally, and is implemented by libc. This
makes Chrome crash with PartitionAlloc on Android, since the allocated
memory will be freed by PartitionAlloc even though it was not allocated
by it.

Implement (v)asprintf() ourselves, and wrap it.

(cherry picked from commit 24ac7c7f4e0ab53eb46057b5c1df11c1b58d6aa0)

Bug: 1166558
Change-Id: I4b5ce4be55bd818a029009fa9eb37e123df7f2d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629707
Commit-Queue: Benoit L <lizeb@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#844022}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2742488
Reviewed-by: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1471}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• base/allocator/BUILD.gn[diff]
• base/allocator/allocator_shim_override_linker_wrapped_symbols.h[diff]
• base/allocator/allocator_shim_unittest.cc[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1615169103-6c8b2028112b839da439879d4cb929cc05e644d5.profdata to chrome-linux-4389-1615192253-8cba519c0e7336c1d9dc9969a714b52224eaa54a.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I18ae003be65183f9ebe43e9210f3066b4ff0c7d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2742654
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1470}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1615169103-dd5acdd702306c5545f51f101e9938683a8a5d54.profdata to chrome-mac-4389-1615192253-0995bb2926bfa9829208972ed9e1cbd36c6def4b.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I49628f1d8ef0dbeda9079ea766bb742f887f9626
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2742355
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1469}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1615148657-763fb18a937a1e88e4b229fd0ee86fd1312a8775.profdata to chrome-linux-4389-1615169103-6c8b2028112b839da439879d4cb929cc05e644d5.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I457634e92c0843d78a4e58c547e304414e8c0d4f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2742314
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1468}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1615148657-132284490b79f2f9bf8df04b90a7e43ac429235f.profdata to chrome-mac-4389-1615169103-dd5acdd702306c5545f51f101e9938683a8a5d54.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I983fb038f61fc522552283fed981cda773c6209b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2742236
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1467}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1615127767-e366826890fe19cdb534952467cca46255f39d6e.profdata to chrome-mac-4389-1615148657-132284490b79f2f9bf8df04b90a7e43ac429235f.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ifa5aa06b80ab40f0cf6b13ad9c115611027eed8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741547
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1466}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1615127767-c81b4891de371c48bd1dd6abb90e9b8c718a139c.profdata to chrome-linux-4389-1615148657-763fb18a937a1e88e4b229fd0ee86fd1312a8775.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Icba584d0aa810eaaf9cb8d5edbb0db4988d94a80
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741549
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1465}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Incrementing VERSION to 89.0.4389.85

Change-Id: I51ea0e4ecf1f4853a90daef294010e3df618c644
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2739886
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1464}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1615104907-69c97beeb7810d77e55940c4b05de3875ba07416.profdata to chrome-linux-4389-1615127767-c81b4891de371c48bd1dd6abb90e9b8c718a139c.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I72f7aba93d994c719d1db604d4d17c45106b16b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740550
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1463}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1615104907-9eda9123efb4f08963f9cd6ebd7f02add46617bc.profdata to chrome-mac-4389-1615127767-e366826890fe19cdb534952467cca46255f39d6e.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic8d9a6ba185adf834a59f9fd14c0e2de26208e35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741239
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1462}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1615085516-d90438ab5cca501ddf3c2a596be2d657fa712868.profdata to chrome-linux-4389-1615104907-69c97beeb7810d77e55940c4b05de3875ba07416.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic5a10f9cd2fba0b41828cbb135de9f869f740763
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740909
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1461}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1615085516-c4fb0d36a2f86a3f3e10642dfc8d9db357304348.profdata to chrome-mac-4389-1615104907-9eda9123efb4f08963f9cd6ebd7f02add46617bc.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Id492fc3b8b774efb4d72c30cd9d8a1d26c4d0332
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741384
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1460}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1615069458-b41cbda689f7ed813a149f463b95322544e8e281.profdata to chrome-mac-4389-1615085516-c4fb0d36a2f86a3f3e10642dfc8d9db357304348.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Id975f6f5065f23a93998f1423234de6e37634ce7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741499
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1459}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1615069458-509de1bf8b5e2dc50a9dbeb30df27e84db8471bf.profdata to chrome-linux-4389-1615085516-d90438ab5cca501ddf3c2a596be2d657fa712868.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I9c941857ece68c3f64ffcc2f53f45e52e01c7146
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740760
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1458}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1615040817-7372da8380a48807b13c9da4d9dc1b014c08a886.profdata to chrome-mac-4389-1615069458-b41cbda689f7ed813a149f463b95322544e8e281.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Idd851513ef07b8a12d0f9f60373b1852a4fd32fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741317
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1457}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1615040817-d565cbed1f637bd814c3fcc6296f71a50fbd006c.profdata to chrome-linux-4389-1615069458-509de1bf8b5e2dc50a9dbeb30df27e84db8471bf.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I91a00760f3b2fe796ee7acf76452653a3fe3a194
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740076
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1456}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Incrementing VERSION to 89.0.4389.84

Change-Id: I68fac7fcb48b81fd3845efb7e2b2ac41b76d2213
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2739882
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1455}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1615018616-17336072c9353cf0369ce1f2804fe23130c0af7c.profdata to chrome-linux-4389-1615040817-d565cbed1f637bd814c3fcc6296f71a50fbd006c.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ifcafc13d1731acf10e84c117a3d25fa35979cdca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741377
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1454}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1615018616-9e561ab7fdacf7450c2ea35a04c46201948b1339.profdata to chrome-mac-4389-1615040817-7372da8380a48807b13c9da4d9dc1b014c08a886.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ie4cad0c868483475d08f8e4b65b09cc3558044c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741374
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1453}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1614996835-d3343ae9f454a6d00f900bb858ec5e5a30364c51.profdata to chrome-linux-4389-1615018616-17336072c9353cf0369ce1f2804fe23130c0af7c.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic24889ea6a36acd470bdeffc40e035aa1a0867c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741176
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1452}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1614996835-cc97b658b786c0eb7a7bc5e81286942b91d26caa.profdata to chrome-mac-4389-1615018616-9e561ab7fdacf7450c2ea35a04c46201948b1339.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I76b4c52f94a48381da510108955d1a1b5c98b7b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2741175
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1451}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1614983935-ea360b03cab83ef1356a7b771e6cc212ee3c0334.profdata to chrome-linux-4389-1614996835-d3343ae9f454a6d00f900bb858ec5e5a30364c51.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ibe6fbe1ea0901e53f7076926a2349949f6aaec9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740956
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1450}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1614983935-b594ef7eae1661599a1c92b140c52d05fa621fc5.profdata to chrome-mac-4389-1614996835-cc97b658b786c0eb7a7bc5e81286942b91d26caa.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: If86fd3219c43624a14cb8302a21bf746ee70cb5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740724
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1449}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1614953495-9c69954607b6d2794256e3e51aa300070e5257a8.profdata to chrome-linux-4389-1614983935-ea360b03cab83ef1356a7b771e6cc212ee3c0334.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I803ed4789772b7e1477c20d3dc630f0bd5d3fe16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740184
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1448}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1614953495-e55b40aefaf4797ea74748a85feec65e74550bdf.profdata to chrome-mac-4389-1614983935-b594ef7eae1661599a1c92b140c52d05fa621fc5.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I61cb9f5be8f4c7c598d2cc57e019d54974dc06a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740181
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1447}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Incrementing VERSION to 89.0.4389.83

Change-Id: I286599de31728723f317695b53a48ee59881dde2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2739078
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1446}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

[iOS][Biometric Auth] Disable forced passcode for autofill

(cherry picked from commit 2d8d10906290dd843983e300d5d1ce88ead6334b)

Bug: 1184617
Change-Id: I34df01309056997c419ef96db1b7890314dad4da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2736935
Reviewed-by: Robbie Gibson <rkgibson@google.com>
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Commit-Queue: Javier Flores <javierrobles@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859856}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2739868
Auto-Submit: Javier Flores <javierrobles@chromium.org>
Reviewed-by: Bindu Suvarna <bindusuvarna@google.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1445}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ios/chrome/browser/ui/autofill/form_input_accessory/form_input_accessory_mediator.mm[diff]
• ios/chrome/browser/ui/autofill/manual_fill/manual_fill_injection_handler.mm[diff]

[a11y] Accessibility bridge rejects actions on invalidtrees.

This change rejects actions performed on invalid accessibility trees by
checking if the tree still exists.

Test: Does not crash during manual test of b/2736858
Bug: 1180440
Bug: b/2736858

(cherry picked from commit 1e82f57730279b46a9aed5ce386fd29dce2ce56c)

Change-Id: I12ca7b9ac53e0a026ce62b29b165f4cb169dd403
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2736858
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Sharon Yang <yangsharon@chromium.org>
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859902}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2739440
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1444}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• fuchsia/engine/browser/accessibility_bridge.cc[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1614932097-8290b84a2985c463fb69214f5cbb305878c25166.profdata to chrome-linux-4389-1614953495-9c69954607b6d2794256e3e51aa300070e5257a8.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Id0f7278b4faf014a16e0735af6c1bb868701a033
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740165
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1443}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1614932097-83f3d0ea3e4992f371b0ac4c806601e164bf7590.profdata to chrome-mac-4389-1614953495-e55b40aefaf4797ea74748a85feec65e74550bdf.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I2eb3f37ddd4d7d2fda5f3f0a7891697068d5935c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2740158
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1442}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

[M89] [sheriff] Disable ExtensionInstallDialogViewInteractiveBrowserTest.InvokeUi_ManyPermissions on Windows for real.

R=​bsep@chromium.org

(cherry picked from commit 39e3d27946af47b9eaba725078143502fb228038)

Bug: 1166152
Change-Id: Id951f8454e6f15f2e7401bf92ab5590cd95c218b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626050
Auto-Submit: François Doray <fdoray@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#844024}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2723208
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1441}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/browser/ui/views/extensions/extension_install_dialog_view_browsertest.cc[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1614914567-dd04a4cf9faa78db10c1d32f68a0461c8e863955.profdata to chrome-mac-4389-1614932097-83f3d0ea3e4992f371b0ac4c806601e164bf7590.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Idade7362515470a690abda3207adc66ce9f833c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2739755
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1440}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1614914567-516d3368c36bc74f66aa1449175bbc0b817efca6.profdata to chrome-linux-4389-1614932097-8290b84a2985c463fb69214f5cbb305878c25166.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ia8bd5fb5d8c09ea06a112c2e314f03b495a91072
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2739754
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1439}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1614901254-879811d49103c815c97aa100ad9d1c3cc6b21f86.profdata to chrome-mac-4389-1614914567-dd04a4cf9faa78db10c1d32f68a0461c8e863955.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ib2a19a0f0ab1a018a88ede14f3269b1b62014b63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2738370
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1438}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1614901254-0fefc26ba49507cf1be184c7d692bd22d25b63b4.profdata to chrome-linux-4389-1614914567-516d3368c36bc74f66aa1449175bbc0b817efca6.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I6bbaf78c3614cef4492a2d5fe79c5c98206cc606
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2739357
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1437}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-4389-1614360415-729cac66dd11a77cbc1c3732108ebc04ae705ed1.profdata to chrome-mac-4389-1614901254-879811d49103c815c97aa100ad9d1c3cc6b21f86.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I495aa5ef7068f3b6eee50d47dcdc5344e09d89c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2737031
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1436}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1614685055-d26d64f2c1cdbd0bbfcf6c30c28fa131f3dde5ce.profdata to chrome-linux-4389-1614901254-0fefc26ba49507cf1be184c7d692bd22d25b63b4.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@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-m90.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Id3bd064a350c71ada1df5afa747cc7ef6b2f3286
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2737943
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1435}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

Merge: remoting: systemd fixes.

It turns out allowing systemctl to prompt for authentication itself runs
into a couple of issues. First, it won't fall back to TTY-based auth if
stdin is not a TTY. Since start-host redirects stdin to /dev/null when
running the python script, this caused start-host not to work without a
running polkit agent. Second, it appears some less-common systemd
configuration causes systemctl to prompt the user for a password three
times when performing `enable --now`. This is both confusing and
annoying for the user. This commit works around the issue by invoking
systemctl as root using either pkexec or sudo.

This commit also fixes a missed s/--systemd/--new-session/.

(cherry picked from commit 17b31dd94103e83e8b25d30d60239eb6c770266a)

Bug: 1184023
Change-Id: Id3f276017de3c0013e8dc2bd33b0767e16d57db5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733257
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859489}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2738708
Reviewed-by: Erik Jensen <rkjnsn@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1434}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• remoting/host/installer/linux/chrome-remote-desktop@.service[diff]
• remoting/host/linux/linux_me2me_host.py[diff]

Incrementing VERSION to 89.0.4389.82

TBR=pbommana@chromium.org

Change-Id: Iadc1f10e61b8a3966696b0a40278fd464ae34b98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2737703
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1433}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

GMC: Enable Global Media Controls for ChromeOS

This CL enables the Global Media Controls for ChromeOS.

(cherry picked from commit eeecc6256c8f9e1f70e729a0088b793692f5bd37)

In addition to the cherry-picked commit, this sets the default feature
param to "default-unpinned" to ensure that we are in quick settings by
default.

Bug: 1184029, 1182564
Change-Id: I4b2395ed08751e414ead9e69c1bf0fb1b6f2af0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2737954
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1432}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ash/media/media_notification_controller_impl_unittest.cc[diff]
• ash/system/media/media_tray_unittest.cc[diff]
• media/base/media_switches.cc[diff]

[sheriff] Disable flaky CartHandlerTest.TestEnableFakeData

(cherry picked from commit df4643c8eb27f380f6e2bed43651d42dd4ab54f5)

Bug: 1175279
Change-Id: I171cfa6ed1e0797c40adeb50b9f5d5c99a554eaa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2731572
Auto-Submit: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859466}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2737958
Commit-Queue: Peter Boström <pbos@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Peter Boström <pbos@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1431}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/browser/cart/cart_handler_unittest.cc[diff]

Incrementing VERSION to 89.0.4389.81

TBR=mmoss@chromium.org

Change-Id: I6e0c9e038ba5821e66685d0620402bcdb196c9b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2737437
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1430}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

Incrementing VERSION to 89.0.4389.80

TBR=bindusuvarna@chromium.org

Change-Id: I4a6daa65ccb58e0a56599be97d33e82deb4ab1cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2737814
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1429}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

[Sheriff] Disable flaky test on TSAN

See linked bug for details.

TBR=finnur@chromium.org

(cherry picked from commit 97eb3a2fe9731caec7b0f1e16c4736a3a48e8d8f)

Bug: 1163813
Change-Id: I536916958e5dcec1a25b631b6ffff5d906ec5a71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633670
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Auto-Submit: Yi Gu <yigu@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#844226}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2737516
Commit-Queue: Peter Boström <pbos@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Auto-Submit: Peter Boström <pbos@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1428}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/browser/extensions/extension_checkup_unittest.cc[diff]

Call SetNeedsAssignmentRecalc in HTMLSlotElement::ChildrenChanged

(cherry picked from commit 3f7c402dfd0acf0277dc4069ee453b4f54be8eb2)

Bug: 1184357
Change-Id: Id9e804e5762ac6c40ba1be0620401d219d6f4d90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2734104
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859652}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2736595
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1427}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• third_party/blink/renderer/core/html/html_slot_element.cc[diff]
• third_party/blink/renderer/core/html/html_slot_element.h[diff]
• third_party/blink/web_tests/external/wpt/dom/slot-recalc-ref.html[Added - diff]
• third_party/blink/web_tests/external/wpt/dom/slot-recalc.html[Added - diff]

Stop preloading vr module to avoid racey crash

It was possible for the vr split to be loaded in the background thread
before the application ClassLoader had been replaced with the chrome
ClassLoader. This was causing issues in the BundleUtils logic which
makes sure ClassLoaders have the correct parent. For now, we will just
disable vr preloading entirely since it is safer for merging to stable,
but we should be able to preload safely after the application
ClassLoader has been replaced.

(cherry picked from commit ec49b049fa7dd5fae03521c01e6e97abcc0fb5a2)

(cherry picked from commit 0b9ed54859eeefc8051be9428cd337ab6cc08bed)

Bug: 1184300
Change-Id: I87461e1093d1acbd47c11a7dfed8e44598a9234e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733370
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Auto-Submit: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Original-Original-Commit-Position: refs/heads/master@{#859594}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733374
Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Original-Commit-Position: refs/branch-heads/4435@{#3}
Cr-Original-Branched-From: f3c257e9298faf4da38daa674571c7ad08873106-refs/heads/master@{#859168}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733811
Reviewed-by: Ben Mason <benmason@chromium.org>
Commit-Queue: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1426}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/android/java/src/org/chromium/chrome/browser/base/SplitChromeApplication.java[diff]

Don't crash on reentrant RunMoveLoop call.

(cherry picked from commit 4b05247f43d592ce748933963df923d9a40705f8)

Bug: 1173484
Change-Id: Ia75b200d2826586080c26089751bef1d12c8fbce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2680089
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#851799}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2735715
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1425}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/browser/ui/views/tabs/tab_drag_controller.cc[diff]

[m89][mac][infra] Align 'Mac10.15 Tests' with 'Mac10.13 Tests'

The test configs in `testing/buildbot/chromium.mac.json` are now the
same between these 2 builders. This is a preparation to make 'mac-rel'
mirror 'Mac10.15 Tests' instead of 'Mac10.13 Tests' for correct naming.

(cherry picked from commit 69e2e00fe0069c9e5eb41bfbef91c6776d8c2790)

No-try: true
Bug: 1171053, 1184461
Change-Id: I8125c402e332a3584ce2aefef3ba1dccde735364
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2707314
Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
Reviewed-by: Lindsay Pasricha <lindsayw@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#855927}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733752
Reviewed-by: Zhaoyang Li <zhaoyangli@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1424}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• testing/buildbot/chromium.mac.json[diff]
• testing/buildbot/test_suite_exceptions.pyl[diff]

Fix download resumption in reduced mode

In reduced mode, we need to call EnsureDownloadSystemInitialized with a
nullptr

BUG=1171071

(cherry picked from commit d7a7ca93627ac2a3fa32d4f05f92e79dd6f58daf)

Change-Id: Ia07ae3483f11e5f09dab1d81d261d61a8e727cf0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2652030
Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#847756}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2734032
Cr-Commit-Position: refs/branch-heads/4389@{#1423}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/browser/download/android/download_startup_utils.cc[diff]

Add WebLayer getters for referrer and form submission.

(cherry picked from commit 3366d0d46a7f8051841648a912afb26cfbe09f6e)

Bug: 1176105
Change-Id: I6b3573d977ff2d440d0d3c28187d96181d935afb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2714426
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#856898}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733390
Auto-Submit: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1422}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• weblayer/browser/android/javatests/src/org/chromium/weblayer/test/NavigationTest.java[diff]
• weblayer/browser/java/org/chromium/weblayer_private/NavigationImpl.java[diff]
• weblayer/browser/java/org/chromium/weblayer_private/interfaces/INavigation.aidl[diff]
• weblayer/browser/navigation_impl.cc[diff]
• weblayer/browser/navigation_impl.h[diff]
• weblayer/public/java/org/chromium/weblayer/Navigation.java[diff]
• weblayer/public/navigation.h[diff]

Enable chromium M89 CQ to trigger chrome M90 builders.

The PGO autoroller situation is a little wonky right now, so the
autoroller running on the stable branch needs to trigger the chrome beta
builders. This should be fine since it should still check out the ref of
the gerrit CL, it'll just result in a mixed history.

Bug: 1183798
Change-Id: I909f81dd814c03704affcb36f0b7f5406acc2d33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2734097
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1421}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• infra/config/generated/commit-queue.cfg[diff]
• infra/config/subprojects/chromium/try.star[diff]

[Merge to M89][Multipaste] Restrict the size of the web contents from the copied HTML

This CL caps the maximum size of the web view rendered from the copied
HTML code. Without doing it, excessive CPU & memory resources will be
consumed if a user copies a big web page.

The maximum size used by this CL which is 2000*2000 should cover the
majority of use cases. In addition, a menu entry's width (around 200)
or height (around 50) are much less than the maximum width (2000) or
height (2000) respectively. Hence, the size restriction should not
bring any damage on UI.

TBR=xiyuan@chromium.org,newcomer@chromium.org,dmblack@chromium.org

(cherry picked from commit 6cf7a7da30578855a44aadade98695ab29d826d5)

Bug: 1182831
Change-Id: I5d8dce6b1963d25fca96c88b5602df46ed94d0c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2727935
Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: David Black <dmblack@google.com>
Commit-Queue: Andrew Xu <andrewxu@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859157}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733416
Auto-Submit: Andrew Xu <andrewxu@chromium.org>
Reviewed-by: Andrew Xu <andrewxu@chromium.org>
Commit-Queue: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1420}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/browser/ui/ash/clipboard_image_model_request.cc[diff]

cros: Make AcceleratorHistory higher priority

Background: AcceleratorFilter keeps track of pressed keys through
AcceleratorHistory. AcceleratorFilter is a PreTargetEventHandler on
Shell.

AcceleratorController uses AcceleratorHistory to ensure proper
accelerators are triggered. For example, a user could press:
1. Search key
2. Release Search
  - At this point, AcceleratorHistory is used to determine that no
    other keys are pressed as Search is released.

There are various issues where other PreTargetHandlers handle KeyEvents,
preventing AcceleratorHistory from seeing them. This means that in some
cases (crbug.com/1174603, crbug.com/1172970) AcceleratorHistory is
tricked into thinking keys are always pressed.

The control flow for AcceleratorController is:
 - AcceleratorHistory learns of a KeyEvent
 - AcceleratorController then uses AcceleratorHistory to validate
   certain accelerators.

The Solution:
 - Make AcceleratorHistory observe aura env independently of
   AcceleratorFilter.

AcceleratorHistory then gets a guarantee that no other
PreTargetEventHandlers will prevent it from seeing events.

This is safe because AcceleratorHistory does not ever SetHandled() or
StopPropagation() on events. It should have no effect on other areas of
the code.

In addition, AcceleratorHistory still learns of the event prior to
its utilization by AcceleratorController.

(cherry picked from commit c41080a7c462ce0e5fc772f6c5e4959e4fbbeb30)

Bug: 1174603
Change-Id: Ic3469f9bcf8f3dd14200bf09aa0bff444300f910
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2724033
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Alex Newcomer <newcomer@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#858775}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2730717
Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1419}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ash/accelerators/accelerator_controller_impl.cc[diff]
• ash/accelerators/accelerator_controller_unittest.cc[diff]
• ash/accelerators/accelerator_filter_unittest.cc[diff]
• ash/clipboard/control_v_histogram_recorder.cc[diff]
• ash/shell.cc[diff]
• ui/base/accelerators/accelerator_history.cc[diff]
• ui/base/accelerators/accelerator_history.h[diff]
• ui/wm/core/accelerator_filter.cc[diff]
• ui/wm/core/accelerator_filter.h[diff]

Incrementing VERSION to 89.0.4389.79

TBR=srinivassista@chromium.org

Change-Id: I84a51c402514dea7b197a859f225482ad51f832c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733521
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1418}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

Wi-Fi Sync: Default autoconnect to enabled when unspecified.

(cherry picked from commit a544facba7da0ffeec9c30e9284edadfbc62febd)

Bug: 1177342,b:180854680
Change-Id: I61cb6baffe8e042876e42a260d5f1a61f336f184
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2723611
Commit-Queue: Jon Mann <jonmann@chromium.org>
Reviewed-by: Azeem Arshad <azeemarshad@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#858350}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733798
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Jon Mann <jonmann@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1417}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chromeos/components/sync_wifi/network_type_conversions.cc[diff]

Active user takes ownership of networks on password updates.

When a wifi network is updated with a new password, through sync
or system ui, the network is now "owned" by active account for
purposes of sync.  Before this, user updates to these networks would
not get saved to sync and could get overwritten on later updates.

(cherry picked from commit f7b9a3aec9711f6420e5209d6d2e9c001d4bbb24)

Bug: 1177342,b:180854680
Change-Id: Ibb2baf90c18f805dd648cb996aa10bc8648189a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2723199
Reviewed-by: Azeem Arshad <azeemarshad@chromium.org>
Commit-Queue: Jon Mann <jonmann@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#858333}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733797
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Jon Mann <jonmann@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1416}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chromeos/network/network_metadata_store.cc[diff]
• chromeos/network/network_metadata_store_unittest.cc[diff]

Prevent showing notification when Wi-Fi Sync is not visible in settings.

It can take some time between when the flag is enabled and the feature has been registered as "supported" with cryptauth.  This change prevents showing the announcement notification during this time.

(cherry picked from commit 26f0b3df81a802ba63a2806b66d05a6862bf230e)

Bug: 1182329,b:180854680
Change-Id: Iad7a482413b36bba2c9568db38acf758c219298b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2732228
Commit-Queue: Jon Mann <jonmann@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859523}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733796
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Jon Mann <jonmann@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1415}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chromeos/services/multidevice_setup/wifi_sync_feature_manager_impl.cc[diff]
• chromeos/services/multidevice_setup/wifi_sync_feature_manager_impl_unittest.cc[diff]

[M89]Use the chrome.exe path instead of the directory.

Currently the the sandboxed shortcut parser compares
the Chrome executable path with the shortcut target
path before allowing it to be reset. However, the
shortcut target path normally includes "chrome.exe"
in its target path. Thus, it should be added into
the path set to be checked.

This CL also updates the working-directory to be
the chrome exe directory.

(cherry picked from commit 4924f2c156d1159988da7c93b25ea4abfd707d4b)
TBR=joenotcharles

Bug: 1174512
Change-Id: Ie742146fa347f47ed41b478a84e3a6c2276f6da2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2691247
Commit-Queue: Bettina Dea <bdea@chromium.org>
Reviewed-by: Joe Mason <joenotcharles@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859084}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2732996
Reviewed-by: Bettina Dea <bdea@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1414}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/chrome_cleaner/chrome_utils/chrome_util.cc[diff]
• chrome/chrome_cleaner/chrome_utils/chrome_util.h[diff]
• chrome/chrome_cleaner/chrome_utils/extensions_util.cc[diff]
• chrome/chrome_cleaner/components/reset_shortcuts_component.cc[diff]
• chrome/chrome_cleaner/components/reset_shortcuts_component.h[diff]
• chrome/chrome_cleaner/components/reset_shortcuts_component_unittest.cc[diff]
• chrome/chrome_cleaner/components/system_report_component.cc[diff]
• chrome/chrome_cleaner/mojom/parser_interface.mojom[diff]
• chrome/chrome_cleaner/parsers/broker/lnk_parser_sandbox_setup_unittest.cc[diff]
• chrome/chrome_cleaner/parsers/shortcut_parser/broker/sandboxed_shortcut_parser.cc[diff]
• chrome/chrome_cleaner/parsers/shortcut_parser/broker/sandboxed_shortcut_parser.h[diff]
• chrome/chrome_cleaner/parsers/shortcut_parser/broker/shortcut_parser_api.h[diff]
• chrome/chrome_cleaner/parsers/shortcut_parser/sandboxed_lnk_parser_test_util.cc[diff]
• chrome/chrome_cleaner/parsers/shortcut_parser/sandboxed_lnk_parser_test_util.h[diff]
• chrome/chrome_cleaner/parsers/shortcut_parser/target/lnk_parser.cc[diff]
• chrome/chrome_cleaner/parsers/shortcut_parser/target/lnk_parser.h[diff]
• chrome/chrome_cleaner/parsers/shortcut_parser/target/lnk_parser_unittest.cc[diff]
• chrome/chrome_cleaner/parsers/target/parser_impl.cc[diff]
• chrome/chrome_cleaner/parsers/target/parser_impl_unittest.cc[diff]
• chrome/chrome_cleaner/scanner/scanner_controller.cc[diff]

[Fuchsia] Fix OutputPresenterFuchsia to send non-decreasing timestamps

Sometimes Scenic was disconnecting WebEngine because the timestamps
it was getting in Present() were out of order. Updated
OutputPresenterFuchsia to guerantee that this never happens.

(cherry picked from commit 068f3d0568ce94bddabdbb3644ddd379d886cf33)

Bug: 1181528
Change-Id: I434a0627af2f72a92f4d3518b8095a10b4a59b67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2719485
Auto-Submit: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#859100}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733636
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1413}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• components/viz/service/display_embedder/output_presenter_fuchsia.cc[diff]
• components/viz/service/display_embedder/output_presenter_fuchsia.h[diff]

Condition Price Tracking on MBB Consent.

This CL adds another condition (MBB) for Price Tracking eligibility.
This doesn't have an impact on the existing tests since they're
controlled by the static (visible for testing) flag.

(cherry picked from commit 5b8fbaffb0e11e4e2851668eb063b3a344d72064)

Bug: 1180234
Change-Id: I278da9f8c16c94e775b58c14bb4dea2a985ba382
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2707134
Commit-Queue: Ayman Almadhoun <ayman@chromium.org>
Reviewed-by: Yue Zhang <yuezhanggg@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#856857}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733101
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1412}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/android/features/tab_ui/java/src/org/chromium/chrome/browser/tasks/tab_management/PriceTrackingUtilities.java[diff]
• chrome/android/features/tab_ui/javatests/src/org/chromium/chrome/browser/tasks/tab_management/PriceTrackingUtilitiesTest.java[Added - diff]
• chrome/android/features/tab_ui/tab_management_java_sources.gni[diff]

[fuchsia] Add multiple component support for audio/video capturers

Allow CastRunner to have multiple components work with the audio and
video capturers.

(cherry picked from commit 1d7fa07f533d072700606d483405060ad423744a)

Bug: 1171057
Change-Id: Ib501322f5de8eddec699a02be02cf478e0ebd6d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2657874
Auto-Submit: Sharon Yang <yangsharon@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Sharon Yang <yangsharon@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#857960}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2733469
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1411}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• fuchsia/runners/cast/cast_runner.cc[diff]
• fuchsia/runners/cast/cast_runner.h[diff]

Incrementing VERSION to 89.0.4389.78

TBR=srinivassista@chromium.org

Change-Id: I0d876ee19dfe880dace3d1fabc9833331867a21b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2730794
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1410}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

[iOS] Guard against grid view item array overrun.

In some cases, it seems like the collection view delegate methods in
GrdiViewController for handing item selection and deselection can be
called with index paths that don't match the item count for the
TabSwitcherItems array. (Specifically, the index path of the (de)selected
item will be one higher than the maximum index of the array).

Given that touches and select/deselect events are handled asynchronously
by UIKit, it's possible that these might be being handled after a model
update (which is synchronous) has changed the size of the items array.
(This does seem unlikely, since model updates should also update the
collection view, so it shouldn't be sending the select/deselect events).

In any case, this CL adds a guard clause to cause calls to
-tappedItemAtIndexPath: no-op if the index path is illegal for the items
array. This should have no user-visible effect, since there's no
tab with that index to be selected.

(cherry picked from commit e58536e2b0a1756a7b9dab419b60b93eb6eea4c6)

Bug: 1163238
Change-Id: I3035bebd270171ef28d75fbbb4f08baa4e8f0caf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2691206
Reviewed-by: David Jean <djean@chromium.org>
Commit-Queue: Mark Cogan <marq@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#855684}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2727968
Reviewed-by: Bindu Suvarna <bindusuvarna@google.com>
Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1409}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ios/chrome/browser/ui/tab_switcher/tab_grid/grid/grid_view_controller.mm[diff]

Incrementing VERSION to 89.0.4389.77

TBR=pbommana@chromium.org

Change-Id: Ifdc147e9d8d3fde1b19abf39a5f3e84e976f558e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2728781
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1408}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

[iOS][MF] Validate web state

And return nil if the webstate is nullptr.

(cherry picked from commit 00d924142fca818e5f8d4285744fa909d8fbc394)

Fixed: 1179611
Change-Id: If8b0fc11d7c0172dce0398de04f14d4fd7e6fd98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2716627
Commit-Queue: Javier Flores <javierrobles@chromium.org>
Auto-Submit: Javier Flores <javierrobles@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#857212}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2729517
Reviewed-by: Bindu Suvarna <bindusuvarna@google.com>
Reviewed-by: Javier Flores <javierrobles@chromium.org>
Commit-Queue: Bindu Suvarna <bindusuvarna@google.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1407}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ios/web/web_state/ui/crw_web_controller.mm[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-4389-1614290320-373d33cbf18eb22e84b14668a584467c2b6064bb.profdata to chrome-win32-4389-1614396420-7c54defc1099a74c50c0a849772a1a652ff14a89.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win32-chromium-beta
Please CC pgo-profile-sheriffs@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:win-chrome-beta
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I8a11ed26a4aabc87a716210bb4621d8e70bbd88a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2726075
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1406}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-4389-1614290320-d3d23b4e3e0402843080ce902ddfacd4694692e5.profdata to chrome-win64-4389-1614396420-3d08e7a5ad8fd34456c7a635c5912da5f1e516b0.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win64-chromium-beta
Please CC pgo-profile-sheriffs@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:win64-chrome-beta
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I3deb9f707bc170dee3f7c52234ef5d6486ef5b9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2726093
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1405}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-4389-1614333145-3fb545b30f8abc065d64d3b5af88abd66c7abb5e.profdata to chrome-linux-4389-1614685055-d26d64f2c1cdbd0bbfcf6c30c28fa131f3dde5ce.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium-beta
Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chrome-beta
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Iea971b894aa2e0857381a5307c4ae0d22a5b9d9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2729143
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1404}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/build/linux.pgo.txt[diff]

[iOS][Settings] Fixes clear browsing data link

Reland: https://crrev.com/c/2720105
'Learn more' isn't always visible depending on the device, sometimes
we have to scroll to make it appear.


This CL fixes the 'Learn more’ link.
It corrects the method name so that the delegate is correctly notified.
It also adds new EG tests and a new action 'TapAtPointPercentage' used
to press the top right corner of the selected element when the link is
displayed on 2 lines.

(cherry picked from commit da3b228f9bf637520c97e050490b66975685d3bb)

Bug: 1179227
Change-Id: I4c4cb1539ce28e85ed168e55187e61b0e80fc8e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2726237
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Commit-Queue: Ewann Pellé <ewannpv@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#858575}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2726251
Cr-Commit-Position: refs/branch-heads/4389@{#1403}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ios/chrome/browser/ui/settings/clear_browsing_data/BUILD.gn[diff]
• ios/chrome/browser/ui/settings/clear_browsing_data/clear_browsing_data_egtest.mm[diff]
• ios/chrome/browser/ui/settings/clear_browsing_data/clear_browsing_data_table_view_controller.mm[diff]
• ios/chrome/test/earl_grey/chrome_actions.h[diff]
• ios/chrome/test/earl_grey/chrome_actions.mm[diff]
• ios/chrome/test/earl_grey/chrome_actions_app_interface.h[diff]
• ios/chrome/test/earl_grey/chrome_actions_app_interface.mm[diff]

[Merge M89] Bento: Save desk names and workspaces after desk reordering

To support desks restore, reordering desks needs to
*1. store the new desk name list in user prefs
*2. save the primary user's active desk index.
3. update window workspace property for all windows in affected desks

To support independent active desks for multi-profile, reordering
needs to
*1. update all affected desk indices in |user_to_active_desk_index_|.
2. allow the secondary user to update primary user's active desk if
such index affected.

Note asterisk (*) marks fixes needed for backward compatibility with
the old behavior in M88 before Bento & Desks Restore M89.

Bug: 1177934
Test: Manual, `ash_unittests --gtest_filter=*DesksRestoreMultiUserTest*`,
and `DesksBentoTest*`.

(cherry picked from commit ebe41a86495cf64e00c17ccc16422074d0ff4228)

Change-Id: I4c6c1fd56d31876633cc479c8eff0a324cc39ada
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2704613
Commit-Queue: Cattalyya Nuengsigkapian <cattalyya@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#858260}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2727578
Cr-Commit-Position: refs/branch-heads/4389@{#1402}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ash/wm/desks/desk_mini_view.cc[diff]
• ash/wm/desks/desks_bar_view.cc[diff]
• ash/wm/desks/desks_controller.cc[diff]
• ash/wm/desks/desks_restore_util.cc[diff]
• ash/wm/desks/desks_restore_util.h[diff]
• ash/wm/desks/desks_unittests.cc[diff]

Incrementing VERSION to 89.0.4389.76

TBR=mmoss@chromium.org

Change-Id: I0415882fe3d84fb34af6586c17725c9527d92f82
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2727308
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1401}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

[M89] ash: Handle nullptr window in WebAuthn request registrar

We noticed that in practice, the window that render_frame_host returns
can be nullptr (e.g. the site is calling IsUvpaa() while navigating to
a new page, causing render_frame_host to be changing). In this case,
we should at least make sure we don't crash on the nullptr window.

Bug: 1165327
Test: Before: site crashes when I click "checkout". After: does not
crash.

(cherry picked from commit 5281afd434b50483ecd8ad30ba0f2c60b9aabf29)

Change-Id: Ib52c06e7d96f6b5c6fc0ae466189986c77af31f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2718926
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Commit-Queue: Yicheng Li <yichengli@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#857971}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2728096
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1400}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ash/in_session_auth/webauthn_request_registrar_impl.cc[diff]
• ash/in_session_auth/webauthn_request_registrar_impl.h[diff]
• ash/public/cpp/webauthn_request_registrar.h[diff]
• chrome/browser/webauthn/chrome_authenticator_request_delegate.cc[diff]

[Merge to M-89][Multipaste] Destruct the multipaste menu views asynchronously

This CL does two things:

(1) Avoid destructing the multipaste menu entries synchronously when
the multipaste menu is closed.

(2) When menu is closed, ClipboardHistoryMenuModelAdapter should
terminate any asynchronous calls on `RemoveItemView()`.

Read the issue for more details.

TBR=xiyuan@chromium.org,newcomer@chromium.org,dmblack@chromium.org

(cherry picked from commit 163c8aba4d4b79a7b0c04bf6fb207d68a6716d28)

Bug: 1181676
Change-Id: I50fc0ab2bf694ab08b428919eec8aff74998f3da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2720645
Commit-Queue: Andrew Xu <andrewxu@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: David Black <dmblack@google.com>
Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#858334}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2724964
Reviewed-by: Andrew Xu <andrewxu@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1399}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ash/clipboard/clipboard_history_controller_impl.cc[diff]
• ash/clipboard/clipboard_history_menu_model_adapter.cc[diff]
• ash/clipboard/clipboard_history_menu_model_adapter.h[diff]
• chrome/browser/ui/ash/clipboard_history_browsertest.cc[diff]

Incrementing VERSION to 89.0.4389.75

TBR=mmoss@chromium.org

Change-Id: I03f6ece20023b02431410c28fbed915423bc1998
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2725821
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1398}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

Incrementing VERSION to 89.0.4389.74

TBR=benmason@chromium.org

Change-Id: Ib3e921b80a8b6ab29b61d1cf83d47896f901ebdd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2726360
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1397}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]

Revert "Use stereo audio processing in stereo calls"

This reverts commit 7e1a20037be948ccd1726dd505ab331f54b76515.

Reason for revert: Causes unexpected regression in peer connections

Fixed: b/180011356

Original change's description:
> Use stereo audio processing in stereo calls
>
> Pipe the number of encoded outgoing channels to the media stream audio
> processor and use it to configure the Audio Processing Module (APM).
> Stereo calls gets audio processing (echo cancellation, noise
> suppression, etc) in stereo. Mono calls will continue to get mono
> audio processing.
>
> Previous behavior was to perform audio processing in mono and upmix
> to two (identical) outgoing channels.
>
> Bug: webrtc:8133
> Change-Id: I97bfa8f6b9736a6e8e0d216c1795d712f075726e
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593122
> Commit-Queue: Gustaf Ullberg <gustaf@chromium.org>
> Reviewed-by: Olga Sharonova <olka@chromium.org>
> Reviewed-by: Guido Urdaneta <guidou@chromium.org>
> Reviewed-by: Henrik Andreasson <henrika@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#842577}

(cherry picked from commit 7d1addbd25b1278206355a402adf625f82d4c8e7)

Bug: webrtc:8133, 1182720
Change-Id: I179092e304767fc0f450000d1d541c877592d876
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2721771
Reviewed-by: Olga Sharonova <olka@chromium.org>
Reviewed-by: Henrik Andreasson <henrika@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#858181}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2723811
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1396}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• media/webrtc/webrtc_switches.cc[diff]
• third_party/blink/public/platform/modules/mediastream/web_media_stream_audio_sink.h[diff]
• third_party/blink/renderer/modules/mediastream/media_stream_audio_processor.cc[diff]
• third_party/blink/renderer/modules/mediastream/media_stream_audio_processor.h[diff]
• third_party/blink/renderer/modules/mediastream/media_stream_audio_processor_test.cc[diff]
• third_party/blink/renderer/modules/mediastream/processed_local_audio_source.cc[diff]
• third_party/blink/renderer/platform/mediastream/media_stream_audio_deliverer.h[diff]
• third_party/blink/renderer/platform/mediastream/media_stream_audio_source.cc[diff]
• third_party/blink/renderer/platform/mediastream/media_stream_audio_source.h[diff]
• third_party/blink/renderer/platform/mediastream/media_stream_audio_track.cc[diff]
• third_party/blink/renderer/platform/mediastream/media_stream_audio_track.h[diff]
• third_party/blink/renderer/platform/peerconnection/webrtc_audio_sink.cc[diff]
• third_party/blink/renderer/platform/peerconnection/webrtc_audio_sink.h[diff]

m89: Makes all accessibility * enable prefs non-synchable

Regressed back in
https://chromium-review.googlesource.com/c/chromium/src/+/1869770

e.g.
-    registry->RegisterBooleanPref(prefs::kAccessibilitySwitchAccessEnabled,
-                                  false);
+  registry->RegisterBooleanPref(
+      prefs::kAccessibilitySwitchAccessEnabled, false,
+      user_prefs::PrefRegistrySyncable::SYNCABLE_PREF);

Spoken feedback seems to be the only one that was spared.
-    registry->RegisterBooleanPref(prefs::kAccessibilitySpokenFeedbackEnabled,
-                                  false);
+  registry->RegisterBooleanPref(prefs::kAccessibilitySpokenFeedbackEnabled,
+                                false);

Prior to that change, none of the prefs were synced. THis change
attempts to pick the subset that makes sense.

R=anastasi@chromium.org, anastasi@google.com, dmazzoni@chromium.org

Bug: 1173010
Change-Id: Ia905987dd9bed139b669420414ab1fabb75cc7ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2707644
Reviewed-by: Anastasia Helfinstein <anastasi@google.com>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#855989}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2717977
Reviewed-by: David Tseng <dtseng@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/branch-heads/4389@{#1395}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• ash/accessibility/accessibility_controller_impl.cc[diff]

Incrementing VERSION to 89.0.4389.73

TBR=govind@chromium.org

Change-Id: I3cacc17e143b94fe49ccc8ef0b0cec83d81c11f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2725651
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/4389@{#1394}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}

• chrome/VERSION[diff]