GitLab

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/60e7f52377fd..dd2c588e3811


git log 60e7f52377fd..dd2c588e3811 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 recipe-roller@chromium.org Roll recipe dependencies (trivial).


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

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.


TBR=agable@chromium.org

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

This reverts commit b60e5cc0.

Reason for revert:

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

Sample Failed Build: https://ci.chromium.org/buildbot/chromium.linux/Cast%20Audio%20Linux/20069

Sample Failed Step: base_unittests

Original change's description:
> [PartitionAlloc] Add a flag to allow callers to zero-fill allocations.
> 
> This enables callers to avoid doing it themselves (centralizing the `memset` in
> 1 place, rather than duplicating it at every call site that wants it), and to
> allow the PartitionAlloc implementation to avoid doing it itself if the
> operating system has already zero'd the new page(s).
> 
> Bug: 864462,680657
> Change-Id: Ibeae0bf7b9f20238334bf9bc022d0f243a77ef11
> Reviewed-on: https://chromium-review.googlesource.com/1162825
> Commit-Queue: Chris Palmer <palmer@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Albert J. Wong <ajwong@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#589389}

Change-Id: Ifd54700a2acb141c458df69304d7ccdce2719cc5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 864462,680657
Reviewed-on: https://chromium-review.googlesource.com/1212346
Cr-Commit-Position: refs/heads/master@{#589404}

Metrics were added 5 years ago in r188357, but they lack metadata.

Bug: 879446
Change-Id: I42daa58100bd8ed6c7c2d13542913e56d82f6f37
Reviewed-on: https://chromium-review.googlesource.com/1208999
Commit-Queue: Trent Apted <tapted@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589403}

This might cause the GPU thread to block forever when shutting down the decoder,
as we could be waiting for an EGL fence that will never be signaled while
queuing an output buffer. See crrev.com/c/1133614.

Some changes are introduced to make sure that:
* Waiting for an EGL fence is no longer blocking and can be interrupted.
* Any tasks queued will check whether a destroy is pending upon starting, and
  early-exit if required.

TEST=ran VDA tests on peach-pi

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: I962cbead32b050cde4f4698b6717e96972d216d4
Reviewed-on: https://chromium-review.googlesource.com/1195225
Commit-Queue: David Staessens <dstaessens@chromium.org>
Reviewed-by: Pawel Osciak <posciak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589402}

Lets Tab's UserDataHost manage TabRedirectorHandler when it is used for
Tab. Also saves Tab from keeping the instance of it.

TabRedirectHandler now defines 3 new methods:

- from(Tab): Returns an instance associated with the Tab. If not present,
            creates a new instance.
- getOrNull(Tab): Similar to |from| but returns null if an instance is
            not present.
- swapFor(Tab): Replaced the current TabRedirectHandler for Tab with
            a new one.

Bug: 877878
Change-Id: I6fe3fcaaba9e5fcf4625bd74691b5a3634a31fce
Reviewed-on: https://chromium-review.googlesource.com/1201630Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589401}

The build error occurs if using `use_jumbo_build=true` in GN
configuration. The same variable name is used in the anonymous namespace
of content_settings_registry.cc and website_settings_registry.cc. It can
cause a name conflict during merging both files.

TBR=raymes@chromium.org
NOTRY=true

Bug: none
Change-Id: I33eeb5ff00a2ab113d28a63f0044442375b98df2
Reviewed-on: https://chromium-review.googlesource.com/1212422
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Reviewed-by: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#589400}

SecureChannel previously had no checks for when the BluetoothAdapter is
disabled or removed.

This CL adds an additional check within SecureChannelImpl that will
cancel a connection request early if the BluetoothAdapter is either
disabled or removed, as well as notify the client of the failure
reason.

Bug: 854366
Change-Id: I021435611c8a018da3e77a9eeb9c001311adada4
Reviewed-on: https://chromium-review.googlesource.com/1194675Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Kyle Qian <kyleqian@google.com>
Cr-Commit-Position: refs/heads/master@{#589399}

Bug: 859095
Change-Id: Ibe8a52dfacad07b1cb9f04e720af063f67f9a3b0
Reviewed-on: https://chromium-review.googlesource.com/1200838Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589398}

Bug: 876796
Change-Id: Ie369384f218fde83ae03f21add99c0573ab97912
Reviewed-on: https://chromium-review.googlesource.com/1211915Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Commit-Queue: Jordy Greenblatt <jordynass@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589397}

Using wpt-import in Chromium 16d88668.

Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/24197

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

NOAUTOREVERT=true
TBR=kyleju

No-Export: true
Change-Id: I69b85c21b76a2e2d292464de225046888d974067
Reviewed-on: https://chromium-review.googlesource.com/1211676
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589396}

