GitLab

The test is failing on CrOS and blocking LKGM updates. This disables it
while we figure out what regressed to allow for LKGM updates.

Bug: 1127052
Change-Id: Ie44baff4b78e495c1af42b4f01e4b6bb6b16071d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404749
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Mitsuru Oshima (Slow: gardener) <oshima@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806261}

...showGooglePasswordManager

Bug: 903249
Change-Id: I8e76df331263ca52846fe48f94b2cbbc412a9ea7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2403282Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806260}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/995a78a14b4b..8ed34138a32b

2020-09-11 jacktfranklin@chromium.org Migrate detached DOM tree heap layout test to e2e
2020-09-11 tvanderlippe@chromium.org Load emulated_devices images from bundle instead of remote

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human
is aware of the problem.

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

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

Bug: chromium:1110817
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I0a5d5dbab5cc6450e7c39cdfcf05b4a78e0405a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406322Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#806259}

https://dawn.googlesource.com/dawn.git/+log/d05e532c6bd2..dbd34449af20

2020-09-11 cwallez@chromium.org Roll third_party/spirv-cross/ bad9dab8d..bdbef7b1f (3 commits)

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

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

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

Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
Bug: None
Tbr: cwallez@google.com
Change-Id: I75c4755f416e75fe6b1d9a8c691e1f7f4f59727a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406326Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#806258}

Starting in macOS 10.14, access to the Safari bookmarks file was
restricted. Chromium didn't notice, and would proceed anyway,
because it assumed that if the file was there, it could be read.
That's not true in the general case anyway, so fix it.

History import from Safari broke many years ago when they moved
to a database for their storage from using a plist. No one realized
that it broke, and since it's access restricted from 10.14 on,
there's no point in fixing it, so this CL removes it.

Bug: 850225
Change-Id: I984ba22a3bcce60ed39cc4fb45331d38f6a6fa94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404529Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806257}

Using wpt-import in Chromium a35a5ecf.
With Chromium commits locally applied on WPT:
8bac593b "Test helper: In answer, apply remote description before local description."
428b08c5 "[Sanitizer API] Add empty config dictionary."


Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

NOAUTOREVERT=true
TBR=smcgruer@google.com

No-Export: true
Change-Id: I76074d99303be0a2333e7c1b9dce4ea06a622c4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404807Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#806256}

This CL refactors how KeySystemConfigSelector::SelectConfig() returns
the results. A Status is added to provided more details on the config
is not supported. The promise rejection messages are also updated to
return different strings on different statuses, which could be useful
or troubleshooting.

Currently we still return the same message for kUnsupportedKeySystem and
kUnsupportedConfigs to avoid updating many tests and potentially affect
existing JS application. In the future we may consider returning
different strings for that case.

For kUnsupportedPlatform we return a different string. This should be
fine for privacy because it'll only be returned when the platform does
not support the key system at all and should not reveal any user/device
information.

Bug: 760720,1126664
Change-Id: I8df167e5c3e86607917d5414a558aae32eed027c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405734Reviewed-by: John Rummell <jrummell@chromium.org>
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806255}

Roll src/net/third_party/quiche/src/ 5c52ad843..0c20b03c8 (3 commits)

https://quiche.googlesource.com/quiche.git/+log/5c52ad843f8a..0c20b03c83cc

$ git log 5c52ad843..0c20b03c8 --date=short --no-merges --format='%ad %ae %s'
2020-09-10 renjietang deprecate gfe2_reloadable_flag_quic_do_not_use_stream_map.
2020-09-10 renjietang deprecate gfe2_reloadable_flag_quic_remove_streams_waiting_for_acks.
2020-09-10 bnc Use IETF application error codes for STOP_SENDING frames.

Created with:
  roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src

R=dschinazi@chromium.org

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

Sometimes gsutil cp operation can fail and cause tree closing. Retry
the operation to mitigate the flaky issue for gcs.

Bug: 1126956
Change-Id: I5f397768745c845f0e61ad87fd1b725e13dfd4fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404395
Commit-Queue: Sven Zheng <svenzheng@chromium.org>
Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806253}

LOG(FATAL) message content is now provided in Crashpad dumps via an
annotation, so there is no longer value in providing markers to allow
the stack to be scanned for the message.

Removing this also avoids the need to update the test not to cause
failures in ASAN builds.

Bug: 802393, 1119821
Change-Id: I6a64778f4da527597e9bb0874fe5764fbf87716a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404926
Auto-Submit: Wez <wez@chromium.org>
Reviewed-by: Joshua Peraza <jperaza@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806252}

Exo gamepad vibration is disabled by default. We add a toggle in
chrome://flags that allows gamepad vibration to be enabled for Exo
clients that support it.

