GitLab

Split the report.body.type:

From:
  access-to-coop-page
  access-from-coop-page

To:
  access-from-coop-page-to-opener
  access-from-coop-page-to-openee
  access-from-coop-page-to-other
  access-to-coop-page-from-opener
  access-to-coop-page-from-openee
  access-to-coop-page-from-other

to match with the new specification updates.

Bug: 1090273
Change-Id: Ia8b9af6b2751ba5154f1c56793d01542cd736bad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2356404Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800157}

When a credential from the list changes (is added in a new check or
removed) the entire list has to change. However, in order to keep the UI
stable, the list should maintain its order, which has to be as follows:

1. Phished credentials appear before leaked credentials.
2. Compromised credentials found in previous checks should appear
in descending order of creation time (most recent first).
3. Compromised credentials found in the current check (and all checks
ran while the list UI is open) have to be appended to the list.
This means that they need to be ordered in ascending order of creation
time.

Bug: 1102025, 1092444
Change-Id: I9e262791227454065fd556c0974b12b43fc9843a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362609
Commit-Queue: Ioana Pandele <ioanap@chromium.org>
Reviewed-by: Friedrich [CET] <fhorschig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800156}

Add 2 histograms which exposes last packet sent time delta and connection duration when receiving PUBLIC_RESET.

R=dschinazi@chromium.org

Change-Id: I75ae9c95b13273ef1421b28113e11c5dd63bc59e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366913
Commit-Queue: David Schinazi <dschinazi@chromium.org>
Reviewed-by: David Schinazi <dschinazi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800155}

There are other devices now.

Fixed: 1119603
Change-Id: I8ea42abcfe4d98397a02b8975ce89d4d30489e2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366312
Auto-Submit: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Fergus Dall <sidereal@google.com>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800154}

Fix this error in GCC compilation:
../../third_party/blink/renderer/platform/heap/member.h:251:13: error: explicit specialization in non-namespace scope ‘class blink::MemberBase<T, tracenessConfiguration>’
  251 |   template <>
      |             ^