This is to support per-board configuration for uni-builds.
Related CLs: crrev.com/c/1208892, crrev.com/i/673295

TEST=Manually on device, test data restructured to be covered by unit
     tests
BUG=b:113908266

Change-Id: I56b3268390ce31e28204e53d443d465a032a84f4
Reviewed-on: https://chromium-review.googlesource.com/1208195
Commit-Queue: Yury Khmel <khmel@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589395}

Content Security Policy does not allow the translate element.js script
to download and execute additional javascript. To get around this, we
redirect to the browser to download and execute the two additional
scripts (main.js and element_main.js).

Bug: 686364
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Ie92f357b9809a0e4efc0ff111e8593f727b936d4
Reviewed-on: https://chromium-review.googlesource.com/1131826
Commit-Queue: John Wu <jzw@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589394}

This re-instates the behavior where Incognito profiles have their
in-memory DB seeded by the on-disk DB of the original profile. This
was temporarily disabled to fix the UAF for M69 release.

This CL adds a CHECK in the destructor of seed DB which will fire
whenever it it is destroyed while a dependent in-memory DB is still
alive.

TBR: droger@chromium.org
Bug: 865321
Test: new unit test, manual testing.
Change-Id: I7c873369b1ffbd3259273c628190ee1cc581b45e
Reviewed-on: https://chromium-review.googlesource.com/1208253
Commit-Queue: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589393}

Adapted the v4l2 video decoder to make use of the GLFenceEGL wrapper, rather
than using EGLSync functionality directly.

Benefits:
* Better code reuse and less code duplication.
* Makes it easier to mock out dependencies when unit testing.
* Easier to swap to different implementation if required.

TEST=ran VDA tests on peach-pi

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: If3f9ab3668bb9e6764b983557e8d9ccd6b3c2cf7
Reviewed-on: https://chromium-review.googlesource.com/1195203
Commit-Queue: David Staessens <dstaessens@chromium.org>
Reviewed-by: Pawel Osciak <posciak@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589392}

https://swiftshader.googlesource.com/SwiftShader.git/+log/fe5861b..108f3e1

BUG=

TBR=kbr@chromium.org

TEST=bots

CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

Change-Id: I041ca25a69e441a98cc0b9168e722c2c93bbc8b5
Reviewed-on: https://chromium-review.googlesource.com/1211864Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Commit-Queue: Nicolas Capens <capn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589391}

https://chromium.googlesource.com/angle/angle.git/+log/4d42ef39658b..801719235b13


git log 4d42ef39658b..801719235b13 --date=short --no-merges --format='%ad %ae %s'
2018-09-06 courtneygo@google.com Add rules file for ANGLE apk


Created with:
  gclient setdep -r src/third_party/angle@801719235b13

The AutoRoll server is located here: https://autoroll.skia.org/r/angle-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: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=fjhenigman@chromium.org

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

This enables callers to avoid doing it themselves (centralizing the `memset` in
1 place, rather than duplicating it at every call site that wants it), and to
allow the PartitionAlloc implementation to avoid doing it itself if the
operating system has already zero'd the new page(s).

Bug: 864462,680657
Change-Id: Ibeae0bf7b9f20238334bf9bc022d0f243a77ef11
Reviewed-on: https://chromium-review.googlesource.com/1162825
Commit-Queue: Chris Palmer <palmer@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589389}

Chrome, Safari, and Firefox pass. Edge hasn't implemented yet.

The test still holds for the proposed new spec text in
https://github.com/whatwg/html/pull/3686

This scenario is discussed at the end of
https://github.com/whatwg/html/issues/603 but the conclusion drawn
appears (to me) to be opposite what Chrome, Safari, and Firefox do.

Related other issues:
https://github.com/w3c/csswg-drafts/issues/2084
https://github.com/whatwg/html/issues/1839

