GitLab

This CL converts IsolatedXRGamepadProviderFactoryPtr and
Binding<IsolatedXRGamepadProviderFactory> in chrome and
device to the new Mojo type, and uses
pending_remote<IsolatedXRGamepadProviderFactory> in
isolated_xr_service.mojom.

Bug: 955171
Change-Id: I109a2197c8e02bdd7908402837284f9f2c45970c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847233
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#704582}

This is phase 6.2 on the design document [1].

CL moves RTCCertificateGenerator directly to blink/renderer, once its
solely clients all reside in blink/renderer now.
The existing base class WebRTCCertificateGenerator, needed to bridge
between blink and content will be removed in a follow up step.

The CL also removes the existing accessor in blink::Platform, and
removes Mock implementations in
//content/test/test_blink_web_unit_test_support.cc|h

BUG=787254
R=guidou@chromium.org, haraken@chromium.org

Change-Id: I7d065a3d9344d779c65938c174c74d82e71a8716
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1814604
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Tommi <tommi@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704581}

TBR=pfeldman

Bug: 1013003
Change-Id: I6b98b0c4698c6c40d323bc996603e6595d3e4340
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852291Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704580}

Failing builds for example:
https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/83781
https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/83780
https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/83779

TBR=rmcilroy@chromium.org,perezju@chromium.org

Bug: 1008001
Notry: true
Change-Id: I1698c7b3d086d4238cca849c31ccb3ab806e581b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852206
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704579}

TBR=austinct

Bug: 1008880
Change-Id: I9f9987e194fe59cbd8dd239105de76ce680a477f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852091Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704578}

virtual/omt-service-worker-startup/external/wpt/service-workers/service-worker/update-bytecheck.https.html expectations
fails on Win10, too, generalizing TestExpectations line.

Bug: 1002377
Tbr: alancutter
Notry: true
Change-Id: I58fd8486fade53a11217c16010376e352aa40429
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852266
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704577}

These histograms are logged from third-party library QUICHE at the
following places:

https://quiche.googlesource.com/quiche/+/refs/heads/master/quic/core/qpack/qpack_encoder.cc#294
https://quiche.googlesource.com/quiche/+/refs/heads/master/quic/core/http/quic_spdy_session.cc#1081

For the definition of QUIC_HISTOGRAM_COUNTS, see
https://quiche.googlesource.com/quiche/+/refs/heads/master/quic/platform/api/quic_exported_stats.h#86
https://cs.chromium.org/chromium/src/net/quic/platform/impl/quic_client_stats_impl.h
https://cs.chromium.org/chromium/src/net/quic/platform/impl/quic_server_stats_impl.h

Change-Id: Icf5a632d9f172cb2c79b53cccec349a2060351b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847797
Commit-Queue: Bence Béky <bnc@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704576}

The screen size flakiness should have been resolved by
crrev.com/704235.

Bug: 977153
Tbr: wangxianzhu@chromium.org
Change-Id: I81a3c2acde46c4a0dfd8a58f78a85b95beab5c03
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852329Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704575}

Bug: 1006759
Change-Id: I55ff55840cbf00a108cb0f3630cf5b489bf3aac2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849386Reviewed-by: Yang Guo <yangguo@chromium.org>
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704574}

