GitLab

This removes the final references to the Chromium-based ANGLE
GTests from CI. After this we can switch ANGLE over to building
standalone tests by default.

Bug: angleproject:5124
Change-Id: I1577318ee0883cd76dceb43bbe5b0b3e29b43e82
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491518
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820124}

Change the tabindex=0 from .xf-panel-label-text to its parent
.xf-panel-text to have the .xf-panel-secondary-text content included in
the a11y for Chromevox.

This makes the estimated time progress available to screen reader users.

Bug: 1086053
Change-Id: Id39560b2249fb12ff4f49fb39c7439746fc1271c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2494400
Auto-Submit: Luciano Pacheco <lucmult@chromium.org>
Reviewed-by: Alex Danilo <adanilo@chromium.org>
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820123}

Chromium style guide recommends grouping overrides for a given interface
together, with no new line in between methods.

This CL applies the rule to blink::Platform implementers.

Change-Id: I27fc748361d63a1bb18b8a705b46572aadeae80c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2492667
Commit-Queue: Charlie Reis <creis@chromium.org>
Auto-Submit: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820122}

Before:
Compiling //components' PaymentManifestWebdataServiceAndroid in
//weblayer would fail because it depends on //chrome's
payment_manifest_webdata_service_android.

Changes:
Move //components' PaymentManifestWebdataServiceAndroid into //chrome.

After:
PaymentManifestWebdataServiceAndroid lives in //chrome and wouldn't
be compiled when //weblayer compile //components payment targets.
Going forwards, PaymentManifestWebdataService will only be used in
Chrome payment, WebLayer payment will find a replacement for it.

Bug: 1140637

Change-Id: I4a07761c5220c930cf3c0abd05d9072b63179693
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488548Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820121}

Bug: 1138282
Change-Id: Ice4b0f604d6bc5e4aa216c30066cd49777cf15e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490962Reviewed-by: Noel Gordon <noel@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820120}

This avoids red webkit_lint step on bots and sheriff efforts to fix
that. Also gives developers warning for manual redundant test
expectations.

Change-Id: I29a46031686812372a38e394e89f67d2da441c47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490825
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820119}

Add filters for flaking webgl_conformance tests.
Add maps tests to Fuchsia x64 CI bot. Increases bot time per run by ~4 minutes.

Bug: 1133540
Change-Id: Ic064b2a7608e0bbf97c02163908c9264c906d737
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493783
Auto-Submit: Chong Gu <chonggu@google.com>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Chong Gu <chonggu@google.com>
Cr-Commit-Position: refs/heads/master@{#820118}

Changes to Autofill Interactive UI tests have been made,
removing the test filters for Win7 to see if those changes
helped these flaky tests as well.

Bug: 967588
Change-Id: I89738958f3caba7ecca4eb8d90af1cf1040d716f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491979Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Auto-Submit: Ian Struiksma <ianstruiksma@google.com>
Commit-Queue: Ian Struiksma <ianstruiksma@google.com>
Cr-Commit-Position: refs/heads/master@{#820117}

Bug: 1040826
Change-Id: If834f99a2d97c295cbe0e574538b891533992443
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2494182
Auto-Submit: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820116}

Bug: 1138281
Change-Id: I3d9feb0156ead58ee3b2765522a888ab8e2a42ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490966Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820115}

This reverts mixed forms inside iframes to the pre-mixed form warning
behavior, they are silently blocked from submitting, and a console
error is shown.

Bug: 1141628
Change-Id: Ibabdc6d250a347bde8475d94c37402b971c0bdec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493302
Commit-Queue: Carlos IL <carlosil@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820114}

Bug: 1110617
Change-Id: I02c5dcfe640355074dbbf4698ac510b5cdb074fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493839Reviewed-by: Frank Liberato <liberato@chromium.org>
Commit-Queue: Ted Meyer <tmathmeyer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820113}

Total runtime drops:
Linux x64: 65m 39s -> 19m 40s
Linux x86: 83m 35s -> 22m 53s
Win x64:   93m 57s -> 25m 30s
Win x86:  103m 25s -> 27m 44s

Bug: angleproject:5124
Change-Id: I2215e7adad8802120ad5656bbb85ce126422ea14
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490987
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820112}

Image format not supported was never implemented and was throwing off our
labels in UMA by 1.

