GitLab

We had originally removed viz_content_browsertests and viz_content_unittests
from Windows, Linux, Mac, and Android FYI bots. This was as we entered Finch
trials and field configurations began to enable this on the CQ.

However we have found out that this only affects test suites withing
chrome/browser. So we lost coverage of content tests.

This re-adds viz_content_browsertests, and viz_content_unittests to the FYI bots
so that we can see if anything is broken.

Change-Id: Ifcb2aab687276b82ec68c9e730aa27cf4ab4b0fc
Reviewed-on: https://chromium-review.googlesource.com/c/1327565Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607037}

being shown.

Bug: 897998
Change-Id: I884709065290889f494a02e06d28602f2bcee68c
Reviewed-on: https://chromium-review.googlesource.com/c/1325561Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Siyu An <siyua@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607036}

Currently, if a cast application is stopped from a different device that
started the application, RemotePlayback is not properly torn down. This
is because the cast application listener is never given a reference to
the session that it should tear down.

This CL fixes the issue, and adds a pre-emptive null check.

Bug: 790766
Change-Id: I6fa67ca87a05efd135c57b396d6d09e69065a6f3
Reviewed-on: https://chromium-review.googlesource.com/c/1327605Reviewed-by: Zhiqiang Zhang <zqzhang@chromium.org>
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607035}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/db21dac6ad7d..8ecbd57f8e89


Created with:
  gclient setdep -r src-internal@8ecbd57f8e89

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=mmoss@chromium.org

Change-Id: I03d1282524d74cb33bba2edbc34fe24a9ac8adad
Reviewed-on: https://chromium-review.googlesource.com/c/1330025Reviewed-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@{#607034}

This is a follw-up change after merge internal change 219177525.

Change-Id: I1ac9774d34c631b8ef3f71e86edd5d7c104c67da
Reviewed-on: https://chromium-review.googlesource.com/c/1327801
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607033}

This CL fixes the computation of the target_size in FromDrawImage() when
the target_size is updated to the size of a mip level. Previously, the
computation rounded down which was inconsistent with the behavior
introduced in https://crrev.com/c/1107049.

Test: the artifact in the referenced bug is no longer present.
Bug: 891316
Change-Id: If8838c1501cbbcedd8261ddf6eac81f21cdca947
Reviewed-on: https://chromium-review.googlesource.com/c/1321774
Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607032}

Change-Id: I4b42fb71f931ef1fcb21150159b06dad4a78ca1d
Reviewed-on: https://chromium-review.googlesource.com/c/1327743Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607031}

Previously Assistant cards were rendered using WebContentsManager.
This did not support either single- or multi-process mash.

After this CL, I'll do a follow up to remove WebContentsManager and
AnswerCardContentsRegistry as they are no longer used by either
Assistant nor AppList.

Known issue: This works fine for single-process mash but a crash
occurs in multi-process mash when testing on device. No crash occurs
with a glinux build so need to do more debugging. That said, this
still moves us forward and allows us to deprecate some classes :)

Bug: b:78078693
Change-Id: Iae0e9de8e5291f0ac99bae12207483838ccb910e
Reviewed-on: https://chromium-review.googlesource.com/c/1321861
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607030}

base::ThreadRestrictions::ScopedAllowWait is deprecated in favor of its more
explicit counterpart.

It should have been replaced by :
 * base::ScopedAllowBaseSyncPrimitivesForTesting in test files.
 * base::ScopedAllowBaseSyncPrimitives in non-test files
 * base::ScopedAllowBaseSyncPrimitivesOutsideBlockingScope when it's used on threads
   that don't allow blocking
The last one is strongly frowned upon but this CL aims to document existing
behavior rather than address it. Owners are encouraged to follow-up by fixing
unnecessary waits and more particularly unnecessary waits
outside-blocking-scope.

Note: The non-for-testing versions require friend'ing in thread_restrictions.h
but care was taken to add these friends ahead of git cl split (since it wasn't
possible to do a line-by-line associated CL split).
Refer to the top-level CL if necessary :
https://chromium-review.googlesource.com/c/chromium/src/+/1288533

Please CQ if LGTY!

This CL was uploaded by git cl split.

R=stevenjb@chromium.org

Bug: 766678
Change-Id: I931476842857ed391d7148febbcac1c811a9ead1
Reviewed-on: https://chromium-review.googlesource.com/c/1324398
Commit-Queue: Gabriel Charette <gab@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607029}