Bug: 981349
Change-Id: I3a9231abd80cfb9098ac3b8e7d261e70547a0c88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852245Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Commit-Queue: Mikhail Khokhlov <khokhlov@google.com>
Cr-Commit-Position: refs/heads/master@{#704573}

This CL converts URLLoaderFactoryRequest from Clone()
in url_loader_factory.mojom using PendingReceiver and
ReceiverSet.

Bug: 955171
Change-Id: Ic85b66e016b4556ff234db1f4545586c294dc6e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844010Reviewed-by: Nathan Parker <nparker@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Commit-Queue: Julie Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/master@{#704572}

New integration test injects backward-compatible keystore Nigori and
tests that client can decrypt password encrypted with the default key.

Backward-compatible keystore Nigori uses some old key (derived from
GAIA passphrase) as the default encryption key. This key is used for
encryption of passwords data and |encryption_keybag| in
NigoriSpecifics. This key also stored in |keystore_decryptor_token|,
which is encrypted with a keystore key, so client should be able to
decrypt everything once it has the keystore keys.

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

Change-Id: Ibe628e70b3d53db9ca132378c2da2ac42cd7746c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847337
Commit-Queue: Paul Lewis <aerotwist@chromium.org>
Reviewed-by: Mathias Bynens <mathias@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704570}

Goma no longer supports cl.exe and the cl.exe version update in this CL hasn't
been uploaded to goma's servers. Everyone who has bots that use cl.exe must make
sure that these bots don't use goma before rolling this CL in.

This change switches the MSVC toolchain to VS 2019 16.3.29324.

Windows SDK is mostly 10.0.18362
Debuggers from 10.0.17763
d3dcompiler_47.dll from 10.0.17134

The instructions for the previous package are included below:

Packaging was done on a Windows Server 2019 VM, cleanly created for this
purpose.

The package was created by downloading VS 2019 Update 3.29324, from
https://visualstudio.microsoft.com/downloads/ and downloading
the 16.3 Visual Studio Professional 2019, and then running the installer
like this:

$ PATH_TO_INSTALLER.EXE ^
    --add Microsoft.VisualStudio.Workload.NativeDesktop ^
    --add Microsoft.VisualStudio.Component.VC.ATLMFC ^
    --add Microsoft.VisualStudio.Component.VC.Tools.ARM64 ^
    --add Microsoft.VisualStudio.Component.VC.MFC.ARM64 ^
    --includeRecommended --passive

Then the 10.0.18362.0 SDK was installed from:
https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk.

Then Add or Remove Programs was used to modify the 10.0.18362.0 SDK to add
the Debuggers package.

Then the packaging script was run like this:

  python depot_tools\win_toolchain\package_from_installed.py 2019 -w 10.0.18362.0

Since the new d3dcompiler_47.dll uses the UCRT and we want to avoid shipping
that the final packaging step was to unzip the package, copy over the two copies
of that DLL from win_sdk\Redist, replace the Debuggers directory with the
10.0.17763 SDK, and then repackage the toolchain with:
  > python package_from_installed.py --repackage=<full-path-to-toolchain-dir>

Bug: 1006238
Change-Id: I623632bd72f018a74ab513d2c79e89199915e647
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1836195Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704569}

This implements phase 6.1 on the design document [1].

[1] https://docs.google.com/document/d/1AJKVA5U4nDkyDB9p4ROrggWXadCxyy-grKaE9KS5vOU/

Basically, the CL moves
content/renderer/media/webrtc/media_stream_video_webrtc_sink.cc|h
to Blink.

Notes:

- the header is temporarily moved to Blink's public API layer until
  all its clients move to Blink.

- the associated unit test will be moved in a later step because of its
  inclusion chain that needs to be handled first (namely
  content/renderer/media/webrtc/mock_peer_connection_dependency_factory.h).

BUG=787254
R=guidou@chromium.org, haraken@chromium.org

Change-Id: I8ede23160a249349e32bbf82a62e8aed1504bbf3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1811179
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704568}

Cause:
  Android webview is reaching a CHECK in the renderer process.
  See: https://crbug.com/1006814.

Plan:
 1) Revert speculatively.
 2) Cherry-pick to M78
 3) Reland later with:
    a) Some CHECK on the browser side to get useful StackTrace.
    b) Some Android webview specific tests.

Reverted CL:
-----------------------------------------------------------------------
Stop reviving crashed RenderFrameHost. Get a new one instead.

On same-site navigations, the browser reuses the current
RenderFrameHost, even if the current RenderFrameHost is crashed.

Instead of reviving the crashed one, we should get a new RenderFrameHost.

This can be seen as a small step in the direction of RenderDocument, which
intend to get a new RenderFrameHost every time, even if the previous
RenderFrameHost is not crashed.
https://docs.google.com/document/d/1C2VKkFRSc0kdmqjKan1G4NlNlxWZqE4Wam41FNMgnmA/edit