BUG=b:158673179
TEST=manual. Enable flag, and ensure exo client can vibrate gamepad.

Change-Id: I4b64b8eb49bba8c7620af80cdaf2ac17ceb3b6cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402110
Auto-Submit: Prabir Pradhan <prabirmsp@chromium.org>
Reviewed-by: Mitsuru Oshima (Slow: gardener) <oshima@chromium.org>
Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org>
Commit-Queue: Prabir Pradhan <prabirmsp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806251}

This is a reland of 612ba1ba.
This CL removes .gni references to v8_cookie_match_type.{cc,h}
that were overlooked in the original CL.

Original change's description:
> CookieStore: Remove matchType
>
> This change removes matchType option from CookieStoreGetOptions.
> This decision has been discussed here [1], and will
> be revisited after launch to re-evaluate if the option
> is good to have or if we should do a full cleanup of
> the option.
>
> [1] https://github.com/WICG/cookie-store/issues/128
>
> Bug: 1124497
> Change-Id: I845c6e872aa25d138114ccf0b0a74332adeb650d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402132
> Commit-Queue: Ayu Ishii <ayui@chromium.org>
> Reviewed-by: Victor Costan <pwnall@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#805855}

Bug: 1124497
Change-Id: Ie79c492c5ec4f1a2dbcccbe886910500f9e89087
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404123Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806250}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2ec1f5c76dcd..409a8e40330a

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC chanli@google.com,sebsg@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-chromeos-chrome
Bug: chromium:1039881,chromium:1040645
Tbr: chanli@google.com,sebsg@google.com
Change-Id: Iaeecf2709aab0a23ea5cdf3dffce8f39ad926098
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406373Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#806249}

This is to facilitate interface changes in webrtc.
No functional change.

Bug: webrtc:11908
Change-Id: I19f56192ddddc93c0577cb76d163bfbb0ce6175b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406216
Auto-Submit: Tommi <tommi@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806248}

Release_Notes: http://go/help_app-x20/relnotes/Main/help_app_nightly_202009110800_RC00.html

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll
Please CC help-app@grotations.appspotmail.com on the revert to ensure that a human
is aware of the problem.

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

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

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

Every NSP has its own URLLoaderFactory, so this CL adds a simple
counter to that class and when the max is reached, sends
ERR_FAILED to all further requests.

Bug: 1127120
Change-Id: I14b8509bdd2c3a0de371675bfe37520c26fc8064
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404157Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806246}

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

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll
Please CC media-app@grotations.appspotmail.com on the revert to ensure that a human
is aware of the problem.

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

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

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: b/138961540,b/141204984,b/157694064,b/162294373,b/165887300,b/166760020,b/167632244,b/168265185,b/168265337
Tbr: media-app@grotations.appspotmail.com
Change-Id: I099475d47eb6d1021f0eef50f553c2111b512a01
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406265Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#806245}

The format used is already implied by the class name, so remove this
redundant information. Also, add some subclass comments for
consistency and clarity.

Refactoring change only. No functional changes intended.

Change-Id: I25e7d354e22a30ea164c9eab74d2d7f36e5a10e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405565
Auto-Submit: Darwin Huang <huangdarwin@chromium.org>
Commit-Queue: Jarryd Goodman <jarrydg@chromium.org>
Reviewed-by: Jarryd Goodman <jarrydg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806244}

and also remove DIA dependencies.

Setting DLLVM_ENABLE_DIA_SDK=OFF makes LLVM default to the native symbolizer,
which was recently implemented, and allows us to remove the DIA dependency.

There aren't many existing test cases for this, so at the moment it's possible
there are edge cases where the native symbolizer doesn't work.

Change-Id: I8ff395f47869296b01bc3c11f3afdeae102664d5
Bug: 1126219
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399515
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806243}

This change removes the kPasswordManagerOnboardingAndroid feature.
While code-complete, this feature was never launched.

Bug: 983445, 1126051
Change-Id: I4a56e924163805fa28e9ac2e2574e26c1864e508
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2403481
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806242}

Make it behave like a secondary browser icon:
* Always pin it when the flag is set, similar to policy-pinned apps
* Default position is to the right of the browser icon
* Context menu does not contain an "Unpin" item

Also change the app name from "LaCrOS" to "Lacros", since we've settled
on the simpler capitalization and I'm adding a test that references
the name.

Bug: 1127153
Test: added to unit_tests
Change-Id: I08ba806d481580988f2be284d8d1ccb6210ea8ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405737
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Nancy Wang <nancylingwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806241}

Currently, the command line switch "--show-dc-layer-debug-borders"
shows borders for only one overlay. This CL extends the support for
multiple overlays on Windows.

