GitLab

R=pcc@chromium.org

Bug: 856128
Change-Id: I3e90a4f40e75439ad6cfa72d5b3dea1c0002d601
Reviewed-on: https://chromium-review.googlesource.com/1114848Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570622}

Modify blink::ReadableStreamOperations::IsDisturbed() to take an
ExceptionState& parameter. Modify all callers so that the ExceptionState
is passed through all the way from the bindings layer. Where
IsDisturbed() is called from code that runs asynchronously, the
context_type, interface_name and property_name are cached and used to
create a new ExceptionState object in the asynchronous context.

Also change methods in the implementation of the payment API to use the
cached context_type, interface_name and property_name instead of
hard-coding the values.

Add the extended attribute "RaisesException" to all the asynchronous
body-reading methods in body.idl so that they receive an ExceptionState&
parameter which is used to handle exceptions thrown when calling
IsDisturbed() inside RejectInvalidConsumption().
RejectInvalidConsumption() now always rejects by throwing an exception
and no longer returns a promise.

An exception-ignoring IsBodyUsedForDCheck() method is added which
doesn't change the exception state.

Also add the [RaisesException] attribute to the bodyUsed accessor. Since
it now throws if it has ever failed, fix the
call-extra-crash-is-disturbed.html layout test to reflect that.

Bug: 853189
Change-Id: Ib6df486a5f4ea7c58ecc123a716ee76ace0c92ed
Reviewed-on: https://chromium-review.googlesource.com/1107578Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Jinho Bang <jinho.bang@samsung.com>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570621}

Test the various ways of setting or changing the port on a blink::KURL
and verify that KURL::Port() returns the correct answers in each case.

The results are different depending on how the port was set: the
constructors are strict about disallowing invalid ports. SetPort()
converts any input to a valid port. SetHostAndPort() is somewhere
inbetween.

Bug: 606462
Change-Id: I1533d47aa113d2bb4482cdfe17e682a5da56649a
Reviewed-on: https://chromium-review.googlesource.com/1114572Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570620}

https://chromium.googlesource.com/libyuv/libyuv.git/+log/bc383e76d631..4d67b3e851b1

$ git log bc383e76d..4d67b3e85 --date=short --no-merges --format='%ad %ae %s'
2018-06-26 fbarchard Add H420 and H422 to ConvertToARGB()
2018-06-20 johannkoenig use unix line endings
2018-06-20 johannkoenig add const to msa loads

Created with:
  roll-dep src/third_party/libyuv

Bug: libyuv:799
Change-Id: I45facaa7902660ea064057c16030a836bbc11c9d
Reviewed-on: https://chromium-review.googlesource.com/1115873
Commit-Queue: Frank Barchard <fbarchard@chromium.org>
Reviewed-by: Frank Barchard <fbarchard@chromium.org>
Reviewed-by: Johann Koenig <johannkoenig@google.com>
Cr-Commit-Position: refs/heads/master@{#570619}

This cl updates shortcuts' colors to match Chrome's.
Changes:
1. All Grey 800 #3C4043 should be changed to Grey 900 #202124.
2. All Grey 600 #80868B should be changed to Grey 700 #5F6368.
These changes apply everywhere, including searchbox, side nav and keys.

Bug: 835374
Test: manual.
Change-Id: I772a54012c031540e8a3476d97bff15805b322e6
Reviewed-on: https://chromium-review.googlesource.com/1115801
Commit-Queue: Tao Wu <wutao@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570618}

NOTRY=true
TBR=nednguyen@chromium.org
BUG=856864

Change-Id: I6cf5b595c15295076feb88a11e8e7009e108e674
Reviewed-on: https://chromium-review.googlesource.com/1116248Reviewed-by: oysteine <oysteine@chromium.org>
Commit-Queue: oysteine <oysteine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570617}

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

Bug: 847574, 835195
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I801925ded3b74520e1f92d1ce269fdbb8bc8bf09
Reviewed-on: https://chromium-review.googlesource.com/1115903Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570616}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/a481ed6f083d..1b45f0dc972b


git log a481ed6f083d..1b45f0dc972b --date=short --no-merges --format='%ad %ae %s'
2018-06-26 yunlian@google.com remove USE=thinlto from elm and peach_pit release


