GitLab

https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+log/4468d4967f5d..02ec9ce5a9bc

$ git log 4468d4967..02ec9ce5a --date=short --no-merges --format='%ad %ae %s'
2018-03-13 wolenetz Updating build configs for M67 roll.
2018-03-13 wolenetz Update build_ffmpeg.py's sysroot name for M67
2018-03-13 wolenetz Remove deprecated av_register_all from ffmpeg.sigs
2018-03-13 wolenetz Copy [de]muxer, codec and parser lists into configs
2018-03-12 wolenetz Update chromium patches README
2018-03-12 vdixit avformat/hlsenc: fix for zero EXTINF tag duration
2018-03-12 matthieu.bouron avcodec/mediacodecdec_common: make INFO_TRY_AGAIN trace messages more consistent
2018-03-10 aman avcodec/mediacodecdec: add debug logging around hw buffer lifecycle
2018-02-27 michael avcodec/nuv: rtjpeg with dimensions less than 16 would result in no decoded pixels thus reject it
2018-02-27 michael avcodec/nuv: Check for minimum input size for uncomprssed and rtjpeg
(...)

Created with:
  roll-dep src/third_party/ffmpeg

Includes removal of FFmpegGlue::InitializeFFmpeg() because
av_register_all is no longer needed (and is deprecated in FFmpeg).

BUG=803898, 772699, 786793, 791237, 791349, 795653, 796778, 800123, 817338

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I94ccecab95831174a3bae6e9a8422e10bfec8e85
Reviewed-on: https://chromium-review.googlesource.com/964248Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543531}

These classes represented Bluetooth Classic connections, which are no longer used.

R=khorimoto@chromium.org

Bug: none
Test: none
Change-Id: I8223f3afca936cf3711f4a73334e9d8aed80d9e1
Reviewed-on: https://chromium-review.googlesource.com/964624
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543530}

Bug: 818902
Test: added test coverage
Change-Id: Ie5c0edf874c50be60b48b37833fcf1e8991e5728
Reviewed-on: https://chromium-review.googlesource.com/963089
Commit-Queue: Qiang Xu <warx@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543529}

As a precursor to moving SDK thunks around and rewiring them, this
fixes some of the weird layering within //mojo/edk.

Namely this introduces a new //mojo/edk target to subsume the role
of //mojo/edk/system (aliased for now to avoid churn), and splits out
a source_set (//mojo/edk:core) for the bulk of the EDK impl with no
linkage dependencies on //mojo/public.

A follow-up patch (https://crrev.com/c/963548) will get rid of the
alias targets.

Bug: 822034
Change-Id: I6b45ce6e8bb9b3a5392ae8e5cdfb61bbc4761769
Reviewed-on: https://chromium-review.googlesource.com/963766
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543528}

We already were silencing most of this via stdout filtering, but there
are still some third-party libraries that were showing warnings. E.g.:

Warning: can't write resource [META-INF/maven/com.google.guava/guava/pom.xml] (Duplicate zip entry [espresso-core-release-no-dep.jar:META-INF/maven/com.google.guava/guava/pom.xml])

This change tells ProGuard to ignore these files, rather than filtering
the resulting errors

Change-Id: I288507de1f2c5576fbb0fea8bfebb189b2603c92
Reviewed-on: https://chromium-review.googlesource.com/963699Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Commit-Queue: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543527}

This reverts commit 93d6eba0.

Reason for revert: Failing webkit_unit_tests:
  RenderedPositionTest.PositionInScrollableRoot
  RenderedPositionTest.PositionInScroller/
on https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/4730

Original change's description:
> Make touch handles relative to scrolling contents
> 
> Selection bounds are sent from Blink to CC as part of a commit cycle so
> that we can draw touch handles for it. Currently, the selection bounds
> are relative to the main graphics layer of a CompositedLayerMapping. In
> the case of a scroller, this will be its clip rect - rather than its
> scrolling contents layer. Unfortunately, this means that scrolling on
> the compositor isn't applied as part of the ToScreen transformation on
> the selection bounds so scrolling wont update the selection bounds
> location until another Blink commit. This went unnoticed until now
> because the root layer was not considered a scroller. The page would
> paint into a document-sized layer and the compositor would provide extra
> scrolling layers to handle frame scrolling. In this configuration, the
> ToScreen transformation from the root layer does include the scroll
> offset.
> 
> Now that root layer scrolling has been turned on, frame scrolling works
> much the same as other scrollers. Thus, this shortcoming is seen on
> frame scrolling also.
> 
> The solution in this CL is to move the selection bounds rect to be
> relative to the scrolling contents layer - if one exists. The ToScreen
> transformation done in CC will correctly compensate for any scroll
> offset applied in the compositor and touch selection handles stick to
> the selection as its scrolled. For the CC side, see
> ComputeViewportSelectionBound in layer_tree_impl.cc
> 
> Bug: 812048
> Change-Id: I219ac3209d334ac91e9c13ffaaa51cbc9db57886
> Reviewed-on: https://chromium-review.googlesource.com/963006
> Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
> Commit-Queue: David Bokan <bokan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#543436}

TBR=bokan@chromium.org,chrishtr@chromium.org

Change-Id: I7ed3e4a8494caf31772af6eae2b25e3d4d13a330
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 812048
Reviewed-on: https://chromium-review.googlesource.com/965281Reviewed-by: Greg Levin <glevin@chromium.org>
Commit-Queue: Greg Levin <glevin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543526}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5d11b541fc9e..ceb1b20c4313

