GitLab

This reverts commit b05d8793.

Reason for revert: Broke ios full_configs bot. See:
https://ci.chromium.org/p/chromium/builders/ci/ios-simulator-full-configs/25885

Doesn't look like this change triggered the full_config bots on try.

Original change's description:
> Rework generated_script handling in MB.
> 
> It turns out the work I did on the "wrapped_*" targets in
> gn_isolate_map was somewhat overlapping with the already-existing
> iOS work to declare things as "generated_scripts". However, the
> generated_scripts did not include test_env.py.
> 
> So, this CL rearranges things so that the generated script will call
> test_env.py, and then we can share logic between the generated_script
> targets (and every target on iOS and LaCrOS) and use that as the
> basis for the rest of the work going forward.
> 
> Bug: 816629
> Change-Id: I9d55c3f1587defcb599ddf1df838dd9ed5b6a12c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357917
> Reviewed-by: Erik Staab <estaab@chromium.org>
> Commit-Queue: Dirk Pranke <dpranke@google.com>
> Cr-Commit-Position: refs/heads/master@{#799171}

TBR=dpranke@google.com,estaab@chromium.org,jeffyoon@chromium.org

Change-Id: I94597d58417f7aa76320579ca282293e6b643811
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 816629
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364014Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799629}

https://docs.google.com/document/d/1EW90R9jfRtBKZA8VHV2_EBqS1okLNmUxrbboCmVpNOk

Bug: 1112872
Change-Id: Ie8966937049ae4d2c36b1e81e274df6b1260493b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364188
Auto-Submit: Fred Mello <fredmello@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799628}

https://android.googlesource.com/platform/external/perfetto.git/+log/0795384a7997..e60f72f6801e

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-linux-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: I1695e9c87cb5b54de3972c2817422308dce998d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363973Reviewed-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@{#799627}

This CL adds "cabal", "dat", "did", "dweb", "ethereum", "hyper",
"ipfs", "ipns", "ssb" to the safelist of
navigator.registerProtocolHandler. Chrome status entry is [1]
and feature has been discussed in [2] [3] [4] [5]. Currently,
the WHATWG and WPT changes are pending on the Mozilla position
review [6].

[1] https://www.chromestatus.com/feature/4776602869170176
[2] https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/29sFh4tTdcs/K4XroilVBAAJ
[3] https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/7nHTRUP1EGY
[4] https://github.com/whatwg/html/issues/3935
[5] https://github.com/whatwg/html/issues/3998
[6] https://github.com/mozilla/standards-positions/issues/339

Bug: 651311
Change-Id: Iba45706e985015cf86bd80adef990abd0980a638
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153064Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Frédéric Wang <fwang@igalia.com>
Cr-Commit-Position: refs/heads/master@{#799626}

The SMSReceiver API has been renamed to WebOTP in specification [1]. We
currently use SMSReceiverStart in Blink.UseCounter.Features to capture
the API usage. To better align with the spec we should update the name.

[1] https://github.com/WICG/web-otp

Bug: 1117238
Change-Id: I982e5abf499ea0dc575163092769040d927a262f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360474Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799625}

This CL adds high-level trusted vault key rotation logic. Once vault
keys are marked as stale, following FetchKeys() call will trigger
attempt to download fresh keys from the vault server. This makes
StandaloneTrustedVaultBackend::FetchKeys() asynchronous, but result
is populated immediately if preconditions aren't met (e.g. device isn't
registered, device somehow misses old vault keys or current account
isn't syncing one).

StandaloneTrustedVaultBackend allows only one ongoing request to the
vault server and only one ongoing fetch keys attempt at the time
(following TrustedVaultClient::FetchKeys() documentation). In case of
abandoning download keys request, ongoing fetch keys fulfilled
immediately.

Bug: 1102340
Change-Id: I2413176f03b07e67a72315a549add16f5e328678
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340977
Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799624}

This change cleans up the CodeCacheHost fuzzer, moving the per-testcase
code into the CodeCacheHostTestcase object and removing
CodeCacheHostFuzzerContext since this was redundant.

Bug: 1076336
Change-Id: I8736106edadb4a88c9d46a007ed5404fec6d4d4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2329571
Commit-Queue: Mark Brand <markbrand@google.com>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799623}

To organize the ownership better, let's move these files into a
new folder -- chromeos/login/app_mode/.

Change-Id: Iae18edd7bba7fb6d762e26a320db4597524a6a91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362647
Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org>
Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799622}

