GitLab

Introduce a build flag for the remote spelling service, and stop
compiling/instantiating SpellingServiceClient on platforms that
don't use it (Android). Also try to reduce the number of platform
ifdefs in spellcheck code, in favor of buildflag usage. Reduce
the amount of code that's compiled but never used by removing
several SpellCheckHostImpl methods on mac/win.

Also remove a couple of obsolete includes.

Change-Id: I5697a5d3f891f69159d5bba855ee72e11a3ca8be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1927412Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Auto-Submit: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718338}

This CL converts ShutdownTestService, ShutdownTestClient, and
ShutdownTestClientController to new Mojo types using PendingReceiver,
PendingRemote, Remote, and Receiver.

Bug: 955171
Change-Id: I3731946c426df305ac59657fa8c255485362a496
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930242Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Julie Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/master@{#718337}

This CL converts DeferredDestroyStrongBindingSet to new
Mojo types using UniqueReceiverSet.
It renames DeferredDestroyStrongBindingSet to
DeferredDestroyUniqueReceiverSet which holds UniqueReceiverSet
instead of StrongBindingSet.

Bug: 955171
Change-Id: Iaf5655eb7050d5c7db49745fec60a6e9a504a300
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930286Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Commit-Queue: Julie Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/master@{#718336}

TBR=meacer@chromium.org

Change-Id: I9adbb27ee0b80a0c589928d145b2c83b27349e38
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1931386Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718335}

This is a reland of 45cef59a

Original change's description:
> Move Renderer processes off Service Manager
>
> Migrates Renderer processes to use the simpler ChildProcess IPC
> interface in place of deprecated Service Manager IPC.
>
> Support for preloaded files in service manifest definitions is
> effectively removed in favor of explicit parameters on
> BrowserChildProcessHost and ChildProcessLauncher. The only use case (V8
> snapshot files) has been migrated from manifest data to a simple map
> definition, and it's used during renderer and utility process launching.
>
> After this CL, only utility processes remain to be moved off of Service
> Manager IPC.
>
> NOPRESUBMIT=true
>
> Bug: 977637
> Change-Id: I1d8205cb73ead904aa21b85d6cbee11cb3fc84f5
> Tbr: boliu@chromium.org
> Tbr: yucliu@chromium.org
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918375
> Reviewed-by: Martin Barbella <mbarbella@chromium.org>
> Reviewed-by: Robert Sesek <rsesek@chromium.org>
> Reviewed-by: Avi Drissman <avi@chromium.org>
> Commit-Queue: Ken Rockot <rockot@google.com>
> Cr-Commit-Position: refs/heads/master@{#717920}

NOPRESUBMIT=true

Bug: 977637
Change-Id: I9dd89104626ef73f81abd93c8a35310a2d6997a2
Tbr: boliu@chromium.org
Tbr: yucliu@chromium.org
Tbr: mbarbella@chromium.org
Tbr: avi@chromium.org
Tbr: rsesek@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930104Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#718334}

This change adds support to schedule when prediction model and host
model features are fetched from the remote Optimization Guide Service.
This change also updates naming for all fetch related permissions
checks to be not hint specific.

A future change will persist any models or host model features successfully
fetched.


Bug: 1001194
Change-Id: I412d2b36814cb1da092bab58c47419df277fddbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930052
Commit-Queue: Michael Crouse <mcrouse@chromium.org>
Reviewed-by: Sophie Chang <sophiechang@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718333}

This removes MC autoupgrades for blockable content (including
websockets) and adds a parameter to disable them for images. This
matches the behavior planned for launch.

Bug: 1025274, 1027686
Change-Id: Iaef5800c09368a547f6301c88208c535b60f9bdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928239Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Carlos IL <carlosil@chromium.org>
Auto-Submit: Carlos IL <carlosil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718332}

This CL updates some of the scrolling tests with platform specific test
expectations. (Since MockScrollbars no longer exist). The CL also gets
rid of duplicated tests without losing coverage.

Bug: 953847
Change-Id: I0bf10ef0434f9630624f73d9deb3986bd67661cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1925180Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Rahul Arakeri <arakeri@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#718331}

Using a ui::LatencyTracker to record all collected latency info
after drawing buffers have been swapped. This records a system health
metric (Event.Latency.ScrollBegin.Wheel.TimeToScrollUpdateSwapBegin4)
as well as the recording of latency info for debugging.

