GitLab

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/f1e5cd73f658..e0d5544c9864

git log f1e5cd73f658..e0d5544c9864 --date=short --no-merges --format='%ad %ae %s'
2019-11-05 jmadill@chromium.org Add missing headers to GN. (#3009)
2019-11-05 chris@chris-lamb.co.uk Correct "environment" typo (#3007)

Created with:
  gclient setdep -r src/third_party/SPIRV-Tools/src@e0d5544c9864

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/spirv-tools-chromium-autoroll
Please CC radial-bots+chrome-roll@google.com,jonahr@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_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64
TBR=radial-bots+chrome-roll@google.com,jonahr@google.com

Bug: None
Change-Id: I0bb09de61d7304556fad1607a28ee36532e2ee06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899354Reviewed-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@{#712507}

Windows inconsistently #define's _alloca as alloca in malloc.h, the
conditions required are not present on Windows on Arm. To fix, we check
and (possibly redefine) alloca on all Windows targets.

Bug: 1020541, 893460
Change-Id: Ife80ce3e7478d39d36e67686d70a74ff2319c714
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1892976Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Richard Townsend <richard.townsend@arm.com>
Cr-Commit-Position: refs/heads/master@{#712506}

https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/7f77b2e8669a..5d0e01d9e7f9

git log 7f77b2e8669a..5d0e01d9e7f9 --date=short --no-merges --format='%ad %ae %s'
2019-11-05 johnkslang@users.noreply.github.com Merge pull request #1961 from zoddicus/fixChromiumRoll
2019-11-04 johnkslang@users.noreply.github.com Merge pull request #1953 from null77/gn-add-missing-headers
2019-11-04 johnkslang@users.noreply.github.com Merge pull request #1954 from corporateshark/master
2019-11-03 cepheus@frii.com Tests: Add more test results for the previous generator version bump.
2019-11-03 cepheus@frii.com Bump up the generator version, which is exposed in SPV test results.
2019-11-01 cepheus@frii.com Merge branch 'dneto0-dead-code'

Created with:
  gclient setdep -r src/third_party/glslang/src@5d0e01d9e7f9

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/glslang-chromium-autoroll
Please CC radial-bots+chrome-roll@google.com,jonahr@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=radial-bots+chrome-roll@google.com,jonahr@google.com

Bug: None
Change-Id: I0c02ba75ec1709fd70dfd6719100fe81b7bb01ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899360Reviewed-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@{#712505}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/835991798ff9..b3914918d320


Created with:
  gclient setdep -r src-internal@b3914918d320

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@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.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

Bug: chromium:None,chromium:None
Change-Id: I48786d70431d254682c363016f237e8f63cb9264
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899356Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#712504}

> Introduction

When PlzDedicatedWorker (off-the-main-thread dedicated worker script loading) is
enabled, top-level dedicated worker script is fetched on a worker thread, not on
the main (or parent) thread. This causes a problem when a dedicated worker is
created from blob URL registered in a sandboxed iframe.

> Problem

A sandboxed iframe has an opaque origin. Blob URL registered in the frame also
has the same opaque origin.

When sending a network request to the blob URL, requester's SecurityOrigin takes
the origin from the blob URL, and then conducts security check (see
SecurityOrigin::CanRequest()). However, it's not straightforward on the opaque
origin because the opaque origin is serialized into the blob URL (KURL) as
"null" string like "blob:null/{UUID}", and there is no direct way to rebuild the
origin from the KURL. To deal with the case, in the current implementation, the
pair of the blob URL and the opaque origin is stored in thread-specific
BlobURLNullOriginMap, and then the security check refers to the map.

This mechanism works well when PlzDedicatedWorker is disabled, but not work when
PlzDedicatedWorker is enabled. This is because the pair of the blob URL and the
opaque origin is stored in the thread-specific map on the main (parent) thread,
but the network request and the security check are conducted on the worker
thread. As a result, the security check always fails.

> Solution

Making BlobURLNullOriginMap thread-safe could be one of solutions, but actually
it's quite hard and not practical. This is because SecurityOrigin is not
thread-safe, and widely used with an assumption that it's not shared among
threads.

Alternatively, this CL makes SecurityOrigin::CanRequest() check the opaque
origin of the blob URL using SecurityOrigin::Nonce. Nonce is uniquely assigned
to SecurityOrigin when it's constructed as an opaque origin, and SecurityOrigin
instances (isolated-)copied from the same opaque origin share the same nonce.
The nonce is base::UnguessableToken, and shareable among thread unlike
SecurityOrigin.

This CL introduces BlobURLNullOriginNonceMap that is the process-global
singleton object to contain pairs of blob URL and opaque origins's nonce. The
map is protected by Mutex, so any threads can access it.
SecurityOrigin::CanRequest() compares the nonce stored in the map to its own
nonce in addition to the existing checks. This fixes the problem.

> Test

This enables to pass some tests that were skipped because of timeout. Several
test cases are still failing even after this change, but it should be caused by
https://crbug.com/1017034.

Bug: 987130
Change-Id: I6bf2212aa4f4b1a37035c41866b3faeffe68c2b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873831
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712503}

New test mimics server-side behavior for triggering keystore key
rotation: generation of new keystore key with touching the Nigori
node. After that client should receive updated keystore keys and the
same Nigori node as it already has (modulo metadata update). The client
should commit the new Nigori node with rotated keystore key and this
verified by checking |encryption_keybag| encryption key name.

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

Bug: None
Change-Id: I12693287a5f005bd3b6d8e2dcb4f40e6baaad938
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898133
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Malay Keshav <malaykeshav@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712501}

Currently, frame is detected as iframe in `destination` which will be fixed in https://bugs.chromium.org/p/chromium/issues/detail?id=1019716.

Bug: 1011724
Change-Id: I722bcbccac3bfc914844711fb6feb1e21f859a6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1886863Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Yifan Luo <lyf@google.com>
Cr-Commit-Position: refs/heads/master@{#712500}

It's not yet been fully understood, but it seems like doubly-proxying
(ReferenceType = Proxy -> RefById -> DefinitionType/TypedefType) is
causing trouble.

This patch fixes the trouble, and makes a ReferenceType an instance
of IdlType (actually of ReferenceType).

Bug: 839389
Change-Id: Iccaa3ef78a1a77318e796248a1bf92a2eac40c80
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1892986Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712499}

Add use counters for the constructors of CountQueuingStrategy and
ByteLengthQueuingStrategy. This will help us evaluate their usage, with a view
to possibly deprecating them. See
https://github.com/whatwg/streams/issues/1005#issuecomment-549184328.

Change-Id: I633ab863fd93da8e74ecdd7001815d6a1728c82b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899236Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712498}

"

This reverts commit 9932d106.

Reason for revert: Broke a test with insufficient testing (see crbug.com/1021332) - will require additional investigation.

Original change's description:
> Layout invalidates when child view's visibility changes.
> 
> 
> 
> Exactly what it says on the tin.
> 
> 
> 
> This is a fix for legacy layouts (fill, box, grid) which aren't derived
> 
> from LayoutManagerBase and which do not benefit from the logic in that
> 
> class which handles the invalidation. LayoutManagerBase still overrides
> 
> this logic with something more sophisticated.
> 
> 
> 
> If in the future a legacy layout overrides ViewVisibilitySet(), it
> 
> should either call the base implementation or handle the invalidation on
> 
> its own.
> 
> 
> 
> 
> Bug: 1003500
> 
> Change-Id: I9eccef21784175820816852e1b9c05d0713ef2eb
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1894260
> Commit-Queue: Dana Fried <dfried@chromium.org>
> Reviewed-by: Siyu An <siyua@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#711966}

TBR=siyua@chromium.org,dfried@chromium.org

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

Bug: 1003500
Change-Id: I9f82556592e9e8db02900620085250e696ab30c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899387Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Dana Fried <dfried@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712497}

Request and Response's formData() multipart/form-data parsing uses
"UTF-8 decode without BOM" which should not strip BOMs.

Spec issue: https://github.com/whatwg/fetch/issues/650
Spec fix: https://github.com/whatwg/fetch/pull/915
WPT fix: https://github.com/web-platform-tests/wpt/pull/17589

Bug: 796192
Change-Id: I24721899006a8c09cf657b3638f1cb17e7953171
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796367
Commit-Queue: Eero Häkkinen <eero.hakkinen@intel.com>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712496}

