GitLab

Test has been flaky on iOS13 simulators since it was enabled in:
https://chromium-review.googlesource.com/c/chromium/src/+/1804214

TBR=michaeldo@chromium.org

Change-Id: I3f76bd737d3f7c42e544489c24b6abcb54346ee4
Bug: 1007986
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823892Reviewed-by: Sebastien Lalancette <seblalancette@chromium.org>
Auto-Submit: Sebastien Lalancette <seblalancette@chromium.org>
Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699797}

This CL adds boarders between permission toggles to help guide the user
when App Management is being used on a device with a touch screen.

Before (without border): https://bugs.chromium.org/p/chromium/issues/attachment?aid=413406&signed_aid=gaumzEtlv1JcHLrQECRcqQ==&inline=1
After (with border): https://bugs.chromium.org/p/chromium/issues/attachment?aid=413407&signed_aid=L9yUkITEkaSUjJ4iHODEjg==&inline=1

Bug: 1007163
Change-Id: I6410e51bbf119879a5376af698b5fba15c86c050
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1820499
Auto-Submit: Jeevan Shikaram <jshikaram@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Commit-Queue: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699796}

Currently service workers only have site_for_cookies to perform
access checks. To correctly handle content settings that specify a
secondary pattern, they additionally need to know the top_frame_origin.

Bug: 988398
Change-Id: I97007f8cab25b64f792f5f69bc6c73ac835ba3a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754007Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699795}

This part of 0d2db6ea wasn't correctly
exported in https://github.com/web-platform-tests/wpt/pull/19124 and
then reverted by dd5d2254.

Bug: 1007920e
Change-Id: I0090bfc009c1faa994323af69d2994f38d4790f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824266Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699794}

Usually, the resolved value of grid-template-rows/columns is the used
value, expanding the repeat() notation. But for elements with a non-grid
display, the resolved value is just the computed value, with repeat(),
since the used value doesn't exist.
Before this patch, the repeat() was dropped, and line names after it
appeared at the wrong position or were also dropped. There was also an
assert failure in debug. This patch fixes the serialization for auto
repeat(). Integer repeat() is still expanded at computed-value time, so
it's not preserved in getComputedStyle().

Spec: https://drafts.csswg.org/css-grid/#resolved-track-list

BUG=988516

TEST=external/wpt/css/css-grid/parsing/grid-template-columns-computed-nogrid.html
TEST=external/wpt/css/css-grid/parsing/grid-template-columns-computed.html
TEST=external/wpt/css/css-grid/parsing/grid-template-rows-computed-nogrid.html
TEST=external/wpt/css/css-grid/parsing/grid-template-rows-computed.html

There are some test failures because integer repeat() is still expanded
at computed-value time (http://crbug.com/989004).

Change-Id: Ia262102472f2270cc9fed97a76f2766a1c17e931
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724517
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/master@{#699793}

Bug: 1005568
Change-Id: Ia88783b47d8048f8b8e946b7c3492b7920f57cc3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821858
Commit-Queue: Allen Bauer <kylixrd@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Auto-Submit: Allen Bauer <kylixrd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699792}

This CL implements a garbage collection routine for device info. This
routine is run on every startup of sync. This is okay from performance
point of view as all data is anyway in memory at this stage and number
of entities we iterate over is small.

Bug: 1007233
Change-Id: Icd6165a532a67218bcdf1d4d275b5b12cddbfaf9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821785
Commit-Queue: Jan Krcal <jkrcal@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699791}

Change-Id: I37527df498582dd0df2a3433d815fc8c303983fc
Bug: 875768
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823862Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Matthias Körber <koerber@google.com>
Cr-Commit-Position: refs/heads/master@{#699790}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/87177fcb..ddfa91df

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I2105a213955d9f592ce9127b9069f70071608795
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823796Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#699789}

OzonePlatform::AfterSandboxEntry() should only be called when GPU is run
as a separate process (whether it is sandboxed or not). If GPU is
in-process, the embedders should not call AfterSandboxEntry(). This CL
updates ozone embedders and ozone implementations to adhere to this
requirement. Comments are also updated to reflect this requirement
clearly.

BUG=998113

Change-Id: I86a479131df463137185fc3217ce12dab107159e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1807700Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Jonathan Backer <backer@chromium.org>
Commit-Queue: Mohsen Izadi <mohsen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699788}

