GitLab

All masks must be PictureLayers, but the type is currently a Layer
regardless. This means the Layer API has to include things for masks
only, which are virtual and overridden only by PictureLayer. Instead
they could just be members of PictureLayer.

This changes the type on cc::Layer to hold a PictureLayer as a mask
instead, and changes callers to work with PictureLayer types directly.
They already had a PictureLayer, because masks must be one, but they
had it upcasted to a cc::Layer.

This makes the GraphicsLayer::CcLayer() return a PictureLayer* instead
of the base class Layer*, which means consumers of GraphicsLayer get to
know about PictureLayer. Since we're moving toward a world with only
content layers, and hopefully no base class, this follows that pattern
of introducing code to the real type sooner rather than later.

R=jbroman@chromium.org, pdr@chromium.org

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I7b0fe935c69e9a0f2ee294c722b2372013617dfc
Reviewed-on: https://chromium-review.googlesource.com/1098152Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567069}

This is a reland of e9753daf

Original change's description:
> Supports the new vsh-into-running-container syntax
> 
> It is no longer necessary to use the run_container.sh script every time a
> container shell is needed. If the container is already running, vsh now allows
> "direct access".
> 
> Bug: 848447
> Change-Id: Ia9aeb120befd016386816cdd16fb3336b45426ff
> Reviewed-on: https://chromium-review.googlesource.com/1082055
> Reviewed-by: Timothy Loh <timloh@chromium.org>
> Commit-Queue: Nicholas Verne <nverne@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#563568}

Bug: 848447
Change-Id: I17c73a37a65a8316e62154556ee94fbc37dd703d
Reviewed-on: https://chromium-review.googlesource.com/1096875Reviewed-by: Timothy Loh <timloh@chromium.org>
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567068}

https://chromium.googlesource.com/catapult.git/+log/0db1e01e3f4c..78a0b0424642


git log 0db1e01e3f4c..78a0b0424642 --date=short --no-merges --format='%ad %ae %s'
2018-06-13 benjhayden@chromium.org Refactor Anomaly queries.


Created with:
  gclient setdep -r src/third_party/catapult@78a0b0424642

The AutoRoll server is located here: https://catapult-roll.skia.org

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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I45688b16d5b00c2e090bb5f808f33305b0f37d85
Reviewed-on: https://chromium-review.googlesource.com/1099977Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#567067}

This patch supports snapping after animated wheel scroll.

More generally, we should snap after a scroll animation if the
animation wasn't for snapping itself.

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

Bug: 851472
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ia2adc8be4d6b007eff22acac225c1f6c4952334a
Reviewed-on: https://chromium-review.googlesource.com/1099882Reviewed-by: John Wu <jzw@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567065}

See spec here: https://wicg.github.io/reporting/#report-types

Specifically, some fields in the IDLs were originally not
marked nullable, but now are.

Bug: 564071, 731810
Change-Id: I731ee46f39920c864856f7eda7f18045f779d1c3

TBR: rbyers@chromium.org
Change-Id: I731ee46f39920c864856f7eda7f18045f779d1c3
Reviewed-on: https://chromium-review.googlesource.com/1097602
Commit-Queue: Paul Meyer <paulmeyer@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567064}

BUG=none
TEST=none (comment only change)

Change-Id: Icc0531dde3e613b6b87fd13620667659249324c1
Reviewed-on: https://chromium-review.googlesource.com/1097469Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567063}

We are interested in knowing how long it takes users from first setting
up a device to setting up Crostini.

Bug: 703927
Change-Id: I68d24b4f6f408b3f5dce853dfaaa40c10e1d72be
Reviewed-on: https://chromium-review.googlesource.com/1082068Reviewed-by: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Ben Wells <benwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567062}

https://skia.googlesource.com/skia.git/+log/7c525e62d405..fdcfb8b7c23f