Originally landed: crrev.com/c/1749145
Reverted: crrev.com/c/1751830

The revert was due to Trusty not supporting ATK_ROLE_STATIC. The change
is something which can wait but should be made eventually.

Original commit message:

  Text leaf nodes and line breaks were being exposed as ATK_ROLE_TEXT.
  However, the definition of ATK_ROLE_TEXT is:

    An interactive widget that supports multiple lines of text
    and optionally accepts user input, but whose purpose is not
    to solicit user input.

  In contrast, ATK_ROLE_STATIC is defined as:

    A generic non-container object whose purpose is to display
    a brief amount of information to the user and whose role is
    known by the implementor but lacks semantic value for the user.

  Thus text leaf nodes and line breaks should be exposed with the latter
  role; not the former.

Bug: 984590
Change-Id: I7da4ea79dcac546a96e55d5ef57c9a052e9bd578
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872409
Auto-Submit: Joanmarie Diggs <jdiggs@igalia.com>
Commit-Queue: Martin Robinson <mrobinson@igalia.com>
Reviewed-by: Martin Robinson <mrobinson@igalia.com>
Cr-Commit-Position: refs/heads/master@{#712495}

This reverts commit 677b08ef.

Reason for revert: This seems to be messing with the code coverage builders.

Original change's description:
> Check for counter overflows when merging profraw files.
> 
> R=​sajjadm,liaoyuke
> 
> Bug: 1020404
> Change-Id: I28e27f40aebbc9743da1fa7cc42deb03f77cee13
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1894619
> Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
> Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#712266}

TBR=robertocn@chromium.org,liaoyuke@chromium.org,sajjadm@chromium.org

Change-Id: Ib7e3c45ac146977c13e133be2200433778558741
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1020404
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899546Reviewed-by: Roberto Carrillo <robertocn@chromium.org>
Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712494}