../../third_party/blink/renderer/platform/heap/member.h:252:76: error: template-id ‘SetRaw<blink::TracenessMemberConfiguration::kUntraced>’ in declaration of primary template
  252 |   ALWAYS_INLINE void SetRaw<TracenessMemberConfiguration::kUntraced>(T* raw) {

To avoid it we change SetRaw to not be a template method, and just check
the traceness configuration. The generated code should be the same.

Bug: 819294
Change-Id: Ia03d7842918bd091beaf966caa3af5e8c647cd76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360020Reviewed-by: Anton Bikineev <bikineev@chromium.org>
Commit-Queue: José Dapena Paz <jdapena@igalia.com>
Cr-Commit-Position: refs/heads/master@{#800153}

This changes site metadata checks for subresource filter activation
to check for a site activation key in the metadata dictionary.
If the dictionary or key does not exist we default to existing
behavior: using the presence of metadata as a signal for subresource
filter activation. Otherwise we use the activation status stored in
the dict.

This enables using the ADS_DATA metadata to persist other ads
related information for a limited duration (currently 7 days).
As persisting metadata in website settings comes with a performance
cost, this should only be applied to a very small subset of sites.
The followup change which uses this API only applies it to sites
with ads violations.

BUG=1099741

Change-Id: I02dac29dd717afadec373114fcaab45bc3e678c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283662Reviewed-by: Kamila Hasanbega <hkamila@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Robbie McElrath <rmcelrath@chromium.org>
Reviewed-by: Theodore Olsauskas-Warren <sauski@google.com>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Commit-Queue: Justin Miron <justinmiron@google.com>
Cr-Commit-Position: refs/heads/master@{#800152}

Bug: 973801
Change-Id: I047c76f8fd782dc7dce5486597b73fa5941c4bd5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363400Reviewed-by: Ian Clelland <iclelland@chromium.org>
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800151}

This adds new UKM metrics as described in the design doc for the launch
crbug.com/1110887.

This CL also adds a JNI bridge for FieldTrialList::CreateFieldTrial.

Bug: b/162224259
Change-Id: Ic432fbc4501dd7364c2eb35137d70b958c85ca66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2356006Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Mathias Carlen <mcarlen@chromium.org>
Commit-Queue: Clemens Arbesser <arbesser@google.com>
Cr-Commit-Position: refs/heads/master@{#800150}

Its purpose is to avoid creating spurious history entries in the case
where we replace the initial empty document with a different
about:blank document (which the spec says not to do, but I think every
major browser does). Explicitly track this case with a bit on
FrameLoader for whether we've ever loaded a non-empty document.

Change-Id: I2bd6d759ccf6f43d14feddeac1f72d2f871a80cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354995Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800149}

Cue-related events (enter, exit, cuechange) are fired up to 250ms late,
and there is a similar latency in their display which is quite
noticeable.

The underlying problem is that we only update cues alongside the
`timeupdate` event, which is fixed at 4 Hz.

My solution is to add a separate timer to CueTimeline
(`CueTimeline::cue_event_timer_`) which is given a timeout for the
next cue event based on the current playback position and rate. This
allows for significantly more precise cue timing accuracy without a
significant performance penalty.

Additionally, several web tests were written with the expectation that
the 'time marches on' algorithm is run before video playback begins
(ie, upon loading text track cues). This behavior is not in accordance
with the spec (as outlined in crbug/1050767), so this CL fixes those
expectations and adds a new test to prevent regressing.

Bug: 576310, 1050767
Change-Id: I675f5f030a68ba9cee10e12b3e79a9b174048193
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008079
Commit-Queue: Will Cassella <cassew@google.com>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#800148}

This change moves one method UpdateSurfaceAndScreenInfo into WidgetBase.
Some intermediate methods needed to be added since some of the code
path is still in RenderWidget.

The big part of this change is that ScreenInfo is now stored on the
WidgetBase.

BUG=1097816

Change-Id: Ie4f19f8bc80d800ee58378682fd059628f1c9fe5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354513
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Cait Phillips <caitkp@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800147}

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: Id83ba088026d563ceaaf84329fad31ab6e98693d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366283Reviewed-by: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#800146}

Bug: 973801
Change-Id: I9f379f98df5e6d0ffc232b395a31758206c24901
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365133Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800145}

AppService is used to load icons for windows. AppService uses async
mojom. So it might be not very appropriate to test with update number
when we have the custom icon, because if the icon is updated fast from
AppService, then it might be updated 4 times, however if slow, then
there are 3 updates only, becuase it has got the customer icon, and the
icon update from AppService could be skipped.

Modify the test case LauncherPlatformAppBrowserTest.SetIcon to check
the final image. If the custom icon is set, check the window's icon is
set as the custom icon.

BUG=1115533

Change-Id: Ief034842fef9360a49a504effb54cf51c8d4c51a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364156Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Nancy Wang <nancylingwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800144}

Show managed UI when SafeBrowsingEnabled policy is set by enterprise.

Bug: 1119647
Change-Id: Ia6ccb0af0d61964867dec60be0f901040553af22
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366002Reviewed-by: Sergio Collazos <sczs@chromium.org>
Commit-Queue: Tina Wang <tinazwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800143}

The test: conformance/glsl/bugs/bool-type-cast-bug-int-float.html
is passing now.

