GitLab

MessageLoop is going away soon.

This CL was uploaded by git cl split.

R=kmackay@chromium.org

Bug: 891670
Change-Id: Ic1325bfe89d1731134cb01a69b120d74eec119ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944149
Auto-Submit: Carlos Caballero <carlscab@google.com>
Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Commit-Queue: Kenneth MacKay <kmackay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720628}

Also fixing CSS related PRESUBMIT errors:
1) removing usage of -webkit-box, which seems to have no effect
2) converting padding/margin CSS properties to use logical start/end
   instead of left/right

This is in preparation of migrating this page to JS modules.

Bug: 1028829
Change-Id: I33019772455cc870e49ebadf11b4c98650eeeb8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941270
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720627}

Bug: 1007725
Change-Id: Ie9ce62d0775094cba94261d95853e4fe9dc19376
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1935649
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720626}

Now that the CRD Chrome app has been removed, we have no need
for the NaCl plugin code.  AFAICT nothing else in remoting
relies on it so it is safe to remove.

Change-Id: Ic977bc8b7d921e6b2bed2cfc8ea0bd40c24acec2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1933132Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720625}

It is possible to create a credential on an authenticator that supports
user verification but doesn't have it configured.

If the user then tries to authenticate using that credential, and the
relying party sets UV=required, the message returned says that no
credential exists. This could be confusing for developers trying to
debug problems.

This patch changes the error to indicate that UV is not available.

Fixed: 1029285
Change-Id: Id70960d0a3830854decfa9d02464cd51c1c8f52a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943386
Commit-Queue: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Reviewed-by: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720624}

Note that removed resources were reported as unused.

Bug: 1024945
Change-Id: Ifc1189a905cf0f12d49ef08dbe34022d62f165ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941048Reviewed-by: Carlos Knippschild <carlosk@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Dan H <harringtond@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720623}

62f10f30bad9 Fix 'make distcheck'
f6fe7cc55ab9 mac processor: Add mapping for
             EXC_BAD_ACCESS/KERN_CODESIGN_ERROR
1f1d950d6a4b Fix compilation of http_upload.cc with Windows gcc
47cd498384fd dump_syms: handle forward reference DWARF attributes

Change-Id: I337887b046d45f7d27b7ccfe9ad20c85fc589169
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943543Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720622}

This CL implements regex substitution. A new key called 'regexSubstitution' is
added to the Redirect dictionary. Rules using the 'regexFilter' can specify the
'regexSubstitution' key to use regex based redirects with capture groups.

BUG=974391
Doc=https://docs.google.com/document/d/1mRErUMII_gSSPaHmxyn31UOYWUaZLj0xOaezekxD2-Y/edit?usp=sharing (Internal only)

Change-Id: I7302e1641d257029d67f189ef427823704fccdf9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929577Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720621}

net/if.h can conflict in confusing ways with linux/if.h (discovered in
the process of some out-of-tree jumbo experiments), but thankfully we
don't need the net/if.h include here.

Change-Id: Ic9784c5d56cf896a56b8c1b989888607d09a3289
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944847Reviewed-by: Paul Jensen <pauljensen@chromium.org>
Commit-Queue: Mostyn Bramley-Moore <mostynb@vewd.com>
Cr-Commit-Position: refs/heads/master@{#720620}

Report animation smoothness for the transition into the hotseat in the
HomeLauncher.

The original change caused use-of-uninitialized-value flaky tests. This
is a possible fix for the issue by explicitly resetting the
|animation_metrics_reporter_|

Bug: 1022178, 1022177, 1028255
Change-Id: I9abe9532e4f8b8cbc8c3700b21db48144f76f767
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940562Reviewed-by: Manu Cornet <manucornet@chromium.org>
Commit-Queue: Ana Salazar <anasalazar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720619}

Bug: 984550
Change-Id: Ieb35138ec94f70d3e8e3064fc013f8266ef09a67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885218Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720618}

https://skia.googlesource.com/skia.git/+log/b97a24a009a1..2e3be5648a9f

git log b97a24a009a1..2e3be5648a9f --date=short --first-parent --format='%ad %ae %s'
2019-12-02 reed@google.com Reland "fix sense of ifdef for deprecated method"

Created with:
  gclient setdep -r src/third_party/skia@2e3be5648a9f

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

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: None
Tbr: bsalomon@google.com
Change-Id: I460c2bfc02aec683c5c7711ab50b0ede38178b04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946864Reviewed-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@{#720617}

Bug: 1027426
Change-Id: I22940610369f88a933c85860dcd6aa97defcb8cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941191Reviewed-by: Taylor Bergquist <tbergquist@chromium.org>
Commit-Queue: Charlene Yan <cyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720616}

This function is dead since r715492.

Bug: None
Change-Id: I22fef49eed2d5e084630b7e94cbbf57056635462
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945921
Auto-Submit: Peter Boström <pbos@chromium.org>
Commit-Queue: Caroline Rising <corising@chromium.org>
Reviewed-by: Caroline Rising <corising@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720615}