Bug: 1111517
Change-Id: I62a8a13fd09dc233ed461fe6715e3d308dfec546
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488718Reviewed-by: Weilun Shi <sweilun@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Ben Goldberger <benwgold@google.com>
Commit-Queue: Ben Goldberger <benwgold@google.com>
Cr-Commit-Position: refs/heads/master@{#820111}

TL;DR: This replacement does not and should not change the behaviour of chrome (both ash and lacros). The change is mostly mechanical except for inserting "//build:chromeos_buildflags" into appropriate deps in BUILD.gn.

Lacros-chrome is currently built as target_os=linux, thus current “OS_CHROMEOS” blocks are not included in lacros-chrome and only included in chromeos-chrome (=ash-chrome).

Since we are planning to switch lacros-chrome to target_os=chromeos, we have to replace OS_CHROMEOS macro with BUILDFLAG(IS_ASH) to ensure that lacros-chrome does not include “current OS_CHROMEOS blocks” after the switch. It also replaces is_chromeos in GN files with is_ash.

Please note that any new defined(OS_CHROMEOS) and is_chromeos introduced to should be consistent with the new meaning.

For more info please refer to http://go/lacros-replace-chromeos-macro-with-ash

Bug: 1052397
Change-Id: I84d5e5578843426df3a1f1b1a68a322b74a94b04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491593Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Yuta Hijikata <ythjkt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820110}

Bug: 1138279
Change-Id: I39b513667cec27eecd02920bd5148b10d087b844
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490968Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820109}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=benmason@chromium.org

Change-Id: I0208618e3991528526c2519beb5cd1f40108c4ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493706Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#820108}

This reverts commit c4cbb461.

Reason for revert: this CSS is used after all. See bug and
AppLauncherLoginHandler::UpdateLogin()

Bug: 1141291

Original change's description:
> Remove defunct NTP css.
>
> action-link no longer exists on the NTP.
>
> Bug: none
> Change-Id: I4df61932f6b1885bd98a56f4963aead4dafe352c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2480889
> Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
> Commit-Queue: Evan Stade <estade@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#818595}

TBR=estade@chromium.org,gayane@chromium.org

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

Bug: none
Change-Id: I4c0ead807a2064f5d51ef7aa631ac3602433697a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491972Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820107}

Using wpt-import in Chromium d63ab91a.

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:
eae@chromium.org, szager@chromium.org:
  external/wpt/intersection-observer
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools
futhark@chromium.org, andruud@chromium.org, ericwilligers@chromium.org, shend@chromium.org:
  external/wpt/css/css-conditional
hbos@chromium.org, hta@chromium.org, guidou@chromium.org, philipp.hancke@googlemail.com:
  external/wpt/webrtc
hongchan@chromium.org, rtoy@chromium.org:
  external/wpt/webaudio
jsbell@chromium.org:
  external/wpt/encoding
  external/wpt/resources
kojii@chromium.org:
  external/wpt/css/css-writing-modes
kojii@chromium.org, mstensho@chromium.org:
  external/wpt/css/CSS2
nzolghadr@chromium.org, mustaq@chromium.org:
  external/wpt/pointerevents
rego@igalia.com:
  external/wpt/css/css-contain
  external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests
xlai@chromium.org, jinho.bang@samsung.com, hs1217.lee@samsung.com:
  external/wpt/css/geometry

NOAUTOREVERT=true
TBR=robertma@google.com

No-Export: true
Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-payments-fyi-rel
Change-Id: Idab38290b0fa91ef15345c02bbb0a04a028c712d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493541Reviewed-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@{#820106}

Already disabled on Mac, but very flaky on Win/Linux too

TBR=jdeblasio@chromium.org

Bug: 1139955
Change-Id: I7d8b8e79adf4b280d2ed092c33423cc6fceec096
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493584
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820105}

Roll Chrome Linux PGO profile from chrome-linux-master-1603389584-2bc38f3ea5293ebadf0ddb7fc3a88d54d7569967.profdata to chrome-linux-master-1603410964-a2043bc9224640fe9aacb254c17e5c20cde84377.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium
Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I406e25c64d867112aa84033be5840f3e7b5960f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493921Reviewed-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@{#820104}

Context:
Since SslValidityChecker depends on //chrome's browser_process,
profiles, reputation, safe_browsing, ssl, it is unlikely to become a
component shareable with WebLayer. Going forward, SslValidityChecker
will remain in Chrome payment, WebLayer payment will check the SSL
state in its own ways.

Before:
//components' SsLValidityChecker depends on //chrome's
ssl_validity_checker_android, which disallows //weblayer from compiling
SsLValidityChecker when it tries to compile the //components payment
targets.

Change:
This CL moves //components's SsLValidityChecker into //chrome.

After:
SsLValidityChecker and ssl_validity_checker_android both
lives in //chrome, so //weblayer's compilation of the //components
payment targets does not include these two files.

Bug: 1140637

Change-Id: I59d5b4b05533fea4d27dc4b62ccdc61f8e9c1d49
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491543Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820103}