This is a reland of 83ced150

Original change's description:
> [base] Introduce base::CheckedContiguousRange
> 
> This change introduces base::CheckedContiguousRange, which similarly to
> base::span is a light-weight wrapper around a contiguous container
> performing bound CHECKs.
> 
> However, in contrast to base::span this class keeps a pointer to the
> underlying container, and thus is able to respond to changes to data()
> and size(), which base::span can't do.
> 
> Furthermore, this change provides a constexpr overload of base::data()
> for std::array and fixes a bug in CheckedContiguousIterator::operator-=.
> 
> Bug: 990059
> 
> Change-Id: I3fef91c7ef7874bf495ac2ab6dbaf3a8b02dab35
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1893858
> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
> Reviewed-by: Chris Palmer <palmer@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#712120}

Bug: 990059
Change-Id: If7cfd16ca526930643e9fac7567f58ba9ef60b1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1893069Reviewed-by: Chris Palmer <palmer@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712493}

https://chromium.googlesource.com/devtools/devtools-frontend/+log/167e7ad444..2cf0518ef4

TBR=bmeurer@chromium.org

Change-Id: Id494978d845223c4ff796e15f8819f53bea25d5d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898650Reviewed-by: Yang Guo <yangguo@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712492}

https://chromium.googlesource.com/angle/angle.git/+log/67527cb45293..df415528411f

git log 67527cb45293..df415528411f --date=short --no-merges --format='%ad %ae %s'
2019-11-05 sunny.sun@arm.com Vulkan: Enable VK_IMAGE_USAGE_STORAGE_BIT when it is needed

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC jonahr@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=jonahr@google.com