Add new update progress calculation which is based on total time left
expectation. New update progress is gradually changed during the update.

Bug: 1117036
Change-Id: I11478e06af64137ebc7643495d198537d1031657
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358681Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Commit-Queue: Roman Aleksandrov <raleksandrov@google.com>
Cr-Commit-Position: refs/heads/master@{#799621}

Skia is trying to remove the use of ctors and instead just have
clients set the values on the structs they need.

Change-Id: I7a934b256068bbbfcffab06490f1178cfbd2fca4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363712Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Greg Daniel <egdaniel@google.com>
Cr-Commit-Position: refs/heads/master@{#799620}

Following the change that adds the grouping.xml check:
https://chromium-review.googlesource.com/c/chromium/src/+/2303313

Also updates grouping.xml to make sure the test passes on CQ.

Bug: 1107860
Change-Id: Icb4eea6540c6ddeb95dcd5efa9ea86ccec2afc13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362988Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799619}

The Clank team is reviewing the ownership
of all `/android` directories and adding/updating OWNERS
as part of an effort to normalize code health metrics
across different data sources.

https://docs.google.com/document/d/1IYe0TIGAsJl-gZL39l31a2zUa_YasmcyfOIC-zllU_s

Bug: 1112872
Change-Id: I71fedd33bb14cb4a449db71c253bd48f23c20097
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362632
Auto-Submit: Fred Mello <fredmello@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799618}

Implements the changes from https://github.com/WICG/native-file-system/pull/219.

Change-Id: Ic785f0362b5c73a843145c5384f063cf24770b7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360597
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799617}

* Shorten code
* Use const more
* Inline temps
* Use safe conversions for float -> int
* TimeDelta::InMicrosecondsF() returns a double


Bug: none
Change-Id: I798ee7107bcbda863f95ee7921c4ddfd76768183
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359008
Commit-Queue: Cait Phillips <caitkp@chromium.org>
Reviewed-by: Cait Phillips <caitkp@chromium.org>
Auto-Submit: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799616}

This infobar will be used (via field trials) to display updated info
about current OS support and provide users with a link to more info.
The infobar receives both activation info (which configs to show for)
and the actual strings to display via field trials, so it can be updated
for deployed Chrome instances without an update cycle.

This change adds:
* The infobar itself
* A feature MacSystemInfobar that controls whether the feature is
  enabled and if so which configs (Arm or Rosetta) it's enabled in
* A switch --force-mac-system-infobar which causes the infobar to act as
  though it was running on a specified system, for both manual and
  automatic tests
* A variety of IDS_MAC_SYSTEM_INFOBAR_* constants to customize the
  infobar's message, link, and link text
* Unit tests for the logic to interpret the feature and the
  enable/disable configs

Bug: 1116578
Change-Id: Ie7fd6e772a0112a17e794d1b8fcb009c57ebed4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360479
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799615}

Although not rolled out yet, some tests fail when structured names
are globally enabled. This CL proactively fixes most remaining issues.


Change-Id: I0f0a54612be8118cf472987cd022b702416b21be
Bug: 1099202
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362734
Commit-Queue: Matthias Körber <koerber@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799614}

The functionality had been available for non-Ozone path.  This CL moves
the necessary enum and utility function to the component so Ozone can
use it.

Bug: 1097007
Change-Id: Id7070dc7a87e4efc36d3611f072b89c4ce9e4da2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359040Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Maksim Sisov (GMT+3) <msisov@igalia.com>
Commit-Queue: Alexander Dunaev <adunaev@igalia.com>
Cr-Commit-Position: refs/heads/master@{#799613}

Turns out the fix in https://crrev.com/c/2346914 doesn't work. This
adresses the problem at the root cause:

RenderWidgetHostViewAura::OnWindowFocused only ignores gaining focus but
not losing it, meaning clicking on the page while the scanning dialog is
open loses focus but the page doesn't get it back from calling Focus()
in WebContentsImpl::IsClipboardPasteAllowedWrapperCallback since
host()->IsIgnoringInputEvents() still returns true at that point.

The fix is to not lose focus in the first place by moving the
IsIgnoringInputEvents call at the top of OnWindowFocused.

Bug: 1100902
Change-Id: I0cfc0d79436514eac50a81df803abac10f71f430
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363692Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799612}

R=pkasting@chromium.org

Bug: 1117548
Change-Id: I9cf42b1e3c866f51a36feceb6186929c92a36ba7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362975
Auto-Submit: Stephen Lin <stephenlin@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799611}

CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-chrome
TBR=chrome-os-gardeners@google.com

Change-Id: I855f54afdbf00736904f83fdba074473f0b7b057
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362346Reviewed-by: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#799610}

https://webrtc.googlesource.com/src.git/+log/876a3dc88ac4..bcdfc8975ea2

2020-08-19 terelius@webrtc.org Group decoded frame events by SSRC when compressing RTC event log.
2020-08-19 nisse@webrtc.org Delete CodecInfo::is_hardware_accelerated

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

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

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

Bug: None
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: Ic41a19e53710c7432d7d68416ce1be8304b7f1a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364265Reviewed-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@{#799609}

Roll Chrome Mac PGO profile from chrome-mac-master-1597795195-73a3893f6ac2e232e6f2551f9490f3476218900c.profdata to chrome-mac-master-1597838234-9c863d7c9dc15ae374a8358c943ba78053f4a35c.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-mac-chromium
Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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: chrome/try:mac-chrome
Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com
Change-Id: Ie54f324eea4a0c4b3c89e47ff911fbfab55114f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363378Reviewed-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@{#799608}

Uses a longer timeout when waiting as video capture device enumeration
seems to take longer on the Marshmallow tablet testers.

Bug: 1115888
Change-Id: I7145fd957571094d149ef928f83c92d682512b97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363355Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799607}

This CL fixes the issue of "Tab title is missing on the single Tab when
Instant Start is enabled". When missing the creation of
TabAttributeCache, SingleTabSwitcherCoordinator won't have a
TabModelSelectorTabObserver, thus will miss the
TabModelSelectorTabObserver#onTitleUpdated(Tab tab) etc. events.

Bug: 1097789
Change-Id: If7037519e4f48292828c390a89cc4cb79fd966a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363715
Commit-Queue: Xi Han <hanxi@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799606}

Change-Id: I4b309c8a1538d0e65761b283410176cfbcd60dc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362612
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Auto-Submit: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799605}

Change the wording and location of the proxy server disclosure in the
transparency panel.

Bug: 1116961
Test: unittests
Change-Id: Id394511a6357329e629a37f19a4f83a4d49ea0db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360073Reviewed-by: Andreea-Elena Costinas <acostinas@google.com>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Reviewed-by: Greg Levin <glevin@chromium.org>
Commit-Queue: Andreea-Elena Costinas <acostinas@google.com>
Cr-Commit-Position: refs/heads/master@{#799604}

Manual reland take 2:
Original CL: https://chromium-review.googlesource.com/c/chromium/src/+/2029609
Revert 1: https://chromium-review.googlesource.com/c/chromium/src/+/2109970
Revert 2: https://chromium-review.googlesource.com/c/chromium/src/+/2254470
Reason for revert: flaky DCHECK in AssertExpectedConcurrency
Fix: DCHECK ended being removed in https://chromium-review.googlesource.com/c/chromium/src/+/2363074
Additional changes: the impl now uses exposed worker_count and
IsCompleted() instead of available_concurrent_marking_task_ids_/
active_markers_, thus reducing complexity and removing need for
concurrent_marker_bootstrapping_lock_.

Original Description:
Note: This CL enables feature BlinkHeapConcurrentMarking to get
the desired behavior. However, we should land enabling
BlinkHeapConcurrentMarking on its own first.

active_markers + GlobalPoolSize() is used to determine
the desired number of workers.

NotifyConcurrencyIncrease() is called periodically from
ConcurrentMarkingStep() if GlobalPoolSize() > 0,
to make sure enough workers are scheduled.

Bug: 1046343
Change-Id: Iac4941d804714745545314eec1e1b33d1734a4a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2261352
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Reviewed-by: Omer Katz <omerkatz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799603}

Using wpt-import in Chromium f3714abe.
With Chromium commits locally applied on WPT:
ed257e2b "[CORS] Set preflight request mode correctly"
3b705a74 "WPT: Service Worker: Add unexpected state check to wait_for_state()"


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

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

https://chromium.googlesource.com/external/github.com/AOMediaCodec/libavif.git/+log/fdc636b4ce09..3fd2db22eef9