Bug: 981339
Change-Id: I17b11abe759906a7f360abeaa45f0bfc77e08768
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1688957
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
-----------------------------------------------------------------------

Bug: 1006814
Change-Id: Ic0b55d61739b5f64c46bf9326eb2fcd4fe03de0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1848390Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704567}

- The check caused Android to return true for IsSyncDisabled when
  "sync the feature" is turned off but transport-mode is active
- The check was a workaround for ClickToCallBrowserTest and is now
  replaced with proper test setup

Bug: 1010968
Change-Id: I6031401d5a781a1f2436a5bfb738059d1ff51961
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845717Reviewed-by: Richard Knoll <knollr@chromium.org>
Commit-Queue: Alex Chau <alexchau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704566}

Change-Id: Id69c525307e93d1b45d0412de643f77efc53188e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844821Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704565}

BackgroundSyncScheduler code was returning an incorrect
delayed_processing_info for Periodic Background Sync.

This change fixes that.

Change-Id: Ic5aa4505de2613bea5cd676de8faeca76100eb8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851424
Auto-Submit: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704564}

This patch extends the syntax of the list-style-type property to accept
arbitrary string values in order to customize the marker contents.

I have followed the same approach as https://crrev.com/c/879135 did for
the display property. When a string is specified for list-style-type,
the patch sets it to a special EListStyleType::kString, and the string
is stored in an extra field. As a result of this split, list-style-type
doesn't use as much auto generated code now, e.g. EListStyleType is not
automatically generated.

Intent to Implement and Ship: list-style-type: <string>
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/GojYpoeDbqc

Spec: https://drafts.csswg.org/css-lists/#valdef-list-style-type-string

Bug: 687946

TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-002.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-003.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-004.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-005a.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-005b.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/list-style-type-string-006.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/parsing/list-style-type-computed.html
TEST=third_party/blink/web_tests/external/wpt/css/css-lists/parsing/list-style-type-valid.html
TEST=third_party/blink/web_tests/external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/lists-3/list-style-type-string-001a.html
TEST=third_party/blink/web_tests/external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/lists-3/list-style-type-string-001b.html

This patch makes some ::marker tests in css-pseudo fail, but this is
expected because ::marker has not been implemented yet.

Change-Id: I5743b99bc1a8e66679235874623c82650860ea29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841472
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704563}

This CL converts XRSessionController{Ptr, Request} in chrome and
device to the new Mojo type, and use
pending_remote<XRSessionController> in isolated_xr_service.mojom.

This CL also remove unnecessary InterfaceSet and it is replaced
with RemoteSet.

Bug: 955171, 965668
Change-Id: I388f1be9010b6c91a0f1fa00bfc719accd457f66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846418
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#704562}

TBR=kinuko, lanwei

Bug: 1011225
Change-Id: I39eb153ac8a3b25b5f0c73af370f498abf3aac8d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852088Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704561}

Bug: 1012098
Change-Id: I266825bc3482fbc82c00fa9ef96d7b269c03a4fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852345Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704560}

It's needed in builds that don't set use_v8_context_snapshot,
such as when cross-compiling from Linux to Windows. The gn file
already lists snapshot_blob.bin as a dependency in that case,
but it never actually made it into the installer.

Since the file is usually always built, this puts it in a section
of chrome.release that's only included conditionally.

Bug: 803591,858874
Change-Id: I26de080231ced9812110d9524dcec990bf3bbee4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844991Reviewed-by: Greg Thompson <grt@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704559}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/d0b81401..35d020e5

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

This reverts commit 7b3a80a2.

Reason for revert: Suspected to break chromeos-kevin-rel bot and webrtc.DecodeAccelUsedVP8, see https://crbug.com/1013105

