GitLab

This removes the BluetoothRemoteGattCharacteristic::WriteWithoutResponse
method. There are no longer any users of this method.

BluetoothRemoteGattCharacteristic::WriteRemoteCharacteristic can now be
used instead since it now takes a |write_type| parameter.

This also removes the last use of IsWritableWithoutResponse() so it can
be removed as well.

Bug: 831524
Change-Id: Ib6c929db61bcee732cf0cd1c5822bde8cfa9a8f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2191234Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Vincent Scheib <scheib@chromium.org>
Commit-Queue: David Lechner <david@pybricks.com>
Cr-Commit-Position: refs/heads/master@{#770282}

MediaSource shouldn't know whether we're mirroring or remoting. The MRP
can switch dynamically between the two modes, and that shouldn't cause
the media source ID to change. This CL removes remoting related code in
media_soruce*, which is already unused.

Bug: 1084155
Change-Id: I83d4327c7906004564663c6a1b983aa4baef7676
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207747
Auto-Submit: Takumi Fujimoto <takumif@chromium.org>
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770281}

'release' outputs build products into out/Release, but 64-bit builds
are expected in out/Release_x64 on Windows.

Bug: dawn:376
Change-Id: I6163eecaa71d1145d4fb23911f1d1494b1c80d97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208969Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Austin Eng <enga@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770280}

Bug: 1004855
Change-Id: I27a1f262c470d13aa8b65b3f0df9803685b6e6f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207505Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Mike Wittman <wittman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770279}

Bug: 1084347
Change-Id: I42f54e5c5c5d9630068fbd41c7f2bc12b3fea3fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208363
Commit-Queue: John Lee <johntlee@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770278}

https://chromium.googlesource.com/webm/libvpx.git/+log/1243d2fc27b1..f80e88872394

$ git log 1243d2fc2..f80e88872 --date=short --no-merges --format='%ad %ae %s'
2020-05-15 marpan vp9-svc: Fix key frame update refresh simulcast flexible svc
2020-04-25 neil.birkbeck vp9_firstpass.c: limit mv_limits with MV_MAX in motion_search

Created with:
  roll-dep src/third_party/libvpx/source/libvpx
R=johannkoenig@google.com

Change-Id: I8448ec3654531a69bb3317839420bf9b63b71496
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209123Reviewed-by: James Zern <jzern@google.com>
Commit-Queue: Marco Paniconi <marpan@google.com>
Cr-Commit-Position: refs/heads/master@{#770277}

Get rid of content::InputEvent. Move the mojom traits into blink.

No functional changes intended.

BUG=1073560

Change-Id: I290da213929167aa431af43565a48f69ff288c3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2197336
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770276}

This reverts commit 2a23cb68.

Reason for revert: Causing compile failure on cast audio Linux
https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8879840634138464160/+/steps/compile/0/stdout

Original change's description:
> Scale source window during tab drag-and-drop
> 
> This behavior is very similar to tablet mode tab drags from the native
> tab strip. Some of this code is copied, and some is shared (through
> TabletModeBrowserWindowDragSessionWindowsHider).
> 
> Bug: 1069869
> Change-Id: If5c6f163f7d8af9918be3bc97ca8a91b1df063c1
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202507
> Commit-Queue: Collin Baker <collinbaker@chromium.org>
> Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
> Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#770272}

TBR=oshima@chromium.org,xdai@chromium.org,collinbaker@chromium.org

Change-Id: I145747ecebeee3e51cc4893dc23b231e4f2a5728
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1069869
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209405Reviewed-by: sebsg <sebsg@chromium.org>
Commit-Queue: sebsg <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770275}

This adds a Tab.setData() and Tab.getData() API which allows setting
arbitrary embedder specific data on a tab. This data will be
saved/restored along with other browser data.

Bug: 1079313
Change-Id: Iccc0f17e647c4252768e2b1e69e2c87d9f695de1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2204540Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770274}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/5a7be3da2119..002f97b35a72