git log 7c525e62d405..fdcfb8b7c23f --date=short --no-merges --format='%ad %ae %s'
2018-06-13 halcanary@google.com Revert "SkTypes: extract SkTo"
2018-06-12 halcanary@google.com SkTypes: add static back
2018-06-12 bungeman@google.com Remove SkBool8.
2018-06-12 brucewang@google.com Implement DWriteFontTypeface::onGetVariationDesignPosition on win10.
2018-06-12 mtklein@google.com Revert "simplify SkTFitsIn"
2018-06-12 khushalsagar@chromium.org fonts: Fix memory allocation for fallback glyphs.
2018-06-12 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 a8802477752f..7ce4a15115cb (3 commits)
2018-06-12 halcanary@google.com SkTypes:  more into SkMacros
2018-06-12 halcanary@google.com SkTypes: templates are usually better than macros
2018-06-12 ethannicholas@google.com renamed SkSL's assert macros
2018-06-12 halcanary@google.com SkMacros split from SkTypes.h
2018-06-12 mtklein@chromium.org avoid immintrin.h in SkNx_sse.h
2018-06-12 benjaminwagner@google.com Add Vulkan jobs for GalaxyS7.
2018-06-12 mtklein@chromium.org remove __cplusplus guard
2018-06-12 mtklein@chromium.org simplify SkTFitsIn
2018-06-12 egdaniel@google.com Add blacklist to failing vulkan gtx660 test.
2018-06-12 halcanary@google.com SkTypes: extract SkTo


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

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

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=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:android_optional_gpu_tests_rel;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=chromium:829622
TBR=csmartdalton@chromium.org

Change-Id: I896d8a03a7b21a46f08d6c14e79548f5b37148cf
Reviewed-on: https://chromium-review.googlesource.com/1098939Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Ben Wagner <bungeman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567061}

The previous CL for the bug was reverted because it caused crashes.
We may still go through the normal paint path which requires layer
states during printing, so for safety don't skip layer state update,
but just suppress the DCHECK when printing.

Bug: 848730
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I9f08af2282c76bb97bd14428eb368791feddbaa8
Reviewed-on: https://chromium-review.googlesource.com/1097558Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Tien-Ren Chen <trchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567060}

R=iannucci,tandrii

No-Try: True
Bug: 795146
Change-Id: Ib19e24035fcf46d3563ece2eda7271bc1e176a03
Reviewed-on: https://chromium-review.googlesource.com/1100174
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567059}

Rename GetAllData() to GetAllDataForDebugging().
The function is only used for Sync Node Browser
of chrome://sync-internals and for unit-tests,
it's name should reflect that.

Bug: 851859
Change-Id: I5a73bf405a8e0aca55adb4ca39ee7fdfad813c07
Reviewed-on: https://chromium-review.googlesource.com/1097049Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com>
Cr-Commit-Position: refs/heads/master@{#567058}

To force migration on Kevin, we are removing "Skip" button from the migration
screen.
"Skip" should still be available in other boards.
Even on Kevin, "Skip" is still available when there is no enough storage to
start migration.

Bug: 852228
Test: Manually confirmed that Skip button is hidden on Kevin and visible on Eve.
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ibd5142db654a3797719feab134de0ea2352cc7dc
Reviewed-on: https://chromium-review.googlesource.com/1098870Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Naoki Fukino <fukino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567057}

Implements the functions of SmbShareFinder and adds tests

Bug: 757625
Change-Id: I072390d39ff060e36ce748dcf28ed98a090b7096
Reviewed-on: https://chromium-review.googlesource.com/1089852
Commit-Queue: Allen Vicencio <allenvic@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567056}

* All Mac bots use Mac-10.13 as os.
* Android device bots use id:<bot name> as dimensions

Bug: 840631
Change-Id: I0ea523e0b4f1f91f20c7f32333ec2db6ab486b03
Reviewed-on: https://chromium-review.googlesource.com/1100070Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567055}

Change-Id: Ia31b9004b57f6dff97f93d2280e3b9a23ca6919c
Reviewed-on: https://chromium-review.googlesource.com/1100079Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567054}

There's updated spec that moves the position of the current wallpaper
info bar to the top of the image list.

https://drive.google.com/corp/drive/folders/0B_2Uyb2Rhx2ObU5VTFJVWHR2WW8