Original change's description:
> media/gpu: Use PortConfig to store ImageProcessor's i/o config.
> 
> ImageProcessor stores input and output's configuration with
> VideoFrameLayout object and VideoFrame::StorageType. However,
> VideoFrameLayout is unable to represent proprietary format, e.g. MT21,
> so it is not suitable to represent IP's input/output config.
> 
> Instead of storing individual configuration properties (format,
> visible_size, color_plane_layout, storage_type), we modify an existing class,
> ImageProcessor::PortConfig, to store ImageProcessor's input/output
> configuration.
> 
> BUG=1004727, 1005636
> TEST=Run VDA test on elm and kukui
> Pass image_processor_test
> 
> Change-Id: I720b8ba41db8c5d4e0d1c42ea41f3d4ba27d3ee7
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1817858
> Reviewed-by: Dan Sanders <sandersd@chromium.org>
> Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
> Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
> Commit-Queue: Chih-Yu Huang <akahuang@chromium.org>
> Auto-Submit: Shuo-Peng Liao <deanliao@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#704499}

TBR=dcheng@chromium.org,deanliao@chromium.org,mcasas@chromium.org,sandersd@chromium.org,akahuang@chromium.org,hiroh@chromium.org,acourbot@chromium.org

Change-Id: I6802f787c6f4567c4a0492681da1b1ded27182fb
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1004727, 1005636, 1013105
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852089Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704557}

The new behavior is behind the 'CustomStatePseudoClass' runtime flag.

Explainer: https://github.com/w3c/webcomponents/blob/gh-pages/proposals/custom-states-and-state-pseudo-class.md

Bug: 1012098
Change-Id: Ia0d1e145cf6589868c7c39d3b1c51fdf2b41bc68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800138
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704556}

This is mostly for consistency with GetBestMatches.

Bug: 1011399
Change-Id: I7369ee04a735c830b30d20bd1b826a66b77d759a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845714
Commit-Queue: Marc Treib <treib@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704555}

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/c18c9ff6bc30..82f84c4b8f19