This is useful because the internal Chromium test bots use debug
builds of Chrome.

BUG=1115604

Change-Id: Iee028c9e15053a4ff9a075b680b35120a2721d07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493152Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820102}

Starting in macOS Big Sur applications must request permission to use
Bluetooth. The getAvailability() API is used by apps to determine
whether the system supports Bluetooth and so they should show UI for
it.

getAvailability() uses BluetoothAdapter::IsPresent() to check if an
adapter was found. This triggers the new macOS permission prompt because
it creates a CBCentralManager. This is bad because sites tend to call it
early and without providing any context for why the permission is being
requested at this time.

This change modifies the IsPresent() method to use the IORegistry to
detect whether the system has Bluetooth hardware and delays the full
initialization of the BluetoothAdapterMac object until it is necessary
to connect to a device or start a scan.

Bug: 1138593
Change-Id: I6d3d77666dbb8f9bf40d0747d2a2859daa5f5844
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2476749
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820101}

This CL uses cursor-compositing to replace the cursor on screen while it
is being dragged.

Originally, when a user drags using the cursor while in capture region
mode, the selected/dragged area lags behind the cursor movements. To
solve that issue, the original screenshot_controller logic hides the
cursor on drag and draws a pseudo cursor directly on the canvas. After
attempting to draw a pseudo cursor on the canvas directly and
encountering issues, it was determined that a better solution would be
to use cursor-compositing, which is what this CL does.

Test: manual, added test
Bug: 1135700
Change-Id: Id35115ab53641c168d8dec4a62756f61d21c967e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487720
Commit-Queue: Richard Chui <richui@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820100}

Right now there's no easy way to invoke a native UI in the browser using
devtools protocol. The API provides a way to open/close UI, particularly
Tab Search UI. It's mainly used for telemetry based performance tests.

Related CL:

Doc: https://docs.google.com/document/d/1-1ijT7wt05hlBZmSKjX_DaTCzVqpxbfTM1y-j7kYHlc
https: //chromium-review.googlesource.com/c/catapult/+/2488841
Bug: 1099917
Change-Id: Id87c9eb6f66c05278fdf722562ba8794e466d8e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488764
Commit-Queue: Yuheng Huang <yuhengh@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820099}

This CL removes FetchRequestData::{Set,}Context() and sets FETCH type
for ResourceRequest from FetchManager since we don't have code paths
that could have given different types and FetchRequestData can only be
FETCH.

It also updates mojom::RequestContextType with
mojom::blink::RequestContextType to use the Blink variant.

Bug: 1059639
Change-Id: I4f55fb48c18fe81917e24241268c6eb8b49de69b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490973Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Julie Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/master@{#820098}

On non-ash chrome, only call VaapiWrapper::PreSandboxInitialization
if we're using the kEnableAcceleratedVideoDecode flag.

Change-Id: Ifc6befb6196627ed41aa07077c8f21fa979b9ba1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2483862
Commit-Queue: Ted Meyer <tmathmeyer@chromium.org>
Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820097}

There were several places where code was trying to determine if a
host could be reused and was suitable for a specific SiteInfo. This
change simply adds 2 helpers to contain this logic and make the
code a little easier to read.

Bug: 1015882
Change-Id: If156be85141092ad43a38c9dd5c413e7280884f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2489160
Commit-Queue: Aaron Colwell <acolwell@chromium.org>
Auto-Submit: Aaron Colwell <acolwell@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820096}

Before this CL navigation links in OS settings menu were not announced
on touch. This CL fixes that issues, it removes div elemts in the anchor
tags that caused this issue.

Bug: 1115704
Change-Id: I83676fad434768a6b23bad5e2f7eb55b65348698
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490785Reviewed-by: Regan Hsu <hsuregan@chromium.org>
Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com>
Cr-Commit-Position: refs/heads/master@{#820095}

TBR=qinmin@chromium.org

Bug: 1141263, 1141278
Change-Id: Ife8ca04cd1599e5e736903f823547930b20a7974
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493582Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820094}