Bug: 824453
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I414fb92f75f5b2ffa1b6b732c9be577ed4838107
Reviewed-on: https://chromium-review.googlesource.com/1083138Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567053}

https://webrtc.googlesource.com/src.git/+log/789221f1101a..aeb0a6475bcc


git log 789221f1101a..aeb0a6475bcc --date=short --no-merges --format='%ad %ae %s'
2018-06-13 peah@webrtc.org AEC3: Increase the range of reported echo path delay metrics
2018-06-13 magjed@webrtc.org Android: Fix VideoTrack behavior for adding/removing VideoSinks
2018-06-13 nisse@webrtc.org Replace all use of rtc::Pathname in generator_unittest.cc.
2018-06-13 danilchap@webrtc.org Introduce list of fields to put into codec agnostic descriptor
2018-06-13 devicentepena@webrtc.org AEC3: Changes to how the reverberation decay is applied.
2018-06-13 jonasolsson@webrtc.org Remove "webrtc_rtp" traces.
2018-06-13 yura.yaroshevich@gmail.com Add ow2_asm license


Created with:
  gclient setdep -r src/third_party/webrtc@aeb0a6475bcc

The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng

BUG=chromium:850538,chromium:852257
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I96d3ed7b7c4bd9a705edda10c15a74623ce6505c
Reviewed-on: https://chromium-review.googlesource.com/1099915Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#567052}

The code now provides as a run action command line argument the Chrome
app guid registered with Omaha, as returned by the configurator, like this:

--appguid={8A69D345-D564-463c-AFF1-A69D9E530F96}

Bug: 687231
Change-Id: I22125e434ffbd4e98de9c3373dcb54ac7f98799a
Reviewed-on: https://chromium-review.googlesource.com/1100088Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567051}

This CL hides the radio button when there is only default download
directory option.

Also tweaks the layout a little bit, so the radio button and the text
can align with the "Download location" title in the preference UI.


Bug: 850586
Change-Id: Id686ee8e8d06bd477606f62741386095fa11c31c
Reviewed-on: https://chromium-review.googlesource.com/1098296Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567050}

Change-Id: I3dfc9477e6cd79358656119628ba660d36bf7e70

Bug: 806109
Change-Id: I3dfc9477e6cd79358656119628ba660d36bf7e70
Reviewed-on: https://chromium-review.googlesource.com/1098030Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567049}

This CL changes the rich layout images to be centered in a box to the
left of the text lines. This allows for answer images and entity images
to be different sizes without doing a lot of less readable math.

Bug: 798631
Change-Id: I882305ca09353266f02115446f481bff00b00e12
Reviewed-on: https://chromium-review.googlesource.com/1094263Reviewed-by: Kevin Bailey <krb@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567048}

This change aims to reduce code duplication in the implementations of
BluetoothTest::SimulateLowEnergyDevice for BlueZ and Windows. In order
to do so it adds a utility struct and method to BluetoothTestBase, that
implementations of SimulateLowEnergyDevice make use of.

Bug: 821766
Change-Id: I5283a1eb55e50d68dce2c9810994cf6c4ed80212
Reviewed-on: https://chromium-review.googlesource.com/1096675Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567047}

crrev.com/c/1090151 moved the null-pointer-arithmetic warning too far back.
It's supported by Xcode 10, but not Xcode 9.3.

Bug: 850333, 843234
Change-Id: I21935c592ca7b3ba75cb6fc7b7c0686564dd3ec4
Reviewed-on: https://chromium-review.googlesource.com/1099649Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567046}

Previously, if a clip was between two transforms, and the clip result
was not tight, and the combination of the two transforms didn't change,
we missed raster invalidation for the changed effective clip.

Now check for change of LocalTransformSpace for clip and effect nodes.

Bug: 848782
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I1b60ecc2bc79cba69c667e188053b024de670361
Reviewed-on: https://chromium-review.googlesource.com/1094202
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567045}

In the BottomContainer, in order to handle sitting on top of multiple
different UIs, the setTranslationY function is overridden to apply
offsets independently of the view's original translation. This was
broken because the initialization logic also attempted to apply this
offset. This patch updates the incorrect call in the init function
and updates the math in setTranslationY.