git log c18c9ff6bc30..82f84c4b8f19 --date=short --no-merges --format='%ad %ae %s'
2019-10-09 ehsannas@gmail.com Use a longer timeout for Bazel tests. (#2956)
2019-10-09 rharrison@google.com Remove non-existent files from BUILD.gn (#2955)
2019-10-09 alanbaker@google.com Disable scope validation for OpReadClockKHR (#2953)
2019-10-09 cwallez@chromium.org CMake: Add support for building with emscripten (#2948)
2019-10-09 stevenperron@google.com Update CHANGES
2019-10-08 stevenperron@google.com Link cfg and dominator analysis in the context (#2946)
2019-10-08 afdx@google.com spirv-fuzz: add transformation and pass to construct composites (#2941)
2019-10-08 paulthomson@users.noreply.github.com reduce: improve remove unref instr pass (#2945)
2019-10-08 afdx@google.com spirv-fuzz: add disabled test to document known issue (#2942)
2019-10-08 afdx@google.com spirv-fuzz: Add fuzzer pass to change selection controls (#2944)
2019-10-07 jeremy-lunarg@users.noreply.github.com Enable OpTypeCooperativeMatrix specialization (#2927)

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

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,geofflang@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,geofflang@google.com

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

ApplyRemoteCreationWithoutValidGUIDOrOCII disabled on TSAN* and ASAN*.

ApplyRemoteCreationWithValidGUID had missed MAYBE prefix, after fix
disabled on TSAN*.

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

Bug: 994219
Change-Id: I1250e61b7482e957396bc02b6a748e126dcb0a1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844271
Commit-Queue: Ionel Popescu <iopopesc@microsoft.com>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704552}

The uses the <picture> element to select different sources for the logo
image based on the device's mode. It also moves the white logo files
to the same place as the existing files for consistency. There are
corresponding CLs to move the google_chrome logo files as well.

Bug: 1006216
Change-Id: I146382b7608b4769306886df81bd80cd051cef86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825418
Commit-Queue: Robbie Gibson <rkgibson@google.com>
Reviewed-by: Dan Beam <dbeam@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704551}

When the user is resizing the app using the splitter, and the tree has
has overflow-y content, a scroll bar appears. That is annoying. Fix by
hiding directory scroll bars while the splitter is active.

Bug: 1002790
Change-Id: Ie03c75f020a9f0cf573b7c46bf0d204190e68d66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851789Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704550}

The previous CL [1] was intended to add use counter only, but
actually accidentally stopped execution of scripts moved between
different element documents under a same context document.

This CL partially reverts [1], and
makes such scripts evaluated again as before.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/1843509

Bug: 721914
Change-Id: I13f5dbdff46c14a5da49e436994cf73a7dd88373
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851524
Commit-Queue: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704549}

https://chromium.googlesource.com/angle/angle.git/+log/c5e0ac757a11..ad5f71649e21

git log c5e0ac757a11..ad5f71649e21 --date=short --no-merges --format='%ad %ae %s'
2019-10-10 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/spirv-tools/src 3c7ff8d4f0a1..82f84c4b8f19 (10 commits)

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

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

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

This patch introduces |NGInlineCursor| member functions for painitng selection:
 - MoveToContainingLine()
 - MoveToFirstChild()
 - MoveToLastChild)(
 - MoveToLastLogicalLeaf()
 - Replacement for NGPaintFragment::InlineFragmentsFor()
   * MoveTo(const LayoutObject&)
   * MoveToNextForSameLayoutObject()
 - MoveToNextSibling()
 - TryToMoveToFirstChild()
 - TryToMoveToLastChild()
 - Property getters for detecting line break
   * Current{Base,Resolved}Direction()
   * CurrentSize()
   * CurrentStyle()
   * CurrentText{Start,End}Offset()
   * IsAtomicInline()
   * IsBeforeSoftLineBreak()
   * IsHiddenForPaint()
   * IsEllipsis()
   * IsLineBreak()

* Rename |NGInlineCursor::IsAtEnd()| to |IsNull()| because
  |MoveTo{First,Last}Child()| set cursor to null if current position has no
  children.
* Rename |NGFragmentItem::ChildrenCount()| to |DescendantsCount()| to avoid
  confusion with immidieate children count and descendants count.

This patch is a preparation of the patch[1].

[1] http://crrev.com/c/1832843 Paint selection with NGFragmentItem

Bug: 982194
Change-Id: Icc09d380371f08477fcc9a45ae0c03c50968a3f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851885
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Auto-Submit: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704547}

This adds new metrics for eviction by back-forward navigation:
BackForwardCache.EvictedReason.

BackForwardCache.EvictedReason records the reason why the page is
evicted, e.g., by JavaScript execution.

This CL is a split of the CL for all the metrices:
https://chromium-review.googlesource.com/c/chromium/src/+/1782233

Bug: 1004676
Change-Id: Ieea66f2ae6ed30fb836262632ab39b450698a6e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1820701
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704546}

ExternalInstallOptions and InstallManager::InstallParams now contain
DisplayMode instead of LaunchContainer.

This allows minimal-ui to be supported by InstallManager.

TBR=jonmann@chromium.org

Bug: 1009909
Change-Id: I13adaf8f834f2cb2d8e80d7ad3bffc24b9d9d73d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849471Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704545}

Implement compression for "gzip" and "deflate". The implementation is
hidden behind the ExperimentalCompressionStream flag.

For unit tests, we compress and stream and uncompress it with pako, and
we make sure its output is the same as our original data.

The original CL was reverted in
https://chromium-review.googlesource.com/c/chromium/src/+/1849376
due to failures on the MSAN and leak bots.

The compression-stream.any.js test has been modified from the original
version of this CL to improve performance, and also marked as slow.

TBR=kinuko

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

This change makes the Touch To Fill implementation robust against a
quick double tap before opening the sheet. It does this by introducing a
new flag in the renderer, that is only unset once a user has dismissed
the Touch To Fill sheet. Until then each focus event will result in a
call to PasswordAutofillDriver::ShowTouchToFill() if the other
conditions are met.

Prior to this change a user could trigger both the Touch To Fill sheet
and the soft keyboard by a quick double-tap on an input field before
the Touch To Fill sheet was expanded. Now this doesn't happen anymore,
as a keyboard will only be shown after the user has explicitly dismissed
the Touch To Fill sheet.

Bug: 1012236
Change-Id: Ie207789fe35aced4f94e3a5433adee016f0738eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1848696
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Friedrich [CET] <fhorschig@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704543}