Bug: 635282
Change-Id: Ice95225b3c9d5d90b80c657643d036490fd2e1b2
Reviewed-on: https://chromium-review.googlesource.com/1153651
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589388}

Create a class, DeviceReenroller, that compares GcmDeviceInfo's list of
supported SoftwareFeatures--eg., BETTER_TOGETHER_CLIENT or
MAGIC_TETHER_CLIENT--with those stored in the local device metadata on the
CryptAuth server. If a SoftwareFeature state has changed from supported to
unsupported, or vice versa, then re-enroll the device with CryptAuth. Finally,
after a successful re-enrollment, re-sync with CryptAuth and verify that the
local device metadata was updated correctly.

The flow is as follows:

1) The supported states of CrOS-relevant SoftwareFeatures are set in
//src/chrome/browser/chromeos/cryptauth/gcm_device_info_provider_impl.cc, based
on FeatureList flags.

2) This information is stored in GcmDeviceInfo, which is passed along to the
MultiDeviceSetupService via a ctor argument.

3) On creation, MultiDeviceSetupImpl creates a DeviceReenroller, providing it
   - a DeviceSyncClient, for communicating with CryptAuth to retrieve local
     device metadata, to re-enroll the device, and to sync the device;
   - and access to GcmDeviceInfo, in order to retrieve the latest list of
     supported SoftwareFeatures.

4) In the DeviceReenroller constructor, the supported software features from
the local device metadata are compared with the latest supported-state given
by GcmDeviceInfo's supported_software_features list.

5) If any supported-state changed, a re-enrollment is attempted via the
DeviceSyncClient.

6) If the re-enrollment is successful, a device sync is attempted via the
  DeviceSyncClient.
  - If the re-enrollment is unsuccessful, another attempt is scheduled to
    run after 5 minutes.

7) If the device sync is unsuccessful, another attempt is scheduled to
    run after 5 minutes.

Note that DeviceReenroller logic only runs when the MultiDeviceSetupService is
created, except for possibly retrying failed enrollments or syncs after some
delay. It does NOT act as an observer, checking for changes to GcmDeviceInfo's
supported features list, because we only expect this to change when Chrome
flags change, i.e., when the Chrome binary restarts.

Bug: 870770
Change-Id: I5f26a68448f3ee0e5dd8759aac12d05d1e4760a6
Reviewed-on: https://chromium-review.googlesource.com/1182419Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Josh Nohle <nohle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589387}

Servers set the download filename in a URL syntax (either through the
Content-Disposition header, or in the filename of the requested URL
itself). Previously, characters would remain percent-encoded when saved
to disk, if they are deemed unsuitable for display. This criteria makes
no sense for setting a filename.

Cases included:
- Control characters.
- Path separators.
- Special URL characters such as '%', '+', '&' and '#'.
- Spoofing characters, such as invisible characters.

Now, all characters are unescaped. Characters that are illegal in
filenames (such as control characters, path separators, colons, etc) are
converted into underscores. Other characters are left bare.

Fixed and added tests.

Bug: 849794
Change-Id: I797ee3d6aa8b803d9a7227e821fd8b4d55d0c58d
Reviewed-on: https://chromium-review.googlesource.com/1209003Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589386}

Bookmark matches' |allowed_to_be_default_match| depends on
|prevent_inline_autocomplete| being false. This field can be set and
copied before |prevent| is set. The bookmark provider was returning
cached results assuming |prevent| was still set. This CL changes the
bookmark provider to never cache, and always generate and return
fresh results.

Bug: 879905
Change-Id: I909364500417cd629cead52a6f430b6d488142b9
Reviewed-on: https://chromium-review.googlesource.com/1204270Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Kevin Bailey <krb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589385}

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context: https://crbug.com/805539

The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-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=gbiv@chromium.org

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

We used to only check the policy on attaching, but we should
also check it when navigating, similar to other session restrictions.

Bug: 880476
Change-Id: I8cbfe149d67eadbc2f723652d140f2cd0925c44c
Reviewed-on: https://chromium-review.googlesource.com/1211948
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589383}

Following bot results are included.
9416 9428 9434 9436 9437 9440 9442 9443 9444 9452 9458 9469
9470 9473 9474 9476 9477 9481 9488