Bug: 851182
Change-Id: Id4955aed45b91cd55a3baf4c70f8087a65123f24
Reviewed-on: https://chromium-review.googlesource.com/1099772Reviewed-by: Pedro Amaral <amaralp@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567044}

Gesture pinch events have |needs_wheel_event| and |zoom_disabled| as
browser side implementation details. There is no need to include these
fields when sending the event to the renderer.

Bug: 787924
Change-Id: I2a2e4f9376f384801bb2ca73b5a0e20d589e92e1
Reviewed-on: https://chromium-review.googlesource.com/1087433Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567043}

Android does not support partial swaps. Instead, when an empty swap
is requested we're supposed to commit overlay planes.

Bug: 850546
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: If77156732b4f43872855a8ad676c42a5e9842678
Reviewed-on: https://chromium-review.googlesource.com/1099266Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567042}

Move CastCommandLineHelper.java from internal to upstream and let CastBrowserHelper use it to initialize command line.

Bug: b/110021629

Test: cast_shell_junit_tests

Change-Id: I9940e95e26be072bc1762e60f6c6ae541277d34c
Reviewed-on: https://chromium-review.googlesource.com/1097548Reviewed-by: Simeon Anfinrud <sanfin@chromium.org>
Commit-Queue: Zhiheng(Vincent) Li <vincentli@google.com>
Cr-Commit-Position: refs/heads/master@{#567041}

https://pdfium.googlesource.com/pdfium.git/+log/4c48b107c6d1..571053a44f87


git log 4c48b107c6d1..571053a44f87 --date=short --no-merges --format='%ad %ae %s'
2018-06-13 hnakashima@chromium.org Mark modified content streams as dirty in CPDF_PageObjectHolder.
2018-06-13 npm@chromium.org Remove CFX_FixedBufGrow from cpdf_renderstatus.cpp
2018-06-13 npm@chromium.org Remove CFX_FixedBufGrow from cpdf_colorspace.cpp
2018-06-13 npm@chromium.org Remove almost all usages of CFX_FixedBufGrow from cpdf_dibsource.cpp
2018-06-13 npm@chromium.org Make CJBig2_Context::GetHuffmanTable return const
2018-06-13 npm@chromium.org Remove CFX_FixedBufGrow from fx_codec_icc.cpp
2018-06-13 art-snake@yandex-team.ru Merge the offset calculation logic within  CPDF_HintsTable.


Created with:
  gclient setdep -r src/third_party/pdfium@571053a44f87

The AutoRoll server is located here: https://pdfium-roll.skia.org

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=dsinclair@chromium.org

Change-Id: I28c83054cdeb3c8977f25384a0a9fdcfaba05834
Reviewed-on: https://chromium-review.googlesource.com/1099815Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#567040}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/e09b6845cf72..31d539486159


git log e09b6845cf72..31d539486159 --date=short --no-merges --format='%ad %ae %s'
2018-06-13 recipe-roller@chromium.org Roll recipe dependencies (trivial).


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

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

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=agable@chromium.org

Change-Id: I36cd8ade79f1655bde894b6200092132072e55a8
Reviewed-on: https://chromium-review.googlesource.com/1099537Reviewed-by: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#567039}

This reverts commit 8dbc0c82.

Reason for revert: broke https://ci.chromium.org/buildbot/chromium.chrome/Google%20Chrome%20Linux%20x64/32416

Original change's description:
> Remove absolute paths from build files
> 
> This CL removes all absolute paths to src and all usages of the out directory
> name from all ninja files on most Linux builds.
> 
> This means it's possible to mount your src directory at different locations and
> still have incremental builds work.  You can also rename your out directory.
> 
> BUG=None
> R=​dpranke,caitkp,rockot
> 
> Change-Id: I5ff5b0d2d60110755dde64e876c7f1a09d814b1a
> Reviewed-on: https://chromium-review.googlesource.com/1091457
> Reviewed-by: Cait Phillips <caitkp@chromium.org>
> Reviewed-by: Ken Rockot <rockot@chromium.org>
> Reviewed-by: Dirk Pranke <dpranke@chromium.org>
> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#567020}

TBR=caitkp@chromium.org,rockot@chromium.org,dpranke@chromium.org,thomasanderson@chromium.org

Change-Id: Iec959adc2e8c82dd191f382c0cfb197aea406fc3
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: None
Reviewed-on: https://chromium-review.googlesource.com/1099979Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567038}

Bug: 852512
Change-Id: Ie118dcafd7dd46f62f03dbbd95091db24cb7ef26
Reviewed-on: https://chromium-review.googlesource.com/1099646Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567037}

Move the proto parsing utilities into the WeeklyTime classes to make
them reusable by policies that use the WeeklyTime protos. Added unit
tests for the proto parsing.

BUG=chromium:849506
TEST=WeeklyTimeInterval and WeeklyTime unit tests

Change-Id: Ic6b327e9b75f6bf9f2c1d1d1a949ed30ec8f18f7
Reviewed-on: https://chromium-review.googlesource.com/1097698
Commit-Queue: Adolfo Higueros <adokar@google.com>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567036}