Bug: chromium:905007
Change-Id: I754cfd896da07d516cb6adeb0a2090f377ede470
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364513Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>
Cr-Commit-Position: refs/heads/master@{#800142}

These two tests pass.

Bug: chromium:1099979
Change-Id: I76b553918990e3a4d768c93888a9990391237dee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363808Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>
Cr-Commit-Position: refs/heads/master@{#800141}

Trust Tokens is a new Chrome feature that adds origin-scoped state and
operations, associated with outgoing resource requests, that can mutate
this state. In order to avoid certain denial-of-service attacks,
executing two of the three Trust Tokens operations requires the
trust-token-redemption Feature Policy feature in the executing context.
To verify that this holds for outgoing subresource requests, we bind to
each frame-level URLLoaderFactory an "upper bound" on whether the frame
has the Feature Policy feature present. This state has two values,
"forbid" and "potentially permit". In theory, if it is "forbid," we know
for sure that we should not see these restricted Trust Tokens operations
from the frame, and, if a renderer initiaties a restricted Trust Tokens
request from such a frame, we kill the renderer because we "know" that
it is misbehaving.

We recently encountered a synchronization issue (crbug.com/1111735)
where the browser process's view of a frame's Trust Tokens state became
inconsistent with well-behaved renderers' views, leading to erroneous
renderer kills. It seems like a similar issue might be occurring with
the CorsURLLoaderFactory Feature Policy check. This change disables the
renderer kill in question as a stopgap to halt the erroneous crashes (we
believe almost all such crashes are false positives) and instead logs a
histogram and records a DumpWithoutCrashing.

R=csharrison

Bug: 1117458
Change-Id: Icb1aac4e9d5812fe8d11467f4884c1d4218cb002
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363851
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800140}

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll
Please CC cr-fuchsia+bot@chromium.org 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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
Tbr: cr-fuchsia+bot@chromium.org
Change-Id: I256f424e774d7c609ef8b147c9fb049e966a57e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367172Reviewed-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@{#800139}

Lite scripts should never show the overlay. This is achieved in two
steps:

- Auto-insert a ConfigureUiState action as the first action to run.
- Blacklist ConfigureUiState, such that scripts can't override this.

Bug: b/164506953
Change-Id: Ibce93307e2f8fd3ef15bb1aeb0b2e338b0e48457
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362822Reviewed-by: Mathias Carlen <mcarlen@chromium.org>
Commit-Queue: Clemens Arbesser <arbesser@google.com>
Cr-Commit-Position: refs/heads/master@{#800138}

This change adds timestamp of the last password check. Timestamp is
visible only during unsafe state.

Bug: 1075494
Change-Id: I8e1bf94b27a94bbc1cbb83736fd4cd3f7344889f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2332605
Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800137}

We should not dismiss the viewController when opening in a new Window.

Bug: 1119762
Change-Id: I3520dbbaaa4123f564df28e1636aa52e180dd025
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365978
Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org>
Commit-Queue: Mark Cogan <marq@chromium.org>
Auto-Submit: Sebastien Lalancette <seblalancette@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800136}

https://webrtc.googlesource.com/src.git/+log/eeedb6ea3337..93a9d19d4eb5

2020-08-20 jonaso@webrtc.org p2p_transport_channel: Add estimated disconnected time to CandidatePairChangeEvent
2020-08-20 handellm@webrtc.org Linux ADMs: fix recursive mutex locks.
2020-08-20 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 9fa04bfc..7a8fca54 (799612:800031)
2020-08-20 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 75c4e773..9fa04bfc (799488:799612)
2020-08-19 orphis@webrtc.org Don't do legacy conference mode temporal layer allocation on non-screenshare

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

During processing conflict the local entity might be deleted, e.g. when
there is a remote update upon local tombstone.

Bug: 1093024
Change-Id: I29341f26b000771a012cbe23f0373e9cb8c00802
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366742Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Rushan Suleymanov <rushans@google.com>
Cr-Commit-Position: refs/heads/master@{#800134}

Add a new component for oobe. The slides can be used for scrolling.
Contains title, body text and illustration.

Bug: 1117161
Change-Id: If583db26a82d108a96c33c71616b2e01d38180e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362812
Commit-Queue: Danila Kuzmin <dkuzmin@google.com>
Reviewed-by: Roman Aleksandrov <raleksandrov@google.com>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800133}

This CL updates the integration test to use fake static to override the
sharesheet apis in the files app.

BUG=1097623

Change-Id: I37c6238bce7a1e0f401d725cab819b9e81d001c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359791
Commit-Queue: Maggie Cai <mxcai@chromium.org>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800132}

Need to pass version_code to the android_app_bundle() target.

Bug: 1119488
Change-Id: I6a5c0501b54b2acc45bf7ac40c427aabf7f0891a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363669Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800131}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/1e53cb87ed5e..b36c2d9991f1