$ git log 5d11b541f..ceb1b20c4 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src-internal


The AutoRoll server is located here: https://src-internal-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=mmoss@chromium.org

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

Now that the web font timing issue for WPT in Blink has been fixed
(https://crbug.com/507054), these tests should no longer be flaky.
Remove the expectations.

Bug: 582836
Change-Id: I88f94b0f9133c8c787a358f00f06a76382e7d26e
Reviewed-on: https://chromium-review.googlesource.com/962704Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543524}

https://chromium.googlesource.com/angle/angle.git/+log/41918387cc52..44a73fcfbe2d

$ git log 41918387c..44a73fcfb --date=short --no-merges --format='%ad %ae %s'
2018-03-06 brandon1.jones Always Invalidate Vertex Attribute Translation

Created with:
  roll-dep src/third_party/angle


The AutoRoll server is located here: https://angle-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.android:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=cwallez@chromium.org

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

The background page only existed to support BT Classic flow, which is
now gone.

R=tengs@chromium.org

Bug: none
Test: none
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I4af74256299656a119507a209b875a213226fadd
Reviewed-on: https://chromium-review.googlesource.com/964909Reviewed-by: Tim Song <tengs@chromium.org>
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543522}

HttpCache::Transaction::ResetPartialState dooms the current entry, and
goes back to creating a new entry for this request. In case of parallel
validation, if the first request is a full request and has written some
part of the response to the cache, then this second transaction would
create the range header with as many bytes as the written response even
on dooming the current entry which is incorrect.
This CL fixes it by restoring the original range header on this path.

RangeGET_ParallelValidationCouldntConditionalize
Also manually verified the test case reported in the bug.

TEST: net_unittests --gtest_filter=HttpCache.
Bug: 820599
Change-Id: I4e57003193873e433c3b503b9fc20a843f28c4da
Reviewed-on: https://chromium-review.googlesource.com/959450Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Commit-Queue: Shivani Sharma <shivanisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543521}

Disabling pending a resolution to crashes observed in the associated
bug.

This change also removes the unused
GetSamplingParamsForCurrentProcess function and adapts
IsProfilerEnabledForCurrentProcess to operate on the current process
and specified thread.

The call to IsProfilerEnabledForCurrentProcess is also removed
from SetServiceManagerConnectorForChildProcess since that function is
only invoked in processes supporting the profiler.

Bug: 774682
Change-Id: Ibbc6f1bd9348ba09a3ee4db2e1595411617f1ccd
Reviewed-on: https://chromium-review.googlesource.com/962937
Commit-Queue: Mike Wittman <wittman@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543520}