password_manager_test_base includes chrome_password_manager_client but
wasn't previously depending on it, meaning that the latter's mojo
dependencies sometimes weren't built in time.

Change-Id: I6b40d771d5744bd3e5975e47857e88b974a1d43a
Reviewed-on: https://chromium-review.googlesource.com/1099493Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567035}

Failing on Mac10.10.

TBR=thakis@chromium.org

Change-Id: I906d7ffe323f10630a21ec93f953b40c33fb0182
Bug: 852536
Reviewed-on: https://chromium-review.googlesource.com/1099715Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567034}

Implements GetShares using an in-memory map to simulate a D-Bus call to
SmbProvider daemon

Bug: 757625
Change-Id: Icb655328ac0f4b766ecd6a05cb2d6439c15d9ac0
Reviewed-on: https://chromium-review.googlesource.com/1089851
Commit-Queue: Allen Vicencio <allenvic@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567033}

An infinite (or actually kTableMaxWidth, which is 1000000px) max logical
width doesn't work well inside flexboxes, because
LayoutFlexibleBox::ComputeInnerFlexBaseSizeForChild() will use a child's
MaxPreferredLogicalWidth() as main axis extent if it's auto.

Grid containers have similar issues with such tables, so avoid it for
them as well.

Don't apply this to deprecated flexbox, as that would cause two tests
failures:
* fast/block/block-size-integer-overflow.html
* fast/deprecated-flexbox/box-size-integer-overflow.html

Bug: 850566
Change-Id: I9984459801ac229575e8177a9d683088e723db6c
Reviewed-on: https://chromium-review.googlesource.com/1095220
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#567032}

Bug: 829272
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I79f0be1b2c5751cf62a5c4cfed1dad30fe1f6358
Reviewed-on: https://chromium-review.googlesource.com/1096285
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Scott Chen <scottchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567031}

This CL fixes two bugs with background-attachment:fixed computation:

1. Since CL 827671 we switch root layer in PaintInfo whenever the
current transform node changes. This has a side effect that the painting
root layer is no longer guaranteed to be a containing block ancestor of
the current layout object, and AccumulatedScrollOffsetForFixedBackground()
may skip over the painting root all the way to the root. This CL adds
the skipping check to ensure we only collect scroll offsets up to the
painting root.

2. FixedAttachmentPositioningArea() converts the viewport rect to the
space of the current paint context. Prior to SPv175 the border box space
of the painting root is always equivalent to the space of the current
paint context, so FixedAttachmentPositioningArea() did just that. In
SPv175 the painting root may not always create a paint offset
translation in case of a squashed layer, thus can induce an offset from
its transform node. This CL ensures the paint offset taken into account.

BUG=529963,849854

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ib2f84a619235ab4ec6a9bfc695b57aae9d41b808
Reviewed-on: https://chromium-review.googlesource.com/1098313
Commit-Queue: Tien-Ren Chen <trchen@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567030}