2020-08-20 tvanderlippe@chromium.org Revert "Remove Properties subpane from Elements panel"
2020-08-20 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS.
2020-08-20 tvanderlippe@chromium.org Typecheck console/ConsoleView.js with TypeScript

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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: chromium:1011811
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I73bc93aca1caf85d968b642524e9188e8b800c96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366676Reviewed-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@{#800130}

13.6 sdk is not found for the current xcode version.
reverting it to 13.4 to unblock CLs from landing.

Bug: 1119668
Change-Id: I10b3259860d04101dbeb65f81657c08028cecce4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366562
Auto-Submit: Jeff Yoon <jeffyoon@chromium.org>
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800129}

Add espresso tests for HomeFragment to test:
- Correct info is shown when the app is launched from the current
  WebView provider and when it's not.
- Long press on the items copy the correct info to clipboard.

Bug: 1106300
Test: out/Debug86/bin/run_webview_instrumentation_test_apk -f "*android_webview.devui*"
Change-Id: I63bab2647e65b758e4b14838d1ba34edd54a064a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352738
Commit-Queue: Hazem Ashmawy <hazems@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800128}

chrome/services/sharing/*
- Introduced PayloadListener::GetFileForPayload for requesting
  file from browser process based on payload_id
- Introduced PayloadListener::OnPayloadReceived for passing incoming
  payload

chrome/browser/nearby_sharing/nearby_connections_manager*
- Browser side usage of the above APIs
  NearbyConnectionsManager stores the payload in a map, and can be
  retrieved via GetIncomingPayload
- NearbyConnectionsManager provides API to register base::FilePath for
  specific payload_id. payload_id are sent via Nearby Share specific
  introduction frames from NearbyDecoder.

Bug: 1076008
Change-Id: I177986dba2a66805085539d2b30a282ec948cf43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352792Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Richard Knoll <knollr@chromium.org>
Reviewed-by: Himanshu Jaju <himanshujaju@chromium.org>
Commit-Queue: Alex Chau <alexchau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800127}

1. A simple container on the main layout for locating a message
2. The basic message mvc components(properties and viewbinder)
3. A simple render test for the mvc

Bug: 1111911
Change-Id: Id6830571995d9c2696283a7eb4128c469a8c4462
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2331638Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Commit-Queue: Lijin Shen <lazzzis@google.com>
Cr-Commit-Position: refs/heads/master@{#800126}

This adds Get/GetOrCreate methods for ShareTargetInfo so we don't
accidentally create entries in the maps. Only a few places actually
need to create a new entry and this makes it easier to track those.

Bug: 1085067
Change-Id: I3d9f20a9a371a0af3968a485748d611840e299b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353334Reviewed-by: Himanshu Jaju <himanshujaju@chromium.org>
Commit-Queue: Richard Knoll <knollr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800125}

Cache SurfaceControls for the lifetime of SurfaceView. This is to avoid
creating/destroying a surface each time the video scrolls off the screen.

Bug: 1102623
Change-Id: Idb02923e6d71109be983ea879f4c8b7fa23121f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360488
Commit-Queue: vikas soni <vikassoni@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800124}

This will allow TWAs to determine whether a browser supports launching
to site settings without having to hard code Chrome's package and
version.

Change-Id: I37b226be1a5118b38f10acb4edefce89db3ad973
Bug: 1119727
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366934
Commit-Queue: Peter Conn <peconn@chromium.org>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800123}

Bug: 1119674
Change-Id: I41c282796aed83d17565fd27349dcddcd6b0db72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366394Reviewed-by: Wenyu Fu <wenyufu@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800122}

This change shows new Password Details screen from Passwords screen  in
the scope of Password Check feature.

Bug: 1075494
Change-Id: Ic103bce25166beae8eff42b5c3281ace39d1b965
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359130
Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800121}

Bug: 1116942
Change-Id: Id2e05b209c5de82a83402d2eb28a85231424c4e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364169
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800120}

Bug: 1116201
Change-Id: Ib4664f4dcc78380da556cb89e2ad4c544e4de312
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366572
Commit-Queue: Theresa  <twellington@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800119}

Bug: 1070620
Change-Id: I27b0b8097b73dc92d5ee9cbcaba26233e7ff50db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362653
Commit-Queue: Andrey Zaytsev <andzaytsev@google.com>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Auto-Submit: Andrey Zaytsev <andzaytsev@google.com>
Cr-Commit-Position: refs/heads/master@{#800118}