Bug: 992026
Change-Id: I904cbec84418426f06c9b237c2ead86566570302
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929264Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Chris Mumford <cmumford@google.com>
Cr-Commit-Position: refs/heads/master@{#718330}

Will delete unnecessary logs later.

Bug: 1026891
Change-Id: I56cbd4d73b5805418167c70ff142ce9a4a1e40a3
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929528Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: Yun Liu <yliuyliu@google.com>
Cr-Commit-Position: refs/heads/master@{#718329}

Using wpt-import in Chromium 4d49b6d2.
With Chromium commits locally applied on WPT:
e83dd93c "Limit backtracking on regexp called from blink."
500a74f5 "Add a runtime flag to enforce strict MIME type checks for workers."


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:
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools

NOAUTOREVERT=true
TBR=robertma

No-Export: true
Change-Id: I2f5692c8f03714f6b05143f015c06aeaf05d2569
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929525Reviewed-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@{#718328}

This adds a new chrome://connection-monitoring-detected page that
gives greater detail when Chrome detects known network interception
certificates.

Screenshots:
- Desktop: https://drive.google.com/file/d/14idB9uoKa4ezUqx-8VbtQJL0ayPWJwFJ/view
- Android: https://drive.google.com/file/d/1H2JMlxNcT2XVjb_ug-hsIRySoaFRTvqE/view

Bug: 1014711
Change-Id: Ic462a23c9d2e5fb3ca3ac4a1e6f1184d5d0ffc29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913715
Commit-Queue: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718327}

https://swiftshader.googlesource.com/SwiftShader.git/+log/c8d4d4254ca1..4584a9c2ccb9

git log c8d4d4254ca1..4584a9c2ccb9 --date=short --no-merges --format='%ad %ae %s'
2019-11-22 sugoi@google.com Handle new device extension properties

Created with:
  gclient setdep -r src/third_party/swiftshader@4584a9c2ccb9

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/swiftshader-chromium-autoroll
Please CC swiftshader-team+autoroll@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_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:b/144945388
Tbr: swiftshader-team+autoroll@google.com
Change-Id: I58afe1273165df11ffc2c295bc245314b9e37153
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1931274Reviewed-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@{#718326}

This diverged from original implementation, which did not use such 250ms delay,
and is potentially causing issues when xrandr and scale factor change events
come in a short interval, as observed in crbug.com/1019344.

Rationale:

With delayed update, events are coalesced thus leading to issues when
DisplayObserver is waiting only for display metrics changes, e.g: scale factor
changes. This is what RenderWidgetHostViewAura does, in order to react to
system's scale factor changes and sync with the compositor, etc.

In this specific issue, the delayed display list update behaves as follows:

Assuming display list initially has a single display (Display 1). XRandR/Gtk
events start coming:

1. Display 2 added
2. Display 1 removed
3. Display 2 metrics changed (scale factor)

Then they are coalesced into (and delivered through DisplayObserver interface):

1. Display 1 removed
2. Display 2 added

So, RenderWidgetHostViewAura::OnDisplayMetricsChanged() is never called and it
gets out of sync with the compositor.

Bug: 1019344
Change-Id: Ic6a7b1264b5656d36a0b25fd7e3bc07ab419568a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930853
Commit-Queue: Nick Yamane <nickdiego@igalia.com>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718325}

Explain the change to the isFallback attribute in the configuration file
for AOSP.

Change-Id: I3ade53829a8b3726434c0dc7a982505715a6be95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1931197
Commit-Queue: Richard Coles <torne@chromium.org>
Auto-Submit: Richard Coles <torne@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718324}

LoadMonitoringExtensionHostQueue was a wrapper around a
SerialExtensionHostQueue that also recorded metrics about the extension
hosts in the queue. We no longer need this data, so remove the wrapper
and mark the metrics as obsolete.

Bug: 1025804
Change-Id: I862caf2140c08a45a782df7f5cf690ef113f3b3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1927312Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718323}

Include details about how to use TrichromeWebView prerelease channels in
the documentation.

Bug: 1016502
Change-Id: Ifb7b8878f6a85d57e01a637922036f8870923d48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929519
Commit-Queue: Richard Coles <torne@chromium.org>
Auto-Submit: Richard Coles <torne@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718322}

--iron-icon-fill-color was being set directly for a <cr-icon-button>.
Even though the <cr-icon-button> currently uses a <iron-icon> which
defines and uses --iron-icon-fill-color, variables of components
contained within a component should not be used directly.

If there is <cr-icon-button> CSS variable what was is needed, that
should be used (which in this case there is one
--cr-icon-button-fill-color). If one does not exist, I think it makes
sense to create one and use that internally to set the CSS variable for
the contained element.

Bug: 1027466
Change-Id: I317a0dff63af9c5000596a16c6bc3038492d6c3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929105Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Commit-Queue: Esmael Elmoslimany <aee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718321}

Bug: 1024103
Test: Manual Test
Change-Id: I323573a32c3b3925e9840f1cabfe8029d5b5ac9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928195Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Yue Li <updowndota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718320}