10 lines were removed and 5 lines were deflaked by consecutive
results since 9443.

TBR=eae@chromium.org, mstensho@chromium.org
NOTRY=true

Bug: 591099
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I220acf8a940d306a081f8f453c18f87e8a4e3ac6
Reviewed-on: https://chromium-review.googlesource.com/1203482
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589382}

This a a follow-up to introducing viz::GpuHostImpl (crrev/c/1180658).
This includes:
 - Removing an expired CHECK;
 - Limiting GpuHost::SetChildSurface() to Windows;
 - Removing unused GpuProcessHost::OnDestroyingVideoSurfaceAck().

BUG=709332

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: Ida7488d887ff5d511b53e8e6997835486572b648
Reviewed-on: https://chromium-review.googlesource.com/1195545
Commit-Queue: Mohsen Izadi <mohsen@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589381}

https://pdfium.googlesource.com/pdfium.git/+log/aaff8f8b902a..1881cb7591c7


git log aaff8f8b902a..1881cb7591c7 --date=short --no-merges --format='%ad %ae %s'
2018-09-06 tsepez@chromium.org Rename CFX_GifContext::ReadData() to ReadAllOrNone()


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

The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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=dsinclair@chromium.org

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

Bug: 881619
Change-Id: I9a7916c4391117e570b08477852c3d77c8ce0468
Reviewed-on: https://chromium-review.googlesource.com/1212086Reviewed-by: Peter Williamson <petewil@chromium.org>
Commit-Queue: Jian Li <jianli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589379}

This change fixes an issue where FileDescriptors were being duplicated,
and as a result leaked, when writing them into a proto to send over
D-Bus

Bug: chromium:881615
Change-Id: I6e7e7abce34a537c3d9228cf9baa6d1d9074625f
Reviewed-on: https://chromium-review.googlesource.com/1211877Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589378}

This was making refactoring for https://crbug.com/879958 difficult.

Closure-compile existing unit_tests for the image_loader extension, and
delete the handcrafted unittest.html files.

Bug: 860355
Change-Id: I0d99d0383eb8fe48813d9142a14ce9af28da2dc5
Reviewed-on: https://chromium-review.googlesource.com/1207784Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589377}

This replaces the hard-coded relay bandwidth cap of 8000Kbps with
the value of maxRateKbps (if present) in the ICE config response from
the TURN server. If the value is not present, no cap is applied.

Bug: 880462
Change-Id: I0d8d2a48f78559e93cff94055a65da7ec32de494
Reviewed-on: https://chromium-review.googlesource.com/1211668Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589376}

This CL is a part of changes for 'Drag and Drop' on wayland and
extends WaylandDataDevice, WaylandDataSource and WaylandDataOffer.

WaylandDataDevice registers event listeners for 'drag and drop',
has 'StartDrag' API connected with 'wl_data_device_start_drag' and
includes reading the data from Wayland.

WaylandDataSource registers event listeners for 'drag and drop' to
handle at a source side and writes the data to the fd delivered
from Wayland when it gets 'OnSend' event.

WaylandDataOffer gets the operation decided by Wayland and requests
the offered data by Wayland.

FakeServer is also extended to support the various compositor side
functionalities needed so that tests 'drag-and-drop' in
wayland_data_device_unittest.cc run. MockDataDevice, MockDataOffer
and MockDataSource classes are extended, implementing the respective
Wayland compositor hooks to communicate with Wayland clients
(eg Ozone/Wayland).

Flow:
1) Sending dragging
'WaylandDataDevice::StartDrag' triggers the drag action to Wayland,
Wayland requests the data through 'WaylandDataSource::OnSend' and
'WaylandDataSource' listens the status through 'OnCancel' or
'OnDnDDropPerformed'.

2) Getting dragging
'WaylandDataDevice' listens drag-and-drop status such as entered/
moved/dropped/left. When the drop action is performed,
'WaylandDataDevice' reads the data using 'WaylandDataOffer'.

BUG=875164
TEST=ozone_unittests