Bug: None
Test: compiles & trybots
Change-Id: I29d5c39a018e6a2ddc0df3e123780f0bffd7aa99
Reviewed-on: https://chromium-review.googlesource.com/963650
Commit-Queue: Qiang Xu <warx@google.com>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543519}

This is a no-op because the BT classic flow is gone.

R=khorimoto@chromium.org

Bug: none
Test: none
Change-Id: I9a3c86e5c2fc7cacbf3d301dcae233ef5c04bfc8
Reviewed-on: https://chromium-review.googlesource.com/963308
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543518}

xdai@ is the owner and author of the code

BUG=None

Change-Id: I5d40ffeee2cf9c80bf715d1f1656d02b01696ed1
Reviewed-on: https://chromium-review.googlesource.com/965004Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543517}

This change prohibits a TableView column from becoming too narrow to show its
entire title.

Bug: 603440
Change-Id: I3184e5fedb6ac7d55792857ea5ba64f85dfedae8
Reviewed-on: https://chromium-review.googlesource.com/962354
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543516}

This CL also changes InstallationNotifier class to be compatible
with OCMock (UIApplication shared instance is not stored in ivar anymore)
and adds resetDispatcher method to allow restoring InstallationNotifier
to its default state.

Bug: 791806
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Iaee0d80938639d23862b254732eb49c97ddd4e86
Reviewed-on: https://chromium-review.googlesource.com/958123
Commit-Queue: Eugene But <eugenebut@chromium.org>
Reviewed-by: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543515}

Bug: 819462
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I364154d00b6fb138a7b1b85240b625984e36fee5
Reviewed-on: https://chromium-review.googlesource.com/961492
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543514}

https://pdfium.googlesource.com/pdfium.git/+log/d1ffda2acaee..35841fa4e3db

$ git log d1ffda2ac..35841fa4e --date=short --no-merges --format='%ad %ae %s'
2018-03-15 hnakashima Create FPDFPage_RemoveObject().
2018-03-15 rharrison Fixing order of guards to avoid potential segvs
2018-03-15 thestig Rename FX_COLORREF variables from "rgb" to "bgr".
2018-03-15 thestig Use Width()/Height() methods from rectangles.
2018-03-15 thestig Remove unused CPDFSDK_BAAnnot methods.
2018-03-15 thestig Fix a red-blue channel flip when rendering masks to EMF.

Created with:
  roll-dep src/third_party/pdfium
BUG=821672


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: If141edae0fe9d00e024a14545336834d172420e9
Reviewed-on: https://chromium-review.googlesource.com/964620
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#543513}

This CL wires 3 display/monitor fields from EDID parsing
to the Chrome private API where they surface, as described
in the DD [1], namely:
1- manufacturer id
2- product id
3- year of manufacture.

(Note that ToT Ozone DRM already parses this list's 1 and 2;
this CL adds code to parse 3). A diagram of the touched areas
is in the DD [1] extracted for quick access in:
  https://i.imgur.com/yx8H0R3.jpg (also [2]).
but in a nutshell: Ozone DRM creates a DisplaySnapshot from
the EDID, and passes it to Browser Process via Mojo and/or IPC
(being migrated); in Browser DisplayChangeObserver transforms that
snapshot into a ManagedDisplayInfo, and in turn passes it to the
DisplayManager that creates a Display that is used later on upon
request by DisplayInfoProviderChromeOS to fill in the JS data struct.

There's a bit of confusion on ToT between product_id and
product_code, so this CL follows the spec and aligns them all,
i.e. EDID parser produces a |product_code|, which is a pack of
the manufacturer id and product id.

Unittests extended, tested on soraka+simplechrome.

[1] go/js-edid-chromeos
[2] https://imgur.com/a/aqNDD

Bug: 821393
Change-Id: Ia219b4eeb92cf3eae3e58046340f1b81c34c9ea2
Reviewed-on: https://chromium-review.googlesource.com/959547
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543512}

https://chromium.googlesource.com/catapult.git/+log/1446cf3fe8a3..ee4c7175f67b