Bug: None
Change-Id: I2456863799c8973de10966ceaeb10fdb85feaad7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899210Reviewed-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@{#712491}

There are multiple datatypes that are platform-dependent and
nevertheless the types and enum values are compiled (no ifdef).

This patch does the same for READING_LIST which is no different.

Bug: 950874
Change-Id: I5598d1e7b221c1f4a1338bb83397066c2b79be60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1893198
Auto-Submit: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712490}

README.js is clearly not holding JS contents, and is causing ESLint
errors.

This is in preparation of turning on ESLint PRESUBMIT checks for
src/components.

Bug: 1019312
Change-Id: Id32353b0f1e4bcd1cc62bd3983739c16fe0d24bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898868
Commit-Queue: Marc Treib <treib@chromium.org>
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712489}

This CL removes the check to make sure rfh exists when
ServiceWorkerProviderHost::OnBeginNavigationCommit is called. For
tests this function is called with a fake frame, and this was
causing ServiceWorker tests to fail.

Bug: 1020884
Change-Id: I5d750e50ca19409cf94867b5e07a7ce35eaa33d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898165
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712488}

This CL moves logic from NetworkServiceNetworkDelegate that performs a
DumpWithoutCrash() on incorrect referrer detection, to where
serialization of a network::ResourceRequest is performed before being
passed to the network service. This is a temporary migration to aid in
debugging long-standing referrer mismatches (crbug.com/912680) as well
as recently-introduced referrer mismatches (crbug.com/1020592).

Bug: 912680,1020592
Change-Id: Id6d7db1c7105bd86f125004868a49beea8c2c3a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1896251Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712487}

Using wpt-import in Chromium 9eccfe81.
With Chromium commits locally applied on WPT:
1d5b803f "Add WebVTT support for inline styling - Web Platform Tests"


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

Directory owners for changes in this CL:
mkwst@chromium.org, andypaicu@chromium.org:
  external/wpt/content-security-policy

NOAUTOREVERT=true
TBR=robertma

No-Export: true
Change-Id: Idd3c89fe559b3991fb1288ed5475a0757a5276ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898180Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#712486}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/3f35966470fb..835991798ff9


Created with:
  gclient setdep -r src-internal@835991798ff9

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@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.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

Bug: chromium:None
Change-Id: I0963bf0ec1df35b86efb094bf3c8ec00dc5a5e3c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899066Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#712485}

Bug: none
Test: none
Change-Id: I1aa70508f9e6a131dc39cf67827bf691558a6882
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899235Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Commit-Queue: Chih-Yu Huang <akahuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712484}

Added a new rule to allow the user 'crosvm' to use libvda D-Bus service
because crosvm is run as 'crosvm' when it's started by vm_concierge.

Bug: b:142864350
Test: Play a video on VM with virtio-vdec
Signed-off-by: Keiichi Watanabe <keiichiw@chromium.org>
Change-Id: I35562356b9a475fc3f72ec7de743cfe636b4a6e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1883451Reviewed-by: Mattias Nissler <mnissler@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712483}

Please see the comments in the file before removing.

NOTRY=true

Bug: 1019501, 1001450
Change-Id: I99beba1bc7d3bacd25208ce1e8d5ab8356808e43
TBR: wangxianzhu@chromium.org, yhirano@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899237Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712482}

Bug: 1021236
Change-Id: I96599537914475508a3404b4771aeab9fa117a05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1896341
Auto-Submit: Eric Roman <eroman@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712481}

To avoid inefficient AtomicString concatting when the header value has
multiple commas.

Bug: 930150
Change-Id: I33439d188be20d130278a961ec6ad82d2ba7fa7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1893608Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712480}

We now use an overlay with opacity to show the hover card transition
between adjacent tabs as the hover card slide-animates between them.

This is done with a second title and domain label that starts out
displaying the old title and domain (obscuring the title and domain
labels displaying the new values) and fades away as the hover card
animates.

We also looked at using layer opacity but the results were less
attractive.

Change-Id: I5098838596ea1e674cdeb884520ac7ea3a328623
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1895945
Commit-Queue: Dana Fried <dfried@chromium.org>
Reviewed-by: Caroline Rising <corising@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712479}