Bug: 1117235
Change-Id: I4ba74a24fa402b5b89411e5c079672f6b9bfbcc9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405559
Commit-Queue: Maggie Chen <magchen@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806240}

This method may try to access the dex file, so ignore strict mode
violations.

Bug: 1105096
Change-Id: I4afe88888ec8de39e7c4ea9c1ee89e1dba9ce2f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404379Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806239}

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

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

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

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

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

Tbr: gbiv@chromium.org
Change-Id: I18605f14aec2ffe24bb2155467c353d1cb05e9ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406328Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#806238}

Implemented calculating current time based on multiple scroll offsets
for both blink and cc ScrollTimeline.


Bug: 1094014
Change-Id: I1c724a1a5191bfa36b91926c1c30a1385cfee10c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2387079Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#806237}

AX-Relnotes: N/A
Change-Id: Id6b8b37f5dadabf689aceafda8fd8f5636fbfabe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406374Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806236}

Bug: 1123883,1124757,1125186
Change-Id: I9caf47c94551c2edfb9221fce8f3105f9563aa08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405938
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Auto-Submit: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806235}

These compile targets are currently specified in recipe configuration.

Bug: 1091004
Change-Id: Ie69bf59618152a9f0efa7e267c7ed37bf6816a5c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391511
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806234}

We've been using the UCRT symbols since 2016, but the documentation was
never updated.

Change-Id: I2e4f6e7378d1be2d1091b2f0b0f04ce2113ae3c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404688Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Benoit L <lizeb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806233}

Bug: 1124111
Test: manual test
Change-Id: I63646022f816c26ea001797c3bccfefa0c8f1b77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380437
Commit-Queue: Li Lin <llin@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806232}

Enables the ConversionMeasurement browser process feature in tests.
This also enabled the dependent ConversionMeasurement blink runtime
feature in tests as well.

Change-Id: Ie20e39737615f7dbe4ab54fc0275c5848a7b4256
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399514
Commit-Queue: John Delaney <johnidel@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806231}

This flag was mistakenly created enabled by default instead of disabled
by default.

Bug: 1127308
Change-Id: Ie20fbbf5ad63081f8b106ebe5066e98a8f3d9063
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404792
Commit-Queue: Robbie Gibson <rkgibson@google.com>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806230}

Tbr: avi@chromium.org

Bug: 1127374
Change-Id: If9430b80dc5d13d2e9e71fd52c4b7730448ccee8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404806
Commit-Queue: sebsg <sebsg@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Chan Li <chanli@chromium.org>
Auto-Submit: sebsg <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806229}

With the rename of permissions policy to feature policy. The
README file needs an update.

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

This replaces direct access to MenuButton in o.c.c.b.toolbar.top/StartSurface* classes with equivalent calls to MenuButtonCoordinator. The significant change required is to move MenuButton interactions out of StartSurfaceToolbarView into SSToolbarCoordinator and Mediator.

Bug:1086676

Change-Id: I36b1f2725e1415d30ffffb3e5743de416b80896c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399576
Commit-Queue: Patrick Noland <pnoland@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806227}

Bug: 1127082
Change-Id: I64ea0a51b703c8094e24fb473189c93f47b6217f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406178
Commit-Queue: Tao Bai <michaelbai@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806226}

This is an experimental CL that delays the firing of a contextmenu event
from long-press to end-of-drag.  This only affects "stationary" drags of
draggable elements (a drag spanning a few pixels is considered
stationary to accommodate shaky finger movements).  Like regular
contextmenu events, the event can be cancelled to suppress the menu.

The change is gated by a web preference.

Bug: 1096189
Change-Id: Ibd3632ef7066315bebd0a1bfac52186112315ef3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340287
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806225}

Following up on
https://chromium-review.googlesource.com/c/chromium/src/+/2404389
which switched trunk builders.

Bug: 1126593
Change-Id: I8a5f7ffc5e91b157d366a38ba0243b5345288e91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405638Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806224}

This CL fixes this bug crbug.com/1127200. Which arise when
`View.setOnClickListener(null)` is called. This causes the view
to become clickable again, even though no click listener exists.

TBR=fhorschig@chromium.org

Bug: 1127200
Change-Id: I0eb0a404346aa97830c29ac0cf4f959c40e06beb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405581Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Commit-Queue: Reda Tawfik <redatawfik@google.com>
Commit-Queue: Ioana Pandele <ioanap@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806223}

The current code assumes that the Multipaste menu shows on the primary
display. This CL implements the logic to calculate the menu anchor
bounds on the secondary display.

Bug: 1117311
Change-Id: Ia42fef183d6bdb16c4a7b3f2b78ac98420de082c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2396599Reviewed-by: David Black <dmblack@google.com>
Commit-Queue: Andrew Xu <andrewxu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806222}