$ git log 1446cf3fe..ee4c7175f --date=short --no-merges --format='%ad %ae %s'
2018-03-15 nednguyen Store the failure message in story_run object for debugging failure reason
2018-03-15 simonhatch Dashboard - Fix 500 errors on single rev alerts
2018-03-15 simonhatch Dashboard - Make _CorrespondingRefTest into tasklet.

Created with:
  roll-dep src/third_party/catapult


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.


TBR=sullivan@chromium.org

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

This also does some cleanup.

BUG=268984

Change-Id: I936c148f22c8c9d18c90b795e2f3412831e9f122
Reviewed-on: https://chromium-review.googlesource.com/962719
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543510}

Now that we've updated Webview on the Android test device to the
latest version, adjust the test filter accordingly.

Change-Id: Ica6f14bda130683c8775ec9b8e072c123fada8f5
Reviewed-on: https://chromium-review.googlesource.com/964808Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543509}

This allows fetching policy for CHILD accunts. CHILD account is known
non-enterprise domain.

this moment it is empty. Add browser test.

Test: Manually. Validated that policy is fetched for CHILD account. At
Bug: 813892
Change-Id: I52440ab2737881499eb2e82f6a80eb0816f65542
Reviewed-on: https://chromium-review.googlesource.com/956962
Commit-Queue: Yury Khmel <khmel@google.com>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Reviewed-by: Drew Wilson <atwilson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543508}

This CL follows the approach described on crbug.com/808527 for
respecting element alignment in the linear layout.

Bug: 808527
Cq-Include-Trybots: luci.chromium.try:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ia11640da59ebcaf14ddd5d82df182ed7cacfd027
Reviewed-on: https://chromium-review.googlesource.com/964787Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543507}

The spec says that if an input to an AudioWorkletNode is not
connected, the input should be represented as an input with a single
channel with a Float32Array of length 0.

Make it so by passing in nullptr for that input to the
AudioWorkletGlobalScope::Process so it can fill the arrays
appropriately.

Bug: 817145
Change-Id: I82407ed0a9fe84c5012333af8af27f4dd08d29b8
Reviewed-on: https://chromium-review.googlesource.com/953970Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543506}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/1acdfd58..f585291b

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

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

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Idc8449bdad9dcc003db9fb9c611811bb4e86694f
Reviewed-on: https://chromium-review.googlesource.com/964391Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543505}

The AsyncClipboardAPI feature flag used to control access to the entire
async clipboard API, but (since we're now shipping the text portions of
the API) its meaning has been changed to control access only to the parts
of the API that are still under development (e.g., image and delayed
generation support).

The Clipboard permission is shipping as part of the text APIs, so it
should no longer be checking this feature flag.

Bug: 677564,821947
Change-Id: Ia57b57df3eae03c2d4372cf5e7472ef1d0532f49
Reviewed-on: https://chromium-review.googlesource.com/963287Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Gary Kacmarcik <garykac@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543504}

In PasswordEntryEditor, PASSWORD_ENTRY_ACTION_CANCELLED represented
the action of cancelling viewing of a password. This action no longer
maps to the current possible UI flows and its representation is
therefore marked as obsolete in this CL.

For more info see the discussion on the associated bug.

Bug: 807577
Change-Id: I79dc75a4d3a14cf1df7f46d1a5a2b26b664e5a0f
Reviewed-on: https://chromium-review.googlesource.com/962453Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Commit-Queue: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543503}

Change-Id: I00fc70141ef1afe1b926e0f9b72c7055d4d82917
Reviewed-on: https://chromium-review.googlesource.com/965007
Commit-Queue: Luna Lu <loonybear@chromium.org>
Reviewed-by: Luna Lu <loonybear@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543502}

This reverts commit 5b0cf7de.

Reason for revert: This CL is causing iOS payment integration test to fail. For example:

https://ci.chromium.org/buildbot/chromium.mac/ios-simulator-full-configs/3996