2020-05-19 ehmaldonado@google.com Abort fetch, gclient, gsutil.py when update_depot_tools fails on Windows

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

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

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

Bug: None
Tbr: agable@chromium.org
Change-Id: I5b5933fb97e6a5413fbd1c595efe11fcb9364660
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209284Reviewed-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@{#770273}

This behavior is very similar to tablet mode tab drags from the native
tab strip. Some of this code is copied, and some is shared (through
TabletModeBrowserWindowDragSessionWindowsHider).

Bug: 1069869
Change-Id: If5c6f163f7d8af9918be3bc97ca8a91b1df063c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202507
Commit-Queue: Collin Baker <collinbaker@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770272}

Bug: b:146669457
Change-Id: Ia8a760cf10902bcac38af7c0b2fae788f0fca627
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208653Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#770271}

By stripping out META-INF from the test dist_jar(). Turbine was adding
in .class files there, which were confusing proguard.

Also R8's stripping caused test failure. Temporarily disable the
optimization until the next R8 roll fixes the issue.

Bug: 1081443, 1082809
Change-Id: I60676c1f654e8a0d6244493402e51f26ee1de701
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209288Reviewed-by: Sam Maier <smaier@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770270}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/501473c8d1a3..79b9f51cc09d

2020-05-19 tvanderlippe@chromium.org Let NetworkManager.NetworkDispatcher implements the correct interface
2020-05-19 mathias@chromium.org Consistently format CSS color and opacity values
2020-05-19 sigurds@chromium.org Typescriptify NetworkLog

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:1011811,chromium:1079233,chromium:1083142
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I5accd675346011e5773175b15f19643710fdac32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209282Reviewed-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@{#770269}

This allows us to display an AVIF image sequence (i.e., animated image)
in the browser using the file: URL.

This is a follow-up to https://crrev.com/c/2153331.

Please see https://aomediacodec.github.io/av1-avif/#avis-mime-definition
for the Internet Media Type and file extension for AVIF image sequences.

Tested:
net_unittests --gtest_filter=MimeUtilTest.*

Bug: 1071484
Change-Id: Ia4c3996a0956dc480e697b87da8815fc9ca20f4b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207985Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Wan-Teh Chang <wtc@google.com>
Cr-Commit-Position: refs/heads/master@{#770268}

It is unused.

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

Bug: 1083147
Change-Id: I369862dbde6d031e39bac5e57be0bbdf53d5c8b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209057Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Kush Sinha <sinhak@chromium.org>
Commit-Queue: Anastasiia N <anastasiian@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770266}

This CL hooks the componentized Site Settings Fragments into the
SiteSettingsFragmentImpl.

Binary-Size: Site Settings client interfaces require lots of methods
Bug: 1049683
Change-Id: I66afa208bd81ca50052040aabbf427adb37b6be3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2184200Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770265}

This reverts commit d8729e7d.

Reason for revert: win-asan doesn't actually have 'is_asan = true' in
its gn configs. A bunch of other death tests are failing on the same
bot, so no need to disable a test on an effectively dead bot.

Original change's description:
> Disable PrintSettingsDeathTest.IsColorModelSelectedUnknown on Win ASAN
> 
> Death tests as a whole seem to be flaking on Win ASAN. Disable this test
> until crbug.com/1075661 is resolved.
> 
> Bug: 1074293
> Change-Id: I3b4bb4053852c184fb55630202daee552fb03424
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2204418
> Reviewed-by: Lei Zhang <thestig@chromium.org>
> Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#769342}

TBR=thestig@chromium.org,dhoss@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 1074293
Change-Id: Ia0e0b02115ac3f9a8bdb316e35a6771c0ce180b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209400Reviewed-by: Daniel Hosseinian <dhoss@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770264}

Change-Id: Iaf5a5c293ad8f3d9420a2faafbb7588c398a6b5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2195199
Commit-Queue: Joe Mason <joenotcharles@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Sigurður Ásgeirsson <siggi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770263}