Bug: 1130644
Change-Id: I15bfaec588cc0b2bd0a08bc555d499b28661cef5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490970Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820093}

Bug: 1138278
Change-Id: I564dc33d57f7e9591e8b798f88094147635d9c3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490969Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820092}

Since TabGridDialog and omnibox both use the ScrimView from
RootUiCoordinator, there will be a conflict when user try to open
dialog from tab strip when omnibox is focused. This CL fixes this issue
by suppressing tab strip when omnibox is focused and restoring
visibility when omnibox loses focus.

Bug: 1096358
Change-Id: I3b12fe1f1753a10df691af61ac23a6ff9a0ea61e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2486622Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820091}

Bug: b/170619368
Change-Id: Ibea31679adb343c79335f884ca5675d75b252ffe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493821Reviewed-by: David Schinazi <dschinazi@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820090}

This reverts commit e2838f16.

Reason for revert: Causing test fail on Fuchsia x64 CI bot (crbug.com/1141702).

Bug: 1141702

Original change's description:
> [Fuchsia] Enable R8 and R8G8 buffer formats
>
> Sysmem now supports R8 and R8G8 image formats, so it can be used to R8
> and R8G8 GpuMemoryBuffers
>
> Bug: 1141538
> Change-Id: I790c6886d67f49c09f2e2c4a93db7a27450aa30f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491995
> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
> Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
> Auto-Submit: Sergey Ulanov <sergeyu@chromium.org>
> Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#820012}

TBR=kmarshall@chromium.org,sergeyu@chromium.org

Change-Id: Ia0fdb609077aded3b85fd577bab0aa5df5cc4250
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1141538
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2492917Reviewed-by: David Dorwin <ddorwin@chromium.org>
Commit-Queue: David Dorwin <ddorwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820089}

DirectSocketsServiceImpl::OpenTcpSocket() now calls
CreateTCPConnectedSocket() on the network context.

Browser test DirectSocketsBrowserTest.OpenTcp_Options verifies
that the remote address, port, buffer sizes and no-delay flag
are passed successfully.

NavigatorSocket::PendingRequest has been split into
TCPSocket and UDPSocket classes, currently with no web-exposed
members implemented.
https://github.com/WICG/raw-sockets/blob/master/docs/explainer.md#tcp
https://github.com/WICG/raw-sockets/blob/master/docs/explainer.md#udp




Explainer: https://github.com/WICG/raw-sockets/blob/master/docs/explainer.md

Intent to Prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/ARtkaw4e9T4/m/npjeMssPCAAJ

Design doc:
https://docs.google.com/document/d/1Xa5nFkIWxkL3hZHvDYWPhT8sZvNeFpCUKNuqIwZHxnE/edit?usp=sharing


This is a reland of https://chromium-review.googlesource.com/c/chromium/src/+/2391181
which was reverted https://chromium-review.googlesource.com/c/chromium/src/+/2404821
as 'New tests are failing on many builders'


Some new tests are temporarily disabled while we investigate their
failures on specific bots - crbug.com/1141241

Bug: 905818,1141241
Change-Id: I13bedf1fdc160b3d1fc857a3debde73e3203ffee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465343
Auto-Submit: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Glen Robertson <glenrob@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820088}

https://android.googlesource.com/platform/external/perfetto.git/+log/c4af5cd3397d..2e5b59565826

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

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

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

Tbr: perfetto-bugs@google.com
Change-Id: I12dd6f40cc2b072493b7dcc215d1ebddf40041b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493127Reviewed-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@{#820087}

Before the CL, //components' JourneyLogger depends on //chrome's
journey_logger_android. This disallows WebLayer from depending on
JourneyLogger.

So this CL moves journey_logger_android into //components.

After the CL, WebLayer can depend on //components' JourneyLogger.

Bug: 1140637

Change-Id: I881fc8dd65071907e424f1184ea221f5bca0d147
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491606Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820086}

Add Mojo and protobuf messages for Chrome to send on blur to the IME
service.

Bug: 1019541
Change-Id: If01c8e2dceaa13c7218ee13913f32a26ddcfe52e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2483944Reviewed-by: Keith Lee <keithlee@chromium.org>
Reviewed-by: Martin Barbella <mbarbella@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820085}