Created with:
  gclient setdep -r src/third_party/chromite@1b45f0dc972b

The AutoRoll server is located here: https://chromite-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.



BUG=chromium:854801
TBR=chrome-os-gardeners@chromium.org

Change-Id: Iaf752b79eead83599902e5bdb3bf9a2b81620527
Reviewed-on: https://chromium-review.googlesource.com/1115978Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#570615}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/7ccf2f0c21b3..1d5659c89760


git log 7ccf2f0c21b3..1d5659c89760 --date=short --no-merges --format='%ad %ae %s'
2018-06-26 recipe-roller@chromium.org Roll recipe dependencies (trivial).


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

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: Ie209632d1682b953ff34278ea245873ad082028f
Reviewed-on: https://chromium-review.googlesource.com/1115938Reviewed-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@{#570614}

Change-Id: I49957e9b7c6b9bda6588823a7b864754a4de0f10
Reviewed-on: https://chromium-review.googlesource.com/1115970Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570613}

When a sink button is clicked / selected with keyboard, activate its
inkdrop to make it clearer that it's been selected. Before this change
the button color would go back to the color before click after a ripple.

Screen capture:
https://drive.google.com/open?id=1w3bToFfyQAj5vu0uakCFwT_fNkcaCHjH

Bug: 856798
Change-Id: Id433dd7633180fcc81ebd8773e70a41b7a02b9b8
Reviewed-on: https://chromium-review.googlesource.com/1109383Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570612}

This was removed in crrev.com/569896, causing significant memory
regressions in system health benchmarks on Android.

It's unclear why the similar size check in PLSA::UpdateScrollableAreaSet
(for computation of scrolls_overflow_) isn't sufficient.

Tested: perf try job
Bug: 856067
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I0334f53d95ac1b4ddd9503b284ff880b8338ab67
Reviewed-on: https://chromium-review.googlesource.com/1115513
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570611}

Allow multiple binds on a storage area where the previous binding is
unbound. This is needed because of the following case:

1. Page A (process X) opens a session storage area.
2. Page A opens a new tab to Page B (still process X) which
   opens a session storage area.
3. The user closes Page B. The storage binding still exists in
   process X.
4. The user presses Ctrl+Shift+T, which re-opens Page B but in a
   new process (process Y).
5. Process Y now opens session storage at the same namspace & origin as
   step 2, which was already bound to process X.

R=mek@chromium.org

Bug: 856629
Change-Id: I6fd833ce1502ec3fb58443f92ac48cfb1b282f99
Reviewed-on: https://chromium-review.googlesource.com/1115867
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570610}

Move static private functions in AnchorElementMetrics to anonymous namespace.

Bug: 850624
Change-Id: I5429b8ce97d9259a761f16717bad3e3ae88fe774
Reviewed-on: https://chromium-review.googlesource.com/1115814Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Lu Chen <chelu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570609}

If a client wants to enable BLE scanning, it should take a ScanHandle.
When all ScanHandles are destroyed, scanning will be disabled.

This is to avoid clients from fighting with each other to determine if
BLE scanning should be enabled or not.

Bug: b/110432359
Test: cast_bluetooth_unittests, device_unittests, manual.
Change-Id: I4d88a602364816837670b7260a3c4934583cc7d5
Reviewed-on: https://chromium-review.googlesource.com/1115912Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Stephen Lanham <slan@chromium.org>
Commit-Queue: Bailey Forrest <bcf@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570608}

This data's been collected for some time, but due to an oversight
wasn't being visualized on the UMA dashboard.

Bug: 852884
Tbr: isherman@chromium.org
Change-Id: Id22a09ed788fa29172884d6f981e4acef52c4a19
Reviewed-on: https://chromium-review.googlesource.com/1114235
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570607}

https://chromium.googlesource.com/catapult.git/+log/33319d66254b..8b52973effb8


git log 33319d66254b..8b52973effb8 --date=short --no-merges --format='%ad %ae %s'
2018-06-26 nednguyen@google.com Update traffic settings to better reflect the settings by devtool
2018-06-26 pasko@chromium.org androidStartupMetric: support multiple browser starts