Change-Id: Ic1ad80fce4ac396385f3ba6780839ef31d717683
Reviewed-on: https://chromium-review.googlesource.com/1176891Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Maksim Sisov <msisov@igalia.com>
Commit-Queue: Julie Jeongeun Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/master@{#589375}

https://skia.googlesource.com/skia.git/+log/e8161dd154d7..106d04e907c1


git log e8161dd154d7..106d04e907c1 --date=short --no-merges --format='%ad %ae %s'
2018-09-06 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader 108f3e10f093..a062f321768d (1 commits)
2018-09-06 brianosman@google.com Only run image tests on Windows once
2018-09-06 mtklein@google.com clean up legacy flags
2018-09-06 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader 787e3d5b4cb5..108f3e10f093 (1 commits)
2018-09-06 herb@google.com Calculate numPlotsY from height
2018-09-06 mtklein@google.com clamp after color pipeline when dst is normalized
2018-09-06 mtklein@google.com add profile->profile mode to imgcvt
2018-09-06 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader ad5c2952ca88..787e3d5b4cb5 (1 commits)


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

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

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

Previously the clip mask was painted at wrong place.

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I73ffd1011ae04c7751c1efff52e63bd6186a9483
Reviewed-on: https://chromium-review.googlesource.com/1211968
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589373}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/b56a43a9064c..60e7f52377fd


git log b56a43a9064c..60e7f52377fd --date=short --no-merges --format='%ad %ae %s'
2018-09-06 nodir@google.com [bot_update] Stop using revision and parent_got_revision properties
2018-09-06 nodir@google.com [gclient] Start actively using repo_path_map
2018-09-06 nodir@chromium.org Revert "bot_update: Specify the target branch for patch_refs."


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

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:877161,chromium:877161,chromium:870279
TBR=agable@chromium.org

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

 - Nested controls are removed:
 The aria attributes of buttons inside <a> links are removed,
 so they won't be read twice by a screen reader.

 - Missing aria labels are added to radio buttons.

Bug: 853996
Change-Id: I9e009425c4d6cc0c03135856135fb830d96cf989
Reviewed-on: https://chromium-review.googlesource.com/1206810
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Reviewed-by: Scott Chen <scottchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589371}

Background fetch wasn't unregistering the provider on destruction which
is why there was a crash when trying to open download home.

Bug: 877670
Change-Id: I955a65694fb67aa8d4285a8e18ff2a37f2b220cc
Reviewed-on: https://chromium-review.googlesource.com/1211623Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589370}

Offline Pages namespaces can be configured to only allow its pages to be
presented in their original tabs. This is enforced using an undeclared
convention that pages for these namespaces will store the tab id value
in the ClientId::id field for their pages. This change makes this
convention more explicit.

Bug: 879801
Change-Id: I3ab3d871abb41d6de9112c55d8b3d8b6491c7386
Reviewed-on: https://chromium-review.googlesource.com/1200389
Commit-Queue: Carlos Knippschild <carlosk@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589369}

DirectoryLoader contains a feature where it can fast fetch a directory based on
the start page token for the parent and the start page token that represents the
last time the directory was fetched.

Each team drive has it's own start page token, and in this case we were not
passing the team_drive_id when fetching the start page token, which means we
were getting the start page token for the users default corpus, which
effectively broke fast fetching for team drives.

The fix is to pass the team drive id to directory loader so it can then
retrieve the right start page token from resource metadata.

Patch comes with a test \o/.

Bug: 783184
Change-Id: Ic8c19efe8ea9bbffa4c97ba0a0d49f5debe2c97b
Reviewed-on: https://chromium-review.googlesource.com/1207779
Commit-Queue: Stuart Langley <slangley@chromium.org>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589368}

Since desktop capture has moved to using its own buffer pool implementation,
method ResurrectLastForProducer() in media::VideoCaptureBufferPool is no
longer used. This CL removes the method.

Bug: 879264
Change-Id: Ia24c683c8e63bc5b0d1bdc800e8c7d491f7c7c89
Reviewed-on: https://chromium-review.googlesource.com/1208952Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Weiyong Yao <braveyao@chromium.org>
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589367}

This patch allows updateWith() take shippingAddressErrors parameter.

Test: chrome/browser/ui/views/payments/shipping_address_editor_view_controller_browsertest.cc

Bug: 861704
Change-Id: I6c67e0c6c8fbd56d389ab279a1bc7816983a6b65
Reviewed-on: https://chromium-review.googlesource.com/1201625Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#589366}