Change-Id: I8515db5ea2ba09a125fbeb1a31447adb7ee76fcd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823872Reviewed-by: Yang Guo <yangguo@chromium.org>
Commit-Queue: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699787}

FirstRunChromeSigninViewController is being leaked when of all those
conditions are true:
 + it is the delegate of its own presentation controller.
 + it is shown inside a navigation view controller in second and last
position.
 + the navigation view controller is dismissed with the view controller
displayed.

Then a retain cycle is created with FirstRunChromeSigninViewController
and UIFormSheetPresentationController.
This is a bug in iOS, and should not happen.
Since FirstRunChromeSigninViewController cannot be swiped to be
dismissed, it doesn't need to be the delegate of its presentation
controller.

The fix is to not set the presentation controller delegate if the view
controller is not part of a navigation controller.
The fix is done in ChromeSigninViewController since
FirstRunChromeSigninViewController is a subclass of if.

Apple Feedback: https://feedbackassistant.apple.com/form-response/15480140

Bug: 1004695
Change-Id: I85f7721c4bef1c95d6d30abfd06e4ce83954209f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823198Reviewed-by: Stepan Khapugin <stkhapugin@chromium.org>
Commit-Queue: Jérôme Lebel <jlebel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699786}

The implementation code of the Fragment and the class actually extending
Fragment live in different ClassLoaders. Thus we need to forward calls
back and forth through aidl interfaces.

Change-Id: I765d116480778ce4d0c82dece91550c85855e950
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1813299Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Pavel Shmakov <pshmakov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699785}

When the token for the unconsented primary account (UPA) was revoked, the
cookies information becomes stale, and the UPA was not updated until the
cookies were refreshed.

However, in this case the UPA should be removed immediately.

This CL fixes a crash where sync was expecting the UPA to be immediately
reset when the token is revoked.

Change-Id: I4b68206a93e2faed52045b813aab6e0e5f2bca6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824467
Auto-Submit: David Roger <droger@chromium.org>
Commit-Queue: Monica Basta <msalama@chromium.org>
Reviewed-by: Monica Basta <msalama@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699784}

https://android.googlesource.com/platform/external/perfetto.git/+log/0c127f488fdb..8adff0796b31

git log 0c127f488fdb..8adff0796b31 --date=short --no-merges --format='%ad %ae %s'
2019-09-25 lalitm@google.com Merge "trace_processor: add support for Android async slices"
2019-09-25 eseckler@google.com Merge "Add public dep for adding categories to data source descriptors"

Created with:
  gclient setdep -r src/third_party/perfetto@8adff0796b31

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-chromium-autoroll
Please CC perfetto-bugs@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

TBR=perfetto-bugs@google.com

Bug: None
Change-Id: I9c1fb7858fce24f71bb075f9912560b0e088dcd2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825078Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#699783}

The VID:PID for the camera is 1bcf:2985
It has been reported to not work correctly on HD mode.
Suspect of advertising video modes that are actually unsupported.

Bug: 1007317
Change-Id: Ic0d83881f869169dd29297fbd6e9c233ea28b429
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824896
Auto-Submit: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Armando Miraglia <armax@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699782}

Sample: https://imgur.com/a/NmdDrkc

Bug: chromium:1004203
Change-Id: I8bae4fcd3db4ad54322883c673002e28f67be3f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1818524
Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699781}

Due to bad revert (https://crrev.com/c/1824299) we have compilation
error on ToT with chrome branded flag enabled (looks like we don't have
a buildbot with is_chrome_branded in args.gn). This commit is a small
fix for this.

TBR=ortuno@chromium.org,raymes@chromium.org,benwells@chromium.org

Change-Id: Ic4d375007ca87e8e6037b77bd01472000f523fbc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824894Reviewed-by: Oleg Davydov <burunduk@chromium.org>
Commit-Queue: Oleg Davydov <burunduk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699780}