Bug: 867518
Change-Id: I16891cc486f3d884229482b8c4d90309f9994b43
Reviewed-on: https://chromium-review.googlesource.com/c/1327810Reviewed-by: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607028}

If the server shows a window, views was also activating the window. Instead
views should just show the window. If the server wants the window active, it'll
activate the window.

BUG=756085
TEST=covered by test

Change-Id: I208945a61d8c96b5dba0a070d7f32f6536342f28
Reviewed-on: https://chromium-review.googlesource.com/c/1330710Reviewed-by: Jun Mukai <mukai@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607027}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: I6e6c980f74f247b4fd1615f7a956a5e8e2a4f8b6
Reviewed-on: https://chromium-review.googlesource.com/c/1330110Reviewed-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@{#607026}

Tbr: chrisha@chromium.org
Bug: 902335
Change-Id: Ie360d85f9f2a6ecc8f2305f9133a7313fb73dc09
Reviewed-on: https://chromium-review.googlesource.com/c/1330353Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607025}

They became the default ones, no need to specify them.

R=iannucci, vadimsh

No-Try: True
Change-Id: Iebc66d8291fdebab72fcdb334e26befdc6d90bf3
Reviewed-on: https://chromium-review.googlesource.com/c/1330288Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607024}

OnEventFromSource for the |held_move_event_| may not return if
one of the event handler creates a run loop -- this happens
on tab-dragging. As long as |held_move_event_| is valid, any
further touch moves are also held and not processed anymore.

Bug: b/119260190
Test: manually
Change-Id: Ibeacc167bbcf71d6d89a40ad2916ecf1f880998c
Reviewed-on: https://chromium-review.googlesource.com/c/1330061Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607023}

Variations service now sets a flag if the last request was an HTTP
retry, and uses it to decide whether to retry again, instead of
relying on the scheme of the final URL. Also, retries are now disabled
if the fallback url is HTTPS.

Bug: 902727
Change-Id: Ibd6df4a22bc6302b231aff0ae32f8e1c8a1f277c
Reviewed-on: https://chromium-review.googlesource.com/c/1325035
Commit-Queue: Carlos IL <carlosil@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607022}

Bug: 902890
Change-Id: I57021c1d018a48869aecf404854566bbf0b5dabd
Reviewed-on: https://chromium-review.googlesource.com/c/1330080Reviewed-by: Michael Moss <mmoss@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607021}

Normalize the score across all anchor elements. This makes
it simpler to use anchor element score when predicting the
next navigation when there are many anchors on the webpage,
and all of them may have high score.

Also, includes minor cleanups where some of the variables
are added to the header file. These will be used in the next CL.

Change-Id: Iad914682ef6d96c1b4d3cab040b555a6723f05de
Bug: 903945
TBR: ryansturm@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/1328561
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607020}

According to the spec,
https://github.com/w3c/csswg-drafts/issues/2593#issuecomment-386154394
scrollIntoView should
1) Always snap to the target element's snap alignment, and
2) All the affected scrollers should also land on a snap position if
one exists.

This patch does part 2). Before a scrollable_area is added to
the smoothScrollSequencer with its new scroll_offset, we will check if
it has a valid snap offset around, and update the final offset
accordingly.

We'll implement part 1) in a separate patch.

Bug: 842317
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ica22134ed0b1f9d36f5a017c8dd0be54e907dd3d
Reviewed-on: https://chromium-review.googlesource.com/c/1188746Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607019}

Bug: 864763
Change-Id: If3baac188ce07a4c2259b97b013353920b4ad3ba
Reviewed-on: https://chromium-review.googlesource.com/c/1329668Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607018}

Changes in the reland compared to the original patch:
Switched to using GetRoot instead of Root() which might prevent the use of an uninitialized root object.

Original description:
Screen readers want to have a reliable way to know whether a document is still loading so as to ignore events coming from it.
The current change can be made irrespective to whether we will mark the document as loaded when HTML parsing has started or when the "interactive" readyState has been entered.

R=dmazzoni@chromium.org, aleventhal@chromium.org

Bug: 897177, 903402
Change-Id: I681883999918ffdd32fc11d2f691b659c7e91149
Reviewed-on: https://chromium-review.googlesource.com/c/1327745
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607017}

Collides with
components/autofill_assistant/browser/batch_element_checker.cc.