In the strongification case the callbacks should return false
indicating that the key is alive and value should be traced.

Bug: 1019191
Change-Id: I508dcb6fa90d91417788302aef1f448a8fc9a744
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1897928Reviewed-by: Omer Katz <omerkatz@chromium.org>
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712478}

Following bot results are included.
178 179 180

A large number of new failures are probably due to r712444
crrev.com/c/1869076 .

TBR=yosin@chromium.org
NOTRY=true

Bug: 982194
Change-Id: If425fdfa62d25435f08f891742626d79ecb61c0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898146Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712477}

This CL cleans up old mojo types for mojom::DisplayPrivate using
AssociatedRemote, PendingAssociatedReceiver, and AssociatedReceiver.

Bug: 955171
Change-Id: Ia8191e6f88b11db9d61481caafcca18e61037976
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1894664
Commit-Queue: Julie Kim <jkim@igalia.com>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#712476}

Bug: 839389
Change-Id: Iedb529071d050b6eaddf76d0b4d7841c788b2f35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898900Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712475}

Bug: 839389
Change-Id: I7f1cea25c7c66cb13a0ef9e4b56bb2a81f6d7869
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898899Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712474}

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

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: I306595250f8868ae0f9c63b17aa406b1793f4cff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898179Reviewed-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@{#712473}

Instead use base::DeleteSoon which enforces usage of TaskTraits.

This CL is a no-op as-is. It was recently discovered however that some
callers did BrowserThread::DeleteSoon() with pending tasks running on
different task queues (different traits  -- e.g.

TaskTraits to make this more obvious. Please review whether calls in
this CL can be migrated as-is or need additional traits to match
potentially pending tasks.

Split from https://chromium-review.googlesource.com/c/chromium/src/+/1894109
for cursory review.

This CL was uploaded by git cl split.

R=fukino@chromium.org


TaskPriority: :BEST_EFFORT) which can result in out-of-order deletion...
BrowserThread: :DeleteSoon() is being migrated to base::DeleteSoon() w/
Bug: 1019767
Change-Id: I58d10f42096525ceb432d30ab59e74cdfa11d290
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1894889
Auto-Submit: Gabriel Charette <gab@chromium.org>
Reviewed-by: Naoki Fukino <fukino@chromium.org>
Commit-Queue: Naoki Fukino <fukino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712472}

This CL adds a permission for Web NFC. The permission will be denied
when the feature is disabled, which is true by default while we're
implementing it.

Spec: https://w3c.github.io/permissions/#nfc

Bug: 520391
Change-Id: Ic8785dc9bf3e2adf0813652b056e29cc7f41c1b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1888655
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#712471}

The refactoring https://crrev.com/c/1861442 caused a regression in
memory when loading a (blank) page. A side effect of the refactoring
was introduced at didFinishNavigation event. Previously
|showRenderedPage| earlied out if |mNativePage| is null, but after the
change it triggered |notifyContentChanged|. This CL fixes it.

Bug: 1019369
Change-Id: Ia4c663781f8d3c51a2f3157227b81b8ce213cfc9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898156Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712470}

These tests were parameterized and the .* does not cross the /
boundary, so the filters didn't filter the tests.

TBR=yuzus@chromium.org

Bug: 1020884
Change-Id: I653b1ef797e0d77ae722080e2e0a33d6fbcfea3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898904Reviewed-by: Fergal Daly <fergal@chromium.org>
Commit-Queue: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712469}

WebKit Mac10.13 (retina)
  virtual/audio-service/media/video-controls-rendering.html

Mac10.11
  media/controls/video-overlay-cast-dark-rendering.html
  virtual/audio-service/media/controls/video-overlay-cast-dark-rendering.html

Bug: 1021407
Change-Id: I73769f1ca62f570ecc7ef8fd629ab1ef5977950d
Tbr: andypaicu@google.com
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898903Reviewed-by: Takashi Sakamoto <tasak@google.com>
Commit-Queue: Takashi Sakamoto <tasak@google.com>
Cr-Commit-Position: refs/heads/master@{#712468}