See https://drafts.csswg.org/web-animations-1/#current

Bug: 1005852
Change-Id: I76390e0bc99078b5c1644970ef1985492414e6e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1814638
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699779}

This includes the upgrade to Esprima master

Change-Id: I491b9c17c0b6e448ba04ee215f8f5cee2c6da093
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824084
Commit-Queue: Tim Van der Lippe <tvanderlippe@chromium.org>
Commit-Queue: Yang Guo <yangguo@chromium.org>
Auto-Submit: Tim Van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699778}

https://webrtc.googlesource.com/src.git/+log/90d6efbd4eb4..e32ae4f8fb8f

git log 90d6efbd4eb4..e32ae4f8fb8f --date=short --no-merges --format='%ad %ae %s'
2019-09-25 eshr@google.com Invalidate encoder rates on VideoStreamEncoder::ReconfigureEncoder
2019-09-25 peah@webrtc.org Moving e to comply to the rest of the stack/heap storage scheme

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

TBR=webrtc-chromium-sheriffs-robots@google.com

Bug: None
Change-Id: I526468413fd04b0daeb4feb4381b6a42c20bf7c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825079Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#699777}

1.set_hide_on_outside_click (didn't have implementation)
2.SetTypesetter.

Bug: 875768
Change-Id: Id9485a040833f96f6e0be3705ab0a3cb7f2cc6cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824891Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699776}

It doesn't need a flag now and is not used anywhere yet.

Bug: 1005746
Change-Id: I22190ebf4d808984efc37fcfe69e4f23663c4088
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821521Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Rafał Godlewski <rgod@google.com>
Cr-Commit-Position: refs/heads/master@{#699775}

Bug: https://github.com/w3c/csswg-drafts/issues/4331
Change-Id: I82de40b04f5a59a21708724e3c30b2de14818a2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1822622Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699774}

This CL is preparation for cleaning PasswordAutofillAgent.

Bug: 949519

Change-Id: I0917c681f707f5b77230b73a34f0bbf5981f3f81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821477
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699773}

The patch migrates away from some APIs that won't exist in the future
and adopts NigoriKeyBag more broadly to avoid dealing with strings.

Bug: 967417
Change-Id: Ieb4b9461fe2a4704b79539994ce92b9e25bff2b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821780
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Maksim Moskvitin <mmoskvitin@google.com>
Cr-Commit-Position: refs/heads/master@{#699772}

Bug: 999235
Change-Id: I20987927f65a36f0d82bd834b1b8f0b4c24f0ae4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824047
Commit-Queue: Adam Rice <ricea@chromium.org>
Auto-Submit: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699771}

This patch parses clamp() in 'sizes' attribute into nested
max(MIN, min(VAL, MAX)) as per spec to support the function in the
attribute.

Bug: 825895
Change-Id: I087fef6654d2f964fc99071edbbd87a5bc5b8967
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1822217Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699770}

A JNI conversion CL (http://crrev.com/c/1809399) introduced the
verification error which regressed Webview startup.

Why did the JNI conversion introduce the error?
More inlining in Clipboard.java caused methods only available on later
versions of Android to be inlined into the startup code path.

How does this CL fix the issue?
By outlining and using annotations to prohibit inlining for the
offending methods.

Tbr: dtrainor@chromium.org
Bug: 1006812
Change-Id: I17ef9deb83ad751f028bfce4440500bb05a7f55e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823439
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: Sam Maier <smaier@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699769}

This patch pulls the probe notification code out of the destructor for
PlayStateUpdateScope. This is part of a refactoring project to align
the implementation of web-animations with the spec.  Over the course of
the next few patches, the update scope will be phased out and the probe
notification will be directly called whenever there is a potential state
change.

Bug: 960944
Change-Id: Icb7356ed3d2a8eb7dbe18a0e1c1a1ca88016e22a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1822321Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699768}