Broken in https://chromium-review.googlesource.com/c/1323489.

Bug: 903940
Change-Id: I8f5efa61ebc3e4ec44f9206ceff863f7082c36ba
Reviewed-on: https://chromium-review.googlesource.com/c/1330293Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607016}

This CL adds UI flag to add WebAuthN UI that guides users through the
pairing process when using Bluetooth authenticators.

Bug: 877344
Change-Id: I12a109fc34f947e64db0ad99089f83fb39ccf6d0
Reviewed-on: https://chromium-review.googlesource.com/c/1329926
Commit-Queue: Jun Choi <hongjunchoi@chromium.org>
Reviewed-by: Kim Paulhamus <kpaulhamus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607015}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/e28390cc438f..af0ede1e73a7


git log e28390cc438f..af0ede1e73a7 --date=short --no-merges --format='%ad %ae %s'
2018-11-09 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-11-09 mheikal@chromium.org Fix crash were CL has no reviewers


Created with:
  gclient setdep -r src/third_party/depot_tools@af0ede1e73a7

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:895722
TBR=agable@chromium.org

Change-Id: I1f65e12c3257a9fa87331f2e409dc702434e5c96
Reviewed-on: https://chromium-review.googlesource.com/c/1330007Reviewed-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@{#607014}

Hovering over a TextNode in DevTools will now highlight it on the
page. Its tooltip shows "#text" with VisualOverflowRect dimensions.

Screenshot: https://imgur.com/a/yPFT73e

Bug: 893426
Change-Id: If988e72960aa68b2d9c666c5de3feb5ce1192509
Reviewed-on: https://chromium-review.googlesource.com/c/1269859Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Erik Luo <luoe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607013}

Moves the 'file count' metric generated by resource_sizes.py out of the
_Specifics group into its own _FileCount group. This is a workaround
for https://crbug.com/903970, where mixing units within a group causes
malformed data to be generated when using the HistogramSet format.

Bug: 892344, 892301
Change-Id: Icfd47567127d51f7ee703262c448c2619148cb10
Reviewed-on: https://chromium-review.googlesource.com/c/1330707Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607012}

This reverts commit ce37f17d.

Reason for revert: Causes crash, see 903671

Original change's description:
> Fix text input on ARC++ Kiosk apps.
> 
> We changed IsInArcAppWindow() to use the window property,
> aura::client::kAppType, but it's not set for ARC++ Kiosk apps' window.
> It makes text input on ARC++ Kiosk apps stop working.
> This CL adds a temporary workaround for this situation. Ideally,
> IsArcAppWindow() in arc_util.cc should handle windows of ARC++ Kiosk app
> correctly.
> 
> Bug: 891825
> Test: Can type text on Wikipedia kiosk app.
> Change-Id: I594aa5c0730704b9ad922441187297bd707de20a
> Reviewed-on: https://chromium-review.googlesource.com/c/1291289
> Commit-Queue: Yusuke Sato <yusukes@chromium.org>
> Reviewed-by: Yusuke Sato <yusukes@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#601631}

TBR=yusukes@chromium.org,yhanada@chromium.org

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

Bug: 891825
Change-Id: Ic50a4bac3af3dfb7f8fd335bb669d3e620a4446a
Reviewed-on: https://chromium-review.googlesource.com/c/1330339Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607011}

Bug: 885376
Change-Id: Ic1b4075a169512103994edabc53b5d1b6daffb10
Reviewed-on: https://chromium-review.googlesource.com/c/1325190
Commit-Queue: Carlos IL <carlosil@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607010}

After initial sync is done, sync loads the persisted metadata and checks
their integrity against the bookmark model.

This CL adds a UMA metric to track different reasons why metadata might
be corrupted

Bug: 516866
Change-Id: I94ed2d80ec487a52069de6a6124419f97b4d5456
Reviewed-on: https://chromium-review.googlesource.com/c/1329248Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607009}

- Creates a free form SMB share dialog
- Dialog will be opened by SmbProvider::RequestMount

Bug: chromium:887135
Change-Id: I379417ac15d633bce704bd50c8d31e8488fc2975
Reviewed-on: https://chromium-review.googlesource.com/c/1289409
Commit-Queue: Bailey Berro <baileyberro@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607008}

This cl add a STOP button to timer notification.

Bug: b/118655426
Test: manual
Change-Id: I88752010e4b0c5be54debddb8394827a798d65fe
Reviewed-on: https://chromium-review.googlesource.com/c/1330296Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607007}