This is a reland of 14dee393

Original change's description:
> Invalidate tabstrip layout when the space available for tabs changes.
> 
> Bug: 1075913
> Change-Id: I2d65a4dc4b4b112e367f216b4a71788bdf825bbe
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2185430
> Commit-Queue: Taylor Bergquist <tbergquist@chromium.org>
> Reviewed-by: Dana Fried <dfried@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#769803}

Bug: 1075913
Change-Id: I29784f838e5208db112b51fbd19ab7fd91e42476
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209233Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Taylor Bergquist <tbergquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770262}

Use Browser::Create method instead of Browser constructor.

Bug:1082216

Change-Id: Ifdfb80a0d9baf198a8c6f4498568e10ad2d5f00f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2196667Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Roman Aleksandrov <raleksandrov@google.com>
Cr-Commit-Position: refs/heads/master@{#770261}

NGFragmentItem may use DisplayItem::Id::fragment to support vector
based fragments, which requires PaintController to support a lot of
fragments without performance issues.

Expand DisplayItem::Id::fragment to be wtf_size_t. This won't increase
size of DrawingDisplayItem by adjusting the order of fields.

Convert the display item map that mapped from DisplayItemClient* to a
vector of indices, to a map that maps from DisplayItem::Id to an index.

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

Change-Id: Id80cfad9af7847664b6f1557aa107d9d6ac6c756
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208114Reviewed-by: Joel Hockey <joelhockey@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770259}

Bug: 1025605
Change-Id: I637f9ea86b5f7a4019ebc83deee84e03ae1606f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208654Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Auto-Submit: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770258}

getAuthToken() is more closely integrated with Gaia and uses accounts
available in Chrome. DICE/Mirror headers are required for the new
consent flow.

launchWebAuthFlow() can also be used with Google OAuth, but it's not
connected to accounts available in Chrome. DICE/Mirror headers are not
needed for this flow.

This CL separates partitions used for these two flows. This would allow
to set DICE/Mirror headers only for one of them. This separation also
stops getAuthToken() and launchWebAuthFlow() from sharing their cookies.

Bug: 1083324
Change-Id: If72f803f3d3e3a8b0e639d1d2c26a89cb291fd06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2203382
Commit-Queue: Alex Ilin <alexilin@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770257}

TBR=govind@chromium.org

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

This reverts commit dbb65740.

Reason for revert: the culprit was found in https://crbug.com/1082670.

Original change's description:
> Add extra thread hops in WebUI code on ChromeOS to simulate old timing.
> 
> The removal of the UI->IO thread hop in r768133 seems to cause some tests in the PFQ to flake. Add extra hops (now UI->IO->UI) to avoid flakiness in the PFQ. This should be reverted once the test issue is tracked down.
> 
> Bug: 1082298
> 
> Change-Id: I64e3e27461a73bf269c8193d9d5c7a65cb3a072a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202671
> Auto-Submit: John Abd-El-Malek <jam@chromium.org>
> Reviewed-by: Jenny Zhang <jennyz@chromium.org>
> Commit-Queue: Jenny Zhang <jennyz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#769037}

TBR=jennyz@chromium.org,jam@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 1082298
Change-Id: I7439699c80a59713f12ed378979f5c21d67e4c39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207858Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Jenny Zhang <jennyz@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770255}

Chrome data use measurement singleton object is currently created
at 2 different places. This CL removes the creation
of data use measurement singleton object by DRP (Data Reduction
Proxy). Instead, the class object would only be created by
chrome/browser/chrome_content_browser_client.cc

Change-Id: I638614f9cc4c71c9ba8a9b4dca683820ae8d2c91
Bug: 1084194
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2205513Reviewed-by: Michael Crouse <mcrouse@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770254}

Bug: 1081250
Change-Id: Ice998a404099e8bf6fcb6e8cdaff72d0c6eb248d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208364Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770253}