Firefox passed
Chrome failed. Bug filed: https://crbug.com/375982

Bug: 900581
Change-Id: I33488661e2938c3fae6bef27ea6672b77047de84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1925347Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Hao Sheng <haozhes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718319}

This is a follow up to http://crrev.com/c/1926920 which adds a
use_webview_provider arg to instrumentation_test_apk. Unfortunately, the
use of --use-webview-provider in gn_isolate_map.pyl for
webview_cts_tests could not be converted to the gn arg because they do
some tricky things and don't use instrumentation_test_apk.

Change-Id: I7843d1210072f989b60bf08561786ac939eee2a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930100Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718318}

This CL modifies the previous code that adds 60 more seconds in the GPU
watchdog timeout on Windows. Instead of killing the GPU main thread at
the end, allow the GPU main thread to continue and write histograms for
all different events. This experiment is now extended to all platforms.

Below are UMA histograms for different platforms. The numbers are still
unreasonable.
ChromeOS : 58% of hangs is within 1 minute.
Android:  21% of hangs is within 1 minute. 14% after foregrounded.
Linux: 47% of hangs is within 1 minute.
Windows: 18% of hangs is within 1 minute. 87% makes progress after wait
          for a minute.

Bug:988344

Change-Id: I309f72944ff8eb180a009e4320b7a5e4cacf2ff6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928232
Commit-Queue: Maggie Chen <magchen@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718317}

Adds Attach/Detach as virtual methods on MessagePumpCFRunLoopBase
so that they can be called unconditionally from SequenceManagerImpl.

BUG=1002087

Change-Id: I8263188aa388a449c799b7bde17e7dac8b44d3be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1826517
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718316}

This is a reland of 48a84a2f

Original change's description:
> views: internalize DialogClientView
>
> DialogClientView is now unknown outside of //ui/views. This change
> makes it unknown outside of DialogDelegate - all use of it is via
> the public API DialogDelegate exposes. This will make fixing
> DialogClientView itself easier, and is also a neater API design
> across the board. Woo!
>
> Bug: 1011446
> Change-Id: I7abe8d29a44a73b78227440dec6e529165149a32
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929981
> Reviewed-by: Robert Liao <robliao@chromium.org>
> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#717994}

Bug: 1011446
Change-Id: I834cca98a40ca89c7333dd9541649106e87e7a27
Tbr: robliao@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1931382Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718315}

Followup to https://chromium-review.googlesource.com/c/chromium/src/+/1532997 .

When these SetFocusBehavior() calls were added, they were necessary on Mac, and
I think ACCESSIBLE_ONLY didn't exist.  Later LocationIconView::Init() was added
and overrode all this, but the (effectively dead) code here wasn't removed.
When I removed Init() early this year this code became live again, but isn't
desirable any longer.

Also does a few other trivial cleanups.

Bug: 1027110
Change-Id: I2a55c6d47db0fcb71160d4dda2e61eec82386b3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930327
Auto-Submit: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718314}

Encryption keys can contain non-utf8 binary content and are better
represented by ArrayBuffer being adopted in the API.

The patch also reorders the parameter order for future expansion
options.

Bug: 1000146
Change-Id: I7d1da9320c7e5c512f657deb5b211d3cf46d06d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919935
Commit-Queue: David Trainor <dtrainor@chromium.org>
Auto-Submit: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718313}

For small maps and sets that contain efficiently moveable items,
base::flat_[set|map] performs inserts better than std::[set|map],
because the former avoids mallocs. Additionally, base::flat_[set|map]
has a smaller overhead than its STL counterpart. Usage recommendation
can be found at base/containers/README.md.

All the substitutions in this CL are made on containers that are
expected to be small (< dozens of entries) and that hold light and
easily moveable items.

Change-Id: I2fe35182cd7c85479db4b7b6343ea9af031031ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1925438
Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718312}

At frame unload, report the number of attempted font family matches by the
frame, broken down by success / fail, system / web font, and top-level vs.
subframe.

For example, say font family C is present on the system, but font
families A, B and D are not. For this definition:

font-family: A, B, C, D;

font family A and B would be considered as unsuccessfully attempted, font
family C would be considered successfully attempted, and font family D wouldn't
contribute to the UKM counters.

Only the counts of font families match attempts are uploaded -- font family
names are not. Duplicate attempts to match the same font family name are
de-duplicated.

UKM privacy review doc (Google internal):
https://docs.google.com/document/d/1YtF7GvIhApgp1V7_9X8tSy4mZ-T9cssbMR3bVWw7AOE/edit?usp=sharing

Bug: 1025945
Change-Id: Id285d7a0dbe6a22db7e2ebb6d62d424e17285085
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907147Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718311}