Original change's description:
> [Payments] Modernize test JavaScript
> 
> Before this patch, browser tests for PaymentRequest would print warnings
> about deprecation of:
> 1) Using an array for 'supportedMethods'.
> 2) Specifying card networks in 'supportedMethods'.
> 
> This patch modernizes the browser test by:
> 1) Converting single-element 'supportedMethods' arrays into strings.
> 2) Splitting up multi-element 'supportedMethods' arrays into arrays of
>    objects with a single string 'supportedMethods' value in each object.
> 3) Using 'basic-card' in 'supportedMethods'.
> 4) Specifying card networks in 'supportedNetworks'.
> 
> After this patch, browser tests for PaymentRequest don't print warnings
> about deprecation.
> 
> Bug: NONE
> Change-Id: I777f299ce32353fbf6a54fb4f839c3bfd19517a9
> Reviewed-on: https://chromium-review.googlesource.com/962928
> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
> Reviewed-by: anthonyvd <anthonyvd@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#543474}

TBR=rouslan@chromium.org,anthonyvd@chromium.org

Change-Id: Ifea0a8c26867af9746b4716564580f36e5f5e7d9
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: NONE
Reviewed-on: https://chromium-review.googlesource.com/965022Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543501}

Issue 964445 fixed the underlying reason for the crashes in these two
test, removing the Crash expectation.

Bug: 964445
Change-Id: Ia96ff6e14d00d2f599701a6586b8491c227e60ca
Tbr: kojii
Reviewed-on: https://chromium-review.googlesource.com/964762Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543500}

This reverts commit 5050d462.

Reason for revert: Failing some bots on L and M (Cannot create shot files java.io.IOException: open failed: EACCES (Permission denied)).

Original change's description:
> Create a top level ui screenshot description
> 
> Merge the screenshot descriptions produced by the instrumentation tests
> into a single description. If the tests are run locally print a link
> to this description, if the are run remotely add a link to the
> description to the json file produced by test_results_presentation
> 
> Change-Id: Ia9dd491460633148283bed66949cec47a410dea3
> Reviewed-on: https://chromium-review.googlesource.com/952972
> Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
> Reviewed-by: John Budorick <jbudorick@chromium.org>
> Commit-Queue: Anthony Berent <aberent@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#543393}

TBR=bauerb@chromium.org,aberent@chromium.org,jbudorick@chromium.org

Change-Id: Iafb4846c02ba54fcbfe5e4c5391bd1e5fbec540e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/964931Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543499}

This reverts commit 0a6d8978.

Reason for revert: touchpad-scroll-impl-to-main.html is a flaky test
that I changed it in the original cl and removed the tests expectations to see if the flake is fixed or not. Changing the test expectations caused unexpected test failure. In this reland I left the test expectations for touchpad-scroll-impl-to-main.html unchanged.

Original change's description:
> Revert "Send GSB before switching to mainthread scrolling in smooth scroll path."
>
> This reverts commit 5d5a062f.
>
> Reason for revert: added a failing test https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Win10/32246 see issue 822386
>
> bug: 822386
>
> Original change's description:
> > Send GSB before switching to mainthread scrolling in smooth scroll path.
> >
> > This cl is the equivalent of https://codereview.chromium.org/2854683002 fix for smooth scrolling
> > path,if the compositor handles the GSB and during the scrolling we have to switch to main thread
> > since the compositor cannot handle a GSU a GSB must be sent to the main thread since the original
> > GSB was handled on the compositor rather than being sent to the main thread.
> >
> > touchpad-scroll-impl-to-main.html is the test that forces switch from compositor thread to main
> > thread in the middle of scrolling. It used to get executed with --disable-smooth-scrolling
> > in this cl I've moved the test to a new virtual test suite that has default scroll animation
> > value.
> >
> > I have removed the test expectations since I have changed the test and this might fix the flake.
> >
> > subpixel-accumulation.html needs scroll animation to be disabled and that's why I had to move it to
> > a new test suite.
> >
> > Bug: 820979, 708499, 757165, 800840
> > Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
> > Change-Id: I21b1f4285897d74559f6827e6a232f007dc897b0
> > Reviewed-on: https://chromium-review.googlesource.com/961264
> > Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org>
> > Reviewed-by: Timothy Dresser <tdresser@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#543425}
>
> TBR=tdresser@chromium.org,sahel@chromium.org
>
> Change-Id: I3c5253d96d011c9723063effac91c969ee352305
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 820979, 708499, 757165, 800840
> Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
> Reviewed-on: https://chromium-review.googlesource.com/963388
> Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
> Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#543467}