Updates paths and exclusions so we only test the right things, and Karma
TypeScript knows where to look for types.

Change-Id: I8f984839b3907b119a2edc3f4b452e5465d1c82a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824895
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Auto-Submit: Paul Lewis <aerotwist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699767}

Initial conversion performed using '2to3 -f print .'.
Imports added and duplicate parentheses removed manually.
Manually converted files, comments and inline code that 2to3 missed.
Afterwards ran "git cl format --python" and cherry-picked the formatting changes.

There are no intended behavioural changes.

Bug: 941669
Change-Id: I3944165366e10cfdc3017b540f8563ee26751682
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1818479Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Auto-Submit: Raul Tambre <raul@tambre.ee>
Cr-Commit-Position: refs/heads/master@{#699766}

These tests expect the window.unload event to fire, but this does not
happen by design if BackForwardCache is enabled.

TBR=clamy@chromium.org

Change-Id: Ica712043d4e593f33b407cc985f7c77c1f55a69e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823845
Commit-Queue: Lowell Manners <lowell@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699765}

The Nigori key name can be inferred from key material so there is no
need to consume the proto field with the name.

Bug: 967417
Change-Id: Ibbd98b6496a9d797f90afbc951e5689e1d7ce491
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824887Reviewed-by: Maksim Moskvitin <mmoskvitin@google.com>
Auto-Submit: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699764}

This CL ensures that the autofill assistant listener is removed.

Bug: 1007556
Change-Id: Id703f5ca610ab8982670814ed246248b6d7760b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824079
Commit-Queue: Clemens Arbesser <arbesser@google.com>
Reviewed-by: Mathias Carlen <mcarlen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699763}

This reverts commit 75bbdfb2.

Reason for revert: https://crbug.com/1007970 - crashing without leave on MacOS.

Original change's description:
> Mojo: Dump core on a configurable queue length threshold.
> 
> Bug: 1003391
> Change-Id: Ibdc72029f647eff989bebb9b6542cffb8273064a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1815847
> Reviewed-by: Ken Rockot <rockot@google.com>
> Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#699387}

TBR=rockot@google.com,siggi@chromium.org

Change-Id: Ie1434d93cce863d898959eaeca3ad24b4205c76d
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1003391
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825137Reviewed-by: Sigurður Ásgeirsson <siggi@chromium.org>
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699762}

https://dawn.googlesource.com/dawn.git/+log/05be0ff34815..cf0e9d93f177

git log 05be0ff34815..cf0e9d93f177 --date=short --no-merges --format='%ad %ae %s'
2019-09-25 natlee@microsoft.com Add StoreOp::Clear

Created with:
  gclient setdep -r src/third_party/dawn@cf0e9d93f177

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/dawn-chromium-autoroll
Please CC cwallez@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
TBR=cwallez@google.com

Bug: None
Change-Id: I685c56113149063204f2040438993612087163b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825077Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#699761}

Also, set the blocked-uri to "trusted-types-policy" in the violation report.

Bug: 992377
Change-Id: I164719050a39a654d002e0accc6858c55efef684
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816467
Commit-Queue: Stefano Sanfilippo <ssanfilippo@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699760}

https://chromium.googlesource.com/catapult.git/+log/6730faf618f8..e00ffeb79abc

git log 6730faf618f8..e00ffeb79abc --date=short --no-merges --format='%ad %ae %s'
2019-09-25 dberris@chromium.org Pinpoint: Remove migration-specific code for benchmark arguments

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC zhanliang@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

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=zhanliang@google.com

Bug: chromium:1006658
Change-Id: Id708b0a14c76dae43732250f7baf47426abf3b65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824034Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#699759}

Mismatch in API caused chromecast extension to fail.

Bug: 989413
Test: Manual display assistant
Change-Id: Ib0855853ac0b49b1f24a4a80b75c45834f0a87db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1814571Reviewed-by: David Tseng <dtseng@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Randy Rossi <rmrossi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699758}