This CL sets overflow of the tabs container to hidden so that when the
last tab animates out and its max-width goes to 0, the container's
width also shrinks.

Moving the gap internally to TabElement makes more sense in terms of
consistency since it's also included internally in the animation of
slideIn and slideOut. Also, previously, having 16px margin on all tabs
except the last tab caused the 16px to snap into place when the last
tab slides out and a new tab becomes the last-child.

Change-Id: Ia0bec1c6c86ab0aa2bfd769fc488429419ff9613
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1924619
Commit-Queue: John Lee <johntlee@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718310}

Change |video_geometry_setter_receivers_| from mojo::ReceiverSet
to mojo::Receiver because a single receiver is more appropriate.

Bug: 925450
Test: Cast youtube with and without VizDisplayCompositor enabled.
Change-Id: I7bd60820297a54e3a84bf268a015cb4625da7199
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1927223Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Guohui Deng <guohuideng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718309}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ccb488f8..dd8cccb7

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

Bug: 1026117,1009862
Change-Id: I0792903c54299e6169472e20129850f479813b30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928037Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: rajendrant <rajendrant@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: rajendrant <rajendrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718307}

Add field to log when the extension request is made.

Bug: 1006899
Change-Id: I21093c7ede9a6d1e823abf302be50c04973a43f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930182
Auto-Submit: Alex Vallee <avallee@chromium.org>
Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718306}

Bug: 1019015

Change-Id: I496f28a4b162bca993d378dc962405d85e09fba8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930687
Commit-Queue: Michael Spang <spang@chromium.org>
Auto-Submit: Michael Spang <spang@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718305}

The browser test UkmBrowserTest.EvictObsoleteSources checks that UKM sources id are properly marked as obsolete and deleted by navigating to and leaving a few example sites, and it began to fail recently due to external change in one of the sites used in the test case. This is because source ids in the tests were obtained from web contents, which could differ from the navigation source id, for example if the site executes a same-document navigation (e.g. history.pushState/replaceState) in the case of https://www.google.com used in the test (https://screenshot.googleplex.com/xofrBc6JHB8.png).

This CL updates the test to get the source id associated to the last committed navigation from the navigation handle instead, which is consistent with the id being marked by SourceUrlRecorderWebContentsObserver::DidFinishNavigation that we aim to test.
https://cs.chromium.org/chromium/src/components/ukm/content/source_url_recorder.cc?type=cs&q=+MarkSourceForDeletion&g=0&l=237
This also changes to use an embedded test server to not depend on external content anymore.

Bug: 1004296
Change-Id: I08d7f225588598655dd946f8661d32a8dbdf53ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929018Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Yue Ru Sun <yrsun@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718304}

The permissions-wizard checks host permissions by running the
(Me2Me or It2Me) host binary with a command-line parameter. This CL
ensures that the binary triggers a fake capturer in this situation.
This causes the Security & Privacy screen to include the app in the
list, so the user can check its box.

Bug: 1027317
Change-Id: Icb38737170c5dcaa544499c9708d907845b95845
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930546
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Auto-Submit: Lambros Lambrou <lambroslambrou@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718303}

This CL adds logic to "remember" the user pressing 'Enter' when
autocomplete matches are stale. This happens if the user types too fast
and presses 'Enter' immediately. Currently, the realbox either does nothing
or navigates to a stale result. After this change, the realbox does nothing
until up-to-date results have arrived. it then navigates to the default
match, if one exists, assuming that navigation to the default match was the
user intent, signaled by typing too fast and pressing 'Enter'.

Bug: 1024109
Change-Id: I67e434419e586d3488b1239b9fa37da8aaa4fec4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928214
Commit-Queue: Moe Ahmadi <mahmadi@chromium.org>
Reviewed-by: Dan Beam <dbeam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718302}

This is a small refactoring to make it clearer that the inner and outer
viewport scroll nodes' existence is linked. That is, if either one is
non-null, then the other one must be as well.

Viewport scroll nodes (and others like page scale, elastic transform,
etc.) are only created for the renderer's main-frame compositor. In an
OOPIF renderer or the UI compositor, these property nodes are never
registered and will always return null. In the main-frame renderer, we
can always assume they're non-null.

Bug: 1016229
Change-Id: Ie022d3d9cb937848a0ceb6560e936ce1ff06142f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871329
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718301}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ea02a5d30e4f..e75a355406dc


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

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
Bug: chromium:992974
Tbr: jbudorick@google.com
Change-Id: I2dfa5bef80799f6fe9fa96527e9dd3c36c43d4fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928028Reviewed-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@{#718300}

Bug: 1007633
Change-Id: I0a020fa00b0d48a5cdcddb75062bad878b17e183
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1931263
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Jun Mukai <mukai@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718299}