Created with:
  gclient setdep -r src/third_party/catapult@8b52973effb8

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

BUG=chromium:760498
TBR=sullivan@chromium.org

Change-Id: I7034a77e379617d2f48727d63ff9d3d6aa6a7b12
Reviewed-on: https://chromium-review.googlesource.com/1115413Reviewed-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@{#570606}

Use CurrentSupportedVersions instead of AllSupportedVersions in the QUIC client to avoid using v99 by default.

Change-Id: Ie45d10894460c6fb92342a38ecf019016ce0be72
Reviewed-on: https://chromium-review.googlesource.com/1115968Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570605}

Apply scrim to solid color image tiles so the user will know what
the background will actually look like. This will be removed when
background previews are implemented.

Bug: 855685
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ic9791a504250378da217038779a75f40c8654bac
Reviewed-on: https://chromium-review.googlesource.com/1115199
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570604}

Enables mojo_core to build as a data dependency of the Chrome binary on
Windows, as it already does for Chrome OS builds.

Also adds the ability for applications to point to a specific mojo_core
DLL path before falling back onto the MOJO_CORE_LIBRARY_PATH environment
variable.

This only causes the DLL to build as a side effect of normal Chrome
builds, and enables the corresponding mojo_core_unittests suite to be
run on Windows bots. The DLL is not yet included in any Chrome installer
builds.

Bug: 855894
Change-Id: Iecb19e0efda73b485269cf23fb0f2ceb6891fcb9
Reviewed-on: https://chromium-review.googlesource.com/1112923Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570603}

In earlier CLs I hadn't matched the migration away from GYP to GN in
the Settings UI closure compilation. This is that migration for
the multidevice folder.


Bug: 632206
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I2ad09426c87c5453b26e0a7d5bbe3957ccc0a1ca
Reviewed-on: https://chromium-review.googlesource.com/1115758Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Jordy Greenblatt <jordynass@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570602}

Converting to a fixed scale PaintShader needs to take into account the
offset in the tile rect.  Previously, this was getting dropped.  It
needs to be scaled, and then subtracted from the picture that we replay
into.

Bug: 855292
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Icac412c29540c5c453dbd642567de2dda3b97523
Reviewed-on: https://chromium-review.googlesource.com/1115958Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570601}

The AttemptToSetMultiDeviceHostOnBackend() function will retry any
pending request immediately when called, but that was not explicitly
documented. Likewise, there was no explicit test for this behavior.

This CL addresses both of those issues; a follow-up CL will invoke
this class in the way that I'm describing.

Bug: 824568
Change-Id: I397455528498b3d52f7c505785f0be93dd0ce212
Reviewed-on: https://chromium-review.googlesource.com/1115735
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570600}

Clean up files in QUIC's core/congestion_control/ directory to remove code divergence with internal version.

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

We didn't get much value out of this UMA. The UMA for start worker
timings will also be changing so it's easiest to just remove this now.

It was intended to distinguish between time spent waiting for Blink to
setup and time spent waiting for the StartWorker IPC to arrive on the
main thread. I've updated the bug with the latest data.

Bug: 855952
Change-Id: Id8524271f0919c7c6a004145afc068c2ae477067
Reviewed-on: https://chromium-review.googlesource.com/1114534Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570598}

Change-Id: I67a8a39901dd164999b93190caf6f4886a404c11
Reviewed-on: https://chromium-review.googlesource.com/1068658
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Grace Kloba <klobag@chromium.org>
Reviewed-by: Chris Palmer <palmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570597}

Now that we have ClientHintsLifetimeFollowedByNoClientHintIncognito
browser test, we can remove ClientHintsHttpsIncognito test.

The former test covers all of the checks covered by the latter
one, and only creates one incognito browser profile, and so
is expected to be more reliable.

Bug: 850945
Change-Id: Ibd8095d02b2bc5ab79d6d08812063e4925149375
Reviewed-on: https://chromium-review.googlesource.com/1115974Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570596}

Fixes InkDrop clipping for non-centered (edge) ToolbarButtons when
rendered in RTL (when rendered flipped).