TBR=tdresser@chromium.org,crouleau@chromium.org

Change-Id: I460ff89a12c94772564c77418f2c1e58c72314a6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 820979, 708499, 757165, 800840
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Reviewed-on: https://chromium-review.googlesource.com/964809
Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org>
Reviewed-by: Sahel Sharifymoghaddam <sahel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543498}

Most of the metrics were added to UKM in:
https://chromium-review.googlesource.com/c/chromium/src/+/939904
Some metrics were missed due to privacy review being stale.
This CL adds the remaining metrics after updating privacy doc

BUG=730783

Change-Id: Iec4cc7d6cc4f90c7fb57a9bd8cad23eef7e3dce9
Reviewed-on: https://chromium-review.googlesource.com/961538Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Siddhartha S <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543497}

https://skia.googlesource.com/skia.git/+log/945ac788d85d..e11d7932940b

$ git log 945ac788d..e11d79329 --date=short --no-merges --format='%ad %ae %s'
2018-03-15 reed detect non-finite pts
2018-03-15 benjaminwagner Upgrade OS and NVIDIA driver on Win10 Golo/MTV lab bots.
2018-03-15 robertphillips Disable CCPR path rendering in DDL mode
2018-03-15 robertphillips Add DDL SkpOnly bot
2018-03-15 borenet update_meta_config: Use new LUCI optional GPU trybot
2018-03-15 reed drawTextRSXform should not apply matrix to shader
2018-03-15 egdaniel Delete unused VkClearTest
2018-03-14 halcanary GrGLES: unify MakeNativeInterface_{android,egl}
2018-03-14 caryclark fix pathops fuzzers and debugging
2018-03-15 herb SkAutoGlyphCache change some sites to Find*.
2018-03-15 robertphillips Make CreateBackendFormatFromTexture shared code
2018-03-15 egdaniel Fix initialLayout update in Vk createTestingOnlyImage
2018-03-15 sugoi Check GL_EXT_texture_format_BGRA8888 before GL_APPLE_texture_format_BGRA8888
2018-03-14 caryclark protect PathMeasure against input paths with NaNs
2018-03-15 robertphillips Remove SK_RASTER_RECORDER_IMPLEMENTATION
2018-03-15 egdaniel Revert "ccpr: Unblacklist vulkan"
2018-03-14 egdaniel Make sure we set correct GrPixelConfig in promise images
2018-03-14 robertphillips Prepare ddl skp rendering for prime time

Created with:
  roll-dep src/third_party/skia


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:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=stephana@chromium.org

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

BlueZ bug makes it wrong to assume that the Discovering property is
updated when StartDiscovery/StopDiscovery returns (crbug.com/822104).
BlueZ bug fixing is deprioritized so here we remove the DCHECK first
until BlueZ bug is fixed.

BUG=814595
TEST=No longer crashes

Change-Id: I12c6d0df808553d3098525b70ab998d8c957b918
Reviewed-on: https://chromium-review.googlesource.com/963845Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
Commit-Queue: Sonny Sasaka <sonnysasaka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543495}

On this case, a call inside the loop may cause visible_pages_ to
change.

Bug: 822091
Change-Id: I41b0715faa6fe3e39203cd9142cf5ea38e59aefb
Reviewed-on: https://chromium-review.googlesource.com/964592Reviewed-by: dsinclair <dsinclair@chromium.org>
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543494}

As per recent discussions in the QUIC IETF Working Group,
the latter is reserved for implementations of the final RFC.

https://github.com/w3c/navigation-timing/issues/71

Change-Id: I743eb5fcca87b1191e046fd531d19a2ee6ce8bef
Reviewed-on: https://chromium-review.googlesource.com/963492Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543493}

Bug: 770983
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I237fe77422971a18476d85b60c1ad67d60aa39bd
Reviewed-on: https://chromium-review.googlesource.com/963643
Commit-Queue: John Wu <jzw@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Hiroshi Ichikawa <ichikawa@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543492}