Bug: 1007716
Change-Id: I89645eb8831a0f28a762c84e092b866e96bea1fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1939846Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720614}

The |tabs_used_in_bg_| field wasn't properly set for the (rare) cases
where the site data reader is available synchronously.

Change-Id: Ida586be452cff80e74088df6d081bfc79899b26a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943535
Auto-Submit: Sébastien Marchand <sebmarchand@chromium.org>
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720613}

Change-Id: If92e2b949ae2792b1cde8b56bd394654897b76e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945956
Auto-Submit: Kenneth MacKay <kmackay@chromium.org>
Commit-Queue: Yuchen Liu <yucliu@chromium.org>
Reviewed-by: Yuchen Liu <yucliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720612}

This change fixes a bug in the extension error bubble in which that
bubble shows two "Details" buttons.

This was ultimately caused by the fact that
GlobalErrorWithStandardBubble defined this method:

  virtual bool ShouldUseExtraView();

When this method returned true, GlobalErrorBubbleView was supposed to:

1) Not have a Cancel button, even if there was Cancel button text
2) Add a button in the extra view slot whose text was the Cancel button
   text
3) Call the GlobalErrorWithStandardBubble back via the cancel pressed
   method when that extra button was pressed

This was used to add a "Details" button to extension errors.
Unfortunately, the condition in (1) led to code like this:

  if (!ShouldUseExtraView() && has_cancel_text)
    AddCancelButton();

which looks like a bug, and so in 74eb4979 I "corrected" it in the
obvious manner. That led to there being two cancel buttons in this
instance. :(

This change:
1) Adds first-class support to GlobalErrorWithStandardBubble for a
   "details" button slot, independent of the cancel & accept buttons
2) Migrates ExtensionErrorUIDefault to use that mechanism
3) Removes GlobalErrorWithStandardBubble::ShouldUseExtraView

Bug: 1024995
Change-Id: I31fe6a7a1d64f0bca2d7abd524650954b4579286
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1933205Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720611}

https://android.googlesource.com/platform/external/perfetto.git/+log/27076e27131f..7724a9414f89

git log 27076e27131f..7724a9414f89 --date=short --first-parent --format='%ad %ae %s'
2019-12-02 zakerinasab@google.com Merge "Add Vulkan memory tracker config to trace config"

Created with:
  gclient setdep -r src/third_party/perfetto@7724a9414f89

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

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

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

Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: If02c245ccb8fa4132b651fc0a982f78dad061b2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946446Reviewed-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@{#720610}

We now only define shard_num and shard map location
in bot_platforms.py.

Bug: 902089
Change-Id: I101743f3a4aaa2291d2dba03d7338d9dbe03798c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941273
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720609}

Bug: 1012203
Change-Id: I5f10793d64cc6a5b64908387dab26e722abf275e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943236Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720608}

Bug: 1007749
Change-Id: Ifd172b7913f2f50c5513c446db7e14731f965039
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941055Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720607}

After crrev.com/c/1915021 that connects the ambient light readings from
powerd to the color transform matrix, we can enable ambient color light
by default.

This CL additionally removes the flag in about://flags since it does
not have any effect on most of devices where ambient color is not
supported.


Bug: 1021193
Change-Id: I2f4b7c57b99e84cc2cf713bb92924b9d57d2d579
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1938627Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Auto-Submit: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720606}

After this change, all Telemetry perf testers will use shard maps,
so it will be easier to do some cleanups.

Bug: 902089
Change-Id: I141614659a3b46aa9b67932f28d4f2a817ae3110
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941287
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Auto-Submit: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720605}

If SkiaRenderer is missing a texture during draw it tries to allocate an
equivalent fallback texture of the correct size and attributes. This
doesn't work for externally allocated textures.

Currently ImageContextImpl::CreateFallbackImage() creates a
GrBackendTexture of type k2D instead of kExternal. This triggers a later
SkASSERT in GrTextureProxy::onValidateSurface(). When SkAsSSERTs are
disabled it still doesn't draw anything. Just skip drawing the fallback
texture by proving a null SkPromiseImageTexture instead.

Bug: 1029522
Change-Id: I6f370694116e8a47e8885492f1365783c046db65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946627Reviewed-by: Jonathan Backer <backer@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720604}

Change-Id: Id118c5a81446635f02fc23ae25ffd007ec400c1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945330
Commit-Queue: Jarryd Goodman <jarrydg@chromium.org>
Reviewed-by: Jarryd Goodman <jarrydg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720603}

I'm not entirely sure why this fixes the issue, but after a couple hours
it was all I was able to come up with. Interestingly, if I move the line
inside the picker's init, the issue remains.

https://screenshot.googleplex.com/UzOWW6uOVRE.png
https://screenshot.googleplex.com/XPG9EPkODoP.png