Bug: chromium:856510
Change-Id: Ie83bfc3b1fd1e8815dae25beeb83f86d89c375c4
Reviewed-on: https://chromium-review.googlesource.com/1115964Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570595}

So that we don't need to come back to the main thread for handling
subresource loading with SW. On a low-end device needing to post a
task on the main thread could add huge delay (due to main thread
contention).

This also changes the worker code path to create SubresourceLoader
on a background thread, but not on IO thread. (Because when NS is not
enabled we need to resolve Blob ptrs if request_body has Blobs, and that
require synchronous IPC that could introduce dead-lock if issued from
the IO thread)

Change-Id: Ibae07ae8fecd42bfcc9943ae1da129a4b062ca22
Bug: 854902
Reviewed-on: https://chromium-review.googlesource.com/1109662
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570594}

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

https://skia.googlesource.com/skia.git/+log/c1b6066263b1..5b201e3b0ba8


git log c1b6066263b1..5b201e3b0ba8 --date=short --no-merges --format='%ad %ae %s'
2018-06-26 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 5bdf8bd1cf56..0265e1ec1eb7 (26 commits)
2018-06-26 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader 41b7748432ef..659d89e94bf9 (2 commits)
2018-06-26 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-06-26 bungeman@google.com Improve CMakeLists.txt auto regeneration.
2018-06-26 jvanverth@google.com Fix some shadow issues.
2018-06-26 benjaminwagner@google.com [Bazel] Omit new test that causes infinite loop in libjpeg-turbo.
2018-06-26 brianosman@google.com Handle F32 in lazy image
2018-06-26 brianosman@google.com Reland "Revert "Update GPU DM/nanobench configs for color testing""
2018-06-26 brianosman@google.com Revert "Temporary fix for SkImage_Lazy handling of color spaces"
2018-06-26 bungeman@google.com Add subpixel offset to Viewer app.
2018-06-26 mtklein@chromium.org basic first pass at RGBA F32 support
2018-06-26 robertphillips@google.com Disable --gpuThreads when skpbenching DDLs
2018-06-26 egdaniel@google.com Remove Vulkan code that supported creating a GrVkRenderTarget.
2018-06-26 csmartdalton@google.com skpbench: Support .svg files
2018-06-26 brianosman@google.com Revert "Revert "Update GPU DM/nanobench configs for color testing""
2018-06-26 egdaniel@google.com Fix some static intializers in Vulkan code.
2018-06-26 scroggo@google.com Expose public factories for platform decoders
2018-06-26 bungeman@google.com Clean up includes in SkMallocPixelRef
2018-06-26 mtklein@chromium.org remove unused enum
2018-06-26 bsalomon@google.com Refactor GrPipeline dynamic state.
2018-06-26 robertphillips@google.com Add --gpuThreads support to skpbench.py (take 2)
2018-06-26 scroggo@google.com Update libjpeg-turbo to pre-2.0.0 (from 1.5.3)
2018-06-26 brianosman@google.com Temporary fix for SkImage_Lazy handling of color spaces
2018-06-26 reed@google.com move blurimagefilter.cpp back into effects


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

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:b/78329453
TBR=jcgregorio@chromium.org

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

This CL is 1/3 in effort to fix the regressions caused by sending
unneeded compositor frames.

This CL gives the SurfaceLayerBridge control over setting the opacity.
We need this because we will be creating the SurfaceLayer before we have
video, and need to be able to set the opacity to false when we have no
frames.

Bug: 829813
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I9eed6b08be0b050ad5c735762d824728263ff091
Reviewed-on: https://chromium-review.googlesource.com/1114092Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Commit-Queue: CJ DiMeglio <lethalantidote@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570591}

This reverts commit 06af064e.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 570570 as the
culprit for failures in the build cycles as shown on:
https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzA2YWYwNjRlZjVjZDhlZjIxODhiZTA0NzBkNzFmYmM1ZjFlMTIwNzYM

Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/6503

Sample Failed Step: compile