$ git log fdc636b4c..3fd2db22e --date=short --no-merges --format='%ad %ae %s'
2020-08-13 jdrago Remove range and sample position from avifImageStealPlanes(), transfer alphaRange manually
2020-08-13 jdrago Revert "Decouple CICP parsing/overriding from decoder->image; ensure CICP is valid and set at the end of Parse and NextImage"
2020-08-13 jdrago Decouple CICP parsing/overriding from decoder->image; ensure CICP is valid and set at the end of Parse and NextImage
2020-08-13 jdrago Remove recent change as it confuses MS' static analysis

Created with:
  roll-dep src/third_party/libavif/src
R=dalecurtis@chromium.org

Change-Id: I097aa9e4b01cb484fcd1fe54bec0b545aa465b29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363658Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Wan-Teh Chang <wtc@google.com>
Cr-Commit-Position: refs/heads/master@{#799601}

Android-R adds an attribution tag to Context. This tag can be used to
identify what parts of an application are requesting/using services.
Chrome code assumes a single Context, and for WebLayer that Context is
the application context. WebLayer calls getApplicationContext() on the
Context supplied to it. This means the attribution tag set on the
Context supplied to WebLayer is lost.

This patch changes WebLayer so that the attribution tag of the supplied
Context is propagated to the Context used by Chrome/WebLayer. This gives
the user of WebLayer a way to attribute usage of system services to
WebLayer.

BUG=1085041
TEST=none

Change-Id: I65eeea60289e57d563875754231658466c37dddd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2361022Reviewed-by: Clark DuVall <cduvall@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799600}

It's similar to PasswordStore::::Observer::OnLoginsChanged() but
captures the originating store too.

Bug: 1108422
Change-Id: I30ce80beec9d7a38bd4d148fe80b8efba722437d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362610
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799599}

https://android.googlesource.com/platform/external/perfetto.git/+log/e60f72f6801e..72e31331da03

2020-08-19 fmayer@google.com Merge changes Icbb2ec8e,I6981cc7a,I14af99be
2020-08-19 lalitm@google.com Merge "tp: rework thread state in prep for parsing blocked reason"

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

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

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

Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel
Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: I1e470b50294bdc02742358810ee51d2b65d8c583
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364263Reviewed-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@{#799598}

The scheduler prioritizes commits when we're in a scroll and there's
a scroll handler. Today this is done by checking for scroll event
handlers in scroll begin and storing that state. It seems like we could
simply apply the scheduling strategy dynamically after scroll begin,
which allows us to remove some connections between LayerTreeHostImpl and
the ThreadedInputHandler.

Bug: 915926
Change-Id: Ic7b0c7b388f77c2f708e5f73c235a9a0e5511d1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363724
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799597}

This CL adds check for scripts availability only
if kPasswordChageInSettings flag is enabled.
This CL also changes PasswordScriptsFetcherBridge so it does not use
Profile information and can be used in SafetyCheck to prewarm cache.

Bug: 1086114, 1092444
Change-Id: I87021c2e65c7886ad90ee80844b9a2e46fb4b626
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351994
Commit-Queue: Milica Selakovic <selakovic@google.com>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Reviewed-by: Andrey Zaytsev <andzaytsev@google.com>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799596}

mMaxPermissionOrder was not updated correctly. Avoid this problem by
not storing it globally.

Bug: 1117422
Change-Id: Ic200c7f6130347cec6635e4d09fa460c99a3a7da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364533
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Auto-Submit: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799595}

Further CLs will migrate blink code to use these bit by bit.

BUG=1096617

Change-Id: Iceb0090a4ea835cf5a524a7333da65068ee7afb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363552Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799594}

This CL adds an interface through which LayerTreeHostImpl and the
"graphics" side of the compositor can talk to the input handler. For
now, LTHI keeps the concrete object and still owns it but eventually
this will be moved out and LTHI will only have a reference to the
interface.

A followup will add an interface for the other direction so that the
input system doesn't have to have a concrete reference to LTHI.

Bug: 915926
Change-Id: Ieb4c0642e6674b6f09e8c7d8b6ff366cc8179bce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359190Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799593}

Bug: 1062344
Change-Id: I45a3ef9f01e234c342bd442ff9b38d802db5a9fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362756Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Victor Vianna <victorvianna@google.com>
Cr-Commit-Position: refs/heads/master@{#799592}

Bug: 1115489

AX-Relnotes: n/a
Change-Id: I9271c6325b6d32d3150e53617851ef4f009084d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360218Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Alexander Surkov <asurkov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#799591}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/6a992541..b1eb63de

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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I9bac8c2d2464e07103f347fe6acf43a16bb20458
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362344Reviewed-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@{#799590}