Bug: 1028090
Change-Id: I8b6ce7135356c863aa396b238ce9a51b0dac26f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940955Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Commit-Queue: Alfonso Garza <alfonsogarza@google.com>
Auto-Submit: Alfonso Garza <alfonsogarza@google.com>
Cr-Commit-Position: refs/heads/master@{#720602}

Bug: 1014148
Change-Id: Ib60bc2d53649ad869f5fd121687ba4931d15efa8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940493Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Doug Arnett <dougarnett@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720601}

This CL is fixing the memory leak describe here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=974239

Without this patch, tasks to check the file existence can be
queued for the same download without being executed. This can
lead to terrible scenario with billion of tasks queued.

This CL is adding a set to keep track of the current pending
download queries. This way, there can not be two pending tasks
at the same time for each download item.

Bug: 974239
Change-Id: I52fb23ce50ba8542ed262552dd7f9aaaa5589548
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946783Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720600}

Allow passing a URL parameter to specify the sort method to be used upon
page load. This will be used by a storage pressure notification which
optionally navigates the user to all sites. The all-sites page will be
sorted by storage, when the user is forwarded here from a storage
pressure notification.

example usage: chrome://settings/content/all?sort=data-stored

Bug: 997258
Change-Id: I4ccc547c2dc4aad974f06debd6e0d4e461e4a0b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865259
Commit-Queue: Jarryd Goodman <jarrydg@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720599}

Change-Id: I32fbf0e9e9b7cb1642b044ecc2a2dae1636c34d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944270Reviewed-by: Roger Tawa <rogerta@chromium.org>
Reviewed-by: Daniel Rubery <drubery@chromium.org>
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720598}

The --chrome_pass Closure compiler flag is only needed for code that relies on
cr.js (cr.define(), cr.exportPath() and friends). For JS code that has migrated
to JS modules --chrome_pass is not necessary.

Explicitly removing --chrome_pass not only makes type-checking faster, but
also ensures that eventually we don't depend on this pass at all.

Note that using |is_polymer3| also opts out a js_type_check() target from
--chrome_pass, but without the new |uses_js_modules| there is no easy way
for non-Polymer code to opt-out.

Note: With this change any JS code that uses JS modules must specify either
|uses_js_modules| or |is_polymer3| attributes.

Bug: 1028829
Change-Id: I4e019770e36ac460402123c5413be6c95e32fef2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1938248Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720597}

Later when experimental tagging support has landed we'll be able to add
an additional test asserting that PDFs are tagged when the right command-line
flag is passed.

Bug: 607777
Change-Id: I5030456efeb0b005d7153eb8c9e36050d6051c72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1927974Reviewed-by: Eric Seckler <eseckler@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720596}

The window system can handle mouse events without them, but
this causes a weird conditions like the ones reported in the
bug. More specifically,
- sending a new mouse event enables the mouse event automatically
- on enabling mouse events, NativeCursorManagerAsh can set
  the last mouse location to an unexpected location
  https://cs.chromium.org/chromium/src/ash/wm/native_cursor_manager_ash.cc?sq=package:chromium&g=0&l=158
- further MouseMove / Press / Release / Click APIs can be affected
  by this.

Bug: 1028413
Test: tast run ui.OverviewScrollPerf ui.WindowResizePerf
Change-Id: I93628663444b405501129a96d32889478dba7a41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940713Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720595}

The flag usage has been removed from devtools-frontend [1].

[1]: https://crrev.com/c/devtools/devtools-frontend/+/1942288

Change-Id: I1436bc8be3258c84a86be9d86df9434647fca180
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1942336Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720594}

Now that the flags for browser plugin have been removed, we remove the
code to support browser plugin from the guest view JS implementation.

Bug: 533069
Change-Id: Ida04f0ce856d0f318835d6369558a3e38cac47e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943579Reviewed-by: James MacLean <wjmaclean@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720593}

The calls to BelongsToCurrentThread appear to be no-ops at the moment, and
assume that they were intended to be DCHECKS, so a quick CL to fix.

Change-Id: I33a6c8e05312b528d5a4e89fd18a0cff6281cd28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762238
Commit-Queue: Xing Liu <xingliu@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720592}

This test doesn't work on Mac and probably won't ever be made to work.
Issue 899286 obscured this test breakage from us, also.

Bug: 1028239
Change-Id: I9f9865ba7ea4fd626fe50298e60c772876b0439b
Tbr: raymes@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943473Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720591}

MessageLoop is going away soon.

This CL was uploaded by git cl split.

R=mfoltz@chromium.org

Bug: 891670
Change-Id: I1678e50cd81155739b1493f68de637bc781abcb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943186
Auto-Submit: Carlos Caballero <carlscab@google.com>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720590}

Change-Id: I7b613853896b4090bf1cd00cdeb6d986c9add676
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1926807Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720589}