Original change's description:
> [CrOS MultiDevice] Add HostStatusProvider.
> 
> This class provides an interface for fetching the current host status
> and, when applicable, the current host device. Additionally, this class
> provides an observer interface for being notified when the status
> changes.
> 
> Bug: 824568
> Change-Id: I6cdc9a12f2201d998aa99080c63cbb6e6d60a60b
> Reviewed-on: https://chromium-review.googlesource.com/1113020
> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#570570}

Change-Id: I642011ecff3b79478838979d9617630986539302
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 824568
Reviewed-on: https://chromium-review.googlesource.com/1116158
Cr-Commit-Position: refs/heads/master@{#570590}

Bug: None
Change-Id: I9d7220fe76b0ca5e485dc73ccdb9d09bfb2f53f1
Reviewed-on: https://chromium-review.googlesource.com/1109300
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570589}

This reverts commit dc9251bd.

Reason for revert: headless_browsertests are flaky on Win7:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20Tests%20%28dbg%29%281%29. This looks like the only possible culprit.

Original change's description:
> Reapply "Headless: don't run unload hooks upon web contents close."
> 
> Change-Id: Ic98de1070c3cee34a926ee0a95eb05cd62345ce6
> Reviewed-on: https://chromium-review.googlesource.com/1113309
> Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
> Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#570003}

TBR=caseq@chromium.org,pfeldman@chromium.org

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

Change-Id: Idb3d74d77c445ee6e870ca3bf476e8a34374b0f9
Reviewed-on: https://chromium-review.googlesource.com/1115839Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570588}

https://pdfium.googlesource.com/pdfium.git/+log/c4dce690f433..bdf3f682d14d


git log c4dce690f433..bdf3f682d14d --date=short --no-merges --format='%ad %ae %s'
2018-06-26 tsepez@chromium.org Use UnownedPtr<> in cpdf_streamcontentparser
2018-06-26 tsepez@chromium.org Use UnownedPtr<> in CPDF_Font
2018-06-26 tsepez@chromium.org Use unowned ptr in CPDF_Cmap


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

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: I829f7b1443037a902726fc8ad94983d1ce47cce3
Reviewed-on: https://chromium-review.googlesource.com/1115740Reviewed-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@{#570587}

This reverts commit fbe272fb.

Reason for revert: exo_unittests are flaky on Linux ASan:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29?limit=200

Original change's description:
> Propagate flip layout proprety of the popups
> 
> BUG=788782
> TEST=manully tested with gtk3-demo
> 
> Change-Id: I4a381b9350675d4e5407b378fbe07ae9de64fe8a
> Reviewed-on: https://chromium-review.googlesource.com/1108558
> Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
> Reviewed-by: David Reveman <reveman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#569893}

TBR=reveman@chromium.org,oshima@chromium.org

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

Bug: 788782
Change-Id: Iae9444d706ff01f37787781955bfbbb8dff63c01
Reviewed-on: https://chromium-review.googlesource.com/1115918Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570586}

- Remove focus stealer and directly attach ax tree to contents view of
  widget delegate of focused widget.
- Returns contents view of widget delegate as focused view if no view is
  focused.

Bug: 852653
Test: Enable ChromeVox arc native support and confirm that it works.
Change-Id: I22feb9c79e54653a037a2b78b729d76fcbb29fa2
Reviewed-on: https://chromium-review.googlesource.com/1103982
Commit-Queue: Yuki Awano <yawano@chromium.org>
Reviewed-by: David Reveman <reveman@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570585}

I'm about to add another usage of a friend class accessing the raw
cryptauth::RemoteDevice, so I cleaned this up by adding an explicit
getter function for this case before continuing.

Bug: 824568
Change-Id: Ifb752ad72d18ba42f59e6bce82e63096c6251a53
Reviewed-on: https://chromium-review.googlesource.com/1115720
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570584}

Without this change, things like 120fps in 60hz (60fps @ 2x rate)
count every other frame as dropped since the cadence is [1:0].

Since dropped frames are used as performance indicators for various
sites, we shouldn't consider these as dropped when they were fully
considered and just chosen to be skipped for smoothness.

BUG=856772
TEST=YT 60fps @ 2x playback rate, updated unittests.

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
Change-Id: I9520504bd7cb48dfadf3f403121dcd59b739b4fe
Reviewed-on: https://chromium-review.googlesource.com/1115698
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570583}