Bug: 881937
Change-Id: Iac86251f6f6d7bba501b2add3260579d2f2ba53b
Reviewed-on: https://chromium-review.googlesource.com/c/1327569
Commit-Queue: Scott Chen <scottchen@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607006}

There are versions of webauthn.dll that ship without BLE support. On
platforms where that is the case, direct access to FIDO token is not
blocked by the OS and so we don't want to integrate with webauthn.dll
there. This changes WinWebAuthnApi to call WebAuthNGetApiVersion on
initialization and mark the API as unavailable if the version number is
 not at least the current version (1).

The check may be overridden by a flag while we wait for
WebAuthNGetApiVersion function to ship.

Bug: 898718
Change-Id: Ic20e55a416d858214b9f444031f4700567933eb4
Reviewed-on: https://chromium-review.googlesource.com/c/1327885
Commit-Queue: Martin Kreichgauer <martinkr@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607005}

BUG=790286,790294,790309

Change-Id: I5314b6a2743a83ed3b864b6842b32d023caed977
Reviewed-on: https://chromium-review.googlesource.com/c/1330340Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Jao-ke Chin-Lee <jchinlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607004}

https://skia.googlesource.com/skia.git/+log/b07ed8fb0766..2bb343c5e822


git log b07ed8fb0766..2bb343c5e822 --date=short --no-merges --format='%ad %ae %s'
2018-11-09 herb@google.com Remove runIndex as a concept for GrTextBlob
2018-11-09 reed@google.com rm legacy flags for hinting enum
2018-11-09 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-11-09 herb@google.com Reland "Move remove ptr args to MakeRecAndEffects"
2018-11-09 herb@google.com Revert "Move remove ptr args to MakeRecAndEffects"
2018-11-09 herb@google.com Move remove ptr args to MakeRecAndEffects


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

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_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;master.tryserver.blink:linux_trusty_blink_rel
TBR=allanmac@chromium.org

Change-Id: I4074acffea1b16b5c684b8b2d47166cca80b0257
Reviewed-on: https://chromium-review.googlesource.com/c/1329992Reviewed-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@{#607003}

Remove java mapped regions so that the unwinder does not try unwinding
these frames at all.

BUG=888434

Change-Id: Ic5999652ec85a4a3ed04aa7e8030d0a3faf11fbd
Reviewed-on: https://chromium-review.googlesource.com/c/1327424
Commit-Queue: ssid <ssid@chromium.org>
Reviewed-by: Mike Wittman <wittman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607002}

Bug: 902554
Change-Id: Ic14cfeaa7b041c316bcb77066d69a7b701bd5a62
Reviewed-on: https://chromium-review.googlesource.com/c/1321260
Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org>
Reviewed-by: Jun Choi <hongjunchoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607001}

https://android.googlesource.com/platform/external/perfetto.git/+log/7b37bbfad45f..1ba4ba601cc4


git log 7b37bbfad45f..1ba4ba601cc4 --date=short --no-merges --format='%ad %ae %s'
2018-11-09 treehugger-gerrit@google.com Merge "profiling/memory: tiny fixups of a couple of copy/move aspects."


Created with:
  gclient setdep -r src/third_party/perfetto@1ba4ba601cc4

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=perfetto-bugs@google.com

Change-Id: I69cc1381e2a50fa4332ac2d776ade5e00bfebc8f
Reviewed-on: https://chromium-review.googlesource.com/c/1330023Reviewed-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@{#607000}

views::TouchSelectionMenuRunnerViews::Menu should be better by
separating it on their own class, this CL introduces
TouchSelectionMenuViews.

Bug: None
Test: Build.
Change-Id: Ic9e8e258c41d2686746ff9b7d73fef1826424851
Reviewed-on: https://chromium-review.googlesource.com/c/1328281Reviewed-by: Mohsen Izadi <mohsen@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: David Jacobo <djacobo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606999}

Now that tablet mode manager tracks all user windows and not just current
accounts, the window should be non account windows should be maximized
on entering tablet mode, not on user switch.

Test: unit_tests MultiUserWindowManagerChromeOS.TabletModeInteraction
Bug: 903427
Change-Id: Ib21a7e1d7f1a37f8a571ad16226f11e03f0db960
Reviewed-on: https://chromium-review.googlesource.com/c/1329502Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606998}