On tab sharing, return TAB_CAPTURE_FAILURE if the media_id does not
contain a valid tab.

Bug: 1078254
Change-Id: Ia9586670f9e8460a47c5486115e2a5e32512cb5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209104
Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770252}

Using wpt-import in Chromium 509b2715.
With Chromium commits locally applied on WPT:
f6984fd9 "De-flaky pointerlock/pointerevent_pointermove_in_pointerlock.html"
74ac20cc "Use original URL before redirects as blocked URL in CSP reporting"
ba055028 "Revert "Reorganize COEP + reporting tests""


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

Directory owners for changes in this CL:
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa

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

I happened to have a bad apk in my build directory, most likely because
I killed a build part way through. Trying to run stack while there is
such an apk results in a cryptic python stack. This makes stack ignore
such files.

BUG=none
TEST=none

Change-Id: Ia99544d4d0c3ab7b63849b14cb0dab780b9103ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208603Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770250}

This reverts commit c97b5d2a.

Reason for revert: It breaks V8, as suggested also by some comments
on this CL (also see https://bugs.chromium.org/p/v8/issues/detail?id=10471#c9).

Original change's description:
> Make compression_utils buildable also without Chromium.
> 
> Starting from https://chromium-review.googlesource.com/c/chromium/src/+/2171416
> the target //tools/android/md5sum:md5sum_bin started to depend on
> //third_party/zlib/google:compression_utils.
> 
> The standalone WebRTC build (without Chromium) depends on
> //tools/android/md5sum:md5sum_bin, so this CL moves compression_utils out
> of the "if (build_with_chromium)" block.
> 
> Bug: None
> Change-Id: Ib9e12109398b88aad7750596cc72baf49b19658e
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2193776
> Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
> Reviewed-by: Ilya Sherman <isherman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#767692}

TBR=isherman@chromium.org,mbonadei@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: None
Change-Id: Ic321efdc3d127f5264789ed5463a64e449e2ea48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207163Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
Reviewed-by: Adenilson Cavalcanti <cavalcantii@chromium.org>
Commit-Queue: Adenilson Cavalcanti <cavalcantii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770249}

Support creation of TablesNG layout objects.
LayoutObjectFactory supports TablesNG runtime flag.

Anonymous creation methods are moved to NG classes,
allowing for eventual removal of Legacy classes.

Bug: 958381
Change-Id: I673efc1d23cfe796d0905a41ba0188c857e56cfc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199921
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770248}

This change properly sets the visibility of the expandable details in
install dialogs, so that screen readers will not see them when they are
not expanded.

Bug: 1070748
Change-Id: Ib08c39f156dbdcd9896ee2b96b90c69d1c36881d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2176988Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Tim Judkins <tjudkins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770247}

No change to logic. This adds logging to capture the user's navigation
to a Fragment, such as through the bottom nav bar or when the app is
created (and we implicitly navigate to the HomeFragment).

Fixed: 1082532
Test: None
Change-Id: I53aa5a100d26d505d667b44ad7092a97105a4809
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199179
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Hazem Ashmawy <hazems@chromium.org>
Cr-Commit-Position: refs/heads/master@{#770246}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/e1837289..b072390c

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Ib84fec7ecbb7ac81dfb2f8980e37ee63dd028b91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208642Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#770245}

This CL does not change behavior. Feature flags in Assistant which are
already completely launched are removed.

Bug: b:156676369
Test: Does not change behavior.
Change-Id: Ie1ee273f3eefe38c688e3bbeac5e01601a8501f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2207860Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: David Black <dmblack@google.com>
Commit-Queue: Abhijeet Singh <siabhijeet@google.com>
Cr-Commit-Position: refs/heads/master@{#770244}

We rename roundTripToBrowserThen() to roundTripToBrowser() and make it
return a promise instead of receiving a callback. The promise resolves
when the callback would have previously been run.

R=nasko@chromium.org

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