GitLab

Bug: None
Change-Id: Ibbf4d41ff940c785b3c14965063f6258d183cedf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506183
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Commit-Queue: Friedrich [CET] <fhorschig@chromium.org>
Auto-Submit: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Friedrich [CET] <fhorschig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822203}

This reverts commit d655a4cc.

Reason for revert: KeyPermissionManagerBrowserTests broken on linux-chromeos-rel : https://bugs.chromium.org/p/chromium/issues/detail?id=1143713

Original change's description:
> KeyPermissions: Add key permissions manager
>
> This CL introduces KeyPermissionsManager (KPM). KPMs are responsible for
> managing platform keys permissions by reading and writing permissions
> into chaps keys' attributes.
>
> Bug: 1113115, 1127284, 1082459
> Change-Id: I5d242604fe784566d086d2012313f77ca0fdbc44
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435386
> Commit-Queue: Omar Morsi <omorsi@google.com>
> Reviewed-by: Dominic Battré <battre@chromium.org>
> Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
> Reviewed-by: Edman Anjos <edman@chromium.org>
> Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
> Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
> Reviewed-by: Pavol Marko <pmarko@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#822131}

TBR=stevenjb@chromium.org,battre@chromium.org,asvitkine@chromium.org,emaxx@chromium.org,pmarko@chromium.org,edman@chromium.org,omorsi@google.com

Change-Id: I1a4bf6572bdfaf56701aaa8c66e9515a85be32ee
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1113115
Bug: 1127284
Bug: 1082459
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507465Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Reviewed-by: Omar Morsi <omorsi@google.com>
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822202}

Since cl/337200290, the Nearby Share server returns both Google contacts
and device contacts in the ListContactPeople RPC response. That update
labels every contact with a Google-, device-, or unknown-contact type.
The burden is on the client to filter by type if desired.

We update the proto here, but do not make use of the new contact type
field.

Bug: 1143680
Change-Id: Icae01e5066f89debe80ea7e66bb5ebd022cae0ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507452
Auto-Submit: Josh Nohle <nohle@chromium.org>
Commit-Queue: James Vecore <vecore@google.com>
Reviewed-by: James Vecore <vecore@google.com>
Cr-Commit-Position: refs/heads/master@{#822201}

This allows SubresourceFilterAgent::GetInheritedActivationState() to
avoid unnecessary conversions to url::Origin.

Bug: 1134740
Change-Id: I74d15db49de14d7e9b6017fb131d2976b727edc8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495923Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822200}

The new setting allows admins to "force pin" an extension to the
toolbar next to the Omnibar, so it always shows the extension icon. The
user cannot unpin it.

This doesn't include any UI changes, so the "Unpin" icon in the
extensions menu is still "interactible", i.e. it will show hover
effects and a ripple for now. It doesn't actually unpin the extension
when you click on it.

PRD: http://go/cbe-extensions-menu-pinning

TEST=Set the policy to pin an extension, then installed it. Verified
     that clicking the "Unpin" button doesn't unpin the extension

Bug: 1071314
Change-Id: I24c8e542b36375e3caf18eec356c5fedc055d3ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424838Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Weilun Shi <sweilun@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822199}

Bug: None
Change-Id: Ie1dffb756ad1c391f728abe5a55f3ce5b5d0ae4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505553Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Solomon Kinard <solomonkinard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822198}

Bug: 11297512
Change-Id: I9283feaa8578df3cfd749831e9d48c9151fe9c71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505986
Auto-Submit: Anton Bikineev <bikineev@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822197}

List of passed tests should be parsed for interrupted builds. However,
crrev/c/2473499 interpreted interrupted builds as "not started" and thus
made it not parsing the list, causing unnecessary retries.

.xcresult folder should not be used as indicator that tests didn't start
because it's created at the end of tests. output_path should serve the
purpose because it's created at the beginning of tests.

Bug: None
Change-Id: Icce037c12383e86356a6bdcc95188d22f97bc0b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505757Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822196}

This also converts the recorded enum to be a scoped enum, which allows:

- clang to enforce kMaxValue correctness
- autodeduction of the max value by UMA_HISTOGRAM_ENUMERATION.

Bug: 742517, 1047547
Change-Id: Ib8acb900fd919945e220bae7f674ea57df062c86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506245
Auto-Submit: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822195}

Bug: 1140063
Change-Id: I75ed31301df82036f1f9d6b59f642c54d3d38071
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506557Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822194}

Bug: 1096986
Change-Id: Ic4d55f8b041a09db22baea5ae49a0d5c3afe78d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505753Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com>
Cr-Commit-Position: refs/heads/master@{#822193}

Bug: 1108692
Change-Id: I475a0123987f69ab4ba749d8bf7bf775033b3ab4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2502612Reviewed-by: Milica Selakovic <selakovic@google.com>
Commit-Queue: Maxim Kolosovskiy  <kolos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822192}

This is a code health CL, it doesn't change behavior.

We are moving the NativePaintWorklet paint off the main thread, which
is captured in this CL:
https://chromium-review.googlesource.com/c/chromium/src/+/2466140

As part of it, we are creating a NativePaintWorkletInput, and it
would share some common bits with the CSS version. So this CL
splits the blink::PaintWorkletInput into two classes:
1. The base class that contains the common bits.
2. A CSSPaintWorkletInput that is specifically for the CSS paint.

Bug: 1139004
Change-Id: Id6d814a0f1e479f6895897e458b3d0995b80d0ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506078Reviewed-by: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822191}

INVALID: gn gen --args="... target_cpu=arm64"
VALID: gn gen --args="... target_cpu=\"arm64\"'

Bug: None
Change-Id: Ib3db48c4909573994866b2b361e5a8a5323283ee
Test: None
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506373
Auto-Submit: Aidan Wolter <awolter@chromium.org>
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822190}

This reverts commit b344652b.
Reason for revert: We have collected enough crashdumps now, and this is
causing crash metrics to be skewed as it's getting counted as a real
crash.

Bug: 1132770
Change-Id: Ia2e7a92bea2ebeca01c62ca9af73d3fe014685f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505985
Auto-Submit: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822189}

Change-Id: I9bf7d0b0f5cbd33ded4ff55bd3b11bdf3c380376
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507509Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822188}

StateNameMapUpdater is a helper class for StateNameMapUpdater
that reads the data from the state data files and loads them to the
map.

Bug: 1111960
Change-Id: I8add7215a1ec450e0a31ef999b2adfa6dade138b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2471337Reviewed-by: Matthias Körber <koerber@google.com>
Reviewed-by: Dominic Battré <battre@chromium.org>
Commit-Queue: Vidhan Jain <vidhanj@google.com>
Cr-Commit-Position: refs/heads/master@{#822187}

This test generates GL errors in ANGLE and flakes very frequently.
This was exposed after ANGLE started looking for errors in
https://chromium-review.googlesource.com/c/angle/angle/+/2134424

TBR=zmo@chromium.org
NOTRY=true

Bug: angleproject:3020
Bug: angleproject:5213
Change-Id: Id5f9407c0b819abcf7d150af3104a1a2e7ae6f06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507571Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822186}

The filename and class name should match, so the files were renamed to
service_delegate.h and service_delegate.mm.

Change-Id: Ib268c39ff7197002f56dfa637ddf81d237326132
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507749Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Mohamed Adel <adelm@google.com>
Cr-Commit-Position: refs/heads/master@{#822185}

PhoneHub will now show a max of two most recently visited tabs instead
of four.

Screenshot:
https://screenshot.googleplex.com/4CoC5BrWf4FXAY7

Fixed: 1142981
Bug: 1106937
Change-Id: I12a54bd92512dd8fb86722be6551ea6284e7badb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2504009
Commit-Queue: Regan Hsu <hsuregan@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822184}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/74cd21ef..35582ccb

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

Change-Id: I09f4847df30ab8dab5aebffc49152c4f40cc2196
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507458
Commit-Queue: Tina Wang <tinazwang@chromium.org>
Commit-Queue: sebsg <sebsg@chromium.org>
Reviewed-by: sebsg <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822182}

On clang rolls, the tidy trybot fails with

  Failed to download prebuilt clang package clang-llvmorg-12-init-10002-ga998cae0-1.tgz

since that hasn't been built yet at the start of the run.

Ideally we'd have a way to say "don't run clang-tidy automatically,
but do include it as a bot when running this through cq", but for now
just skipping all tricium steps altogether seems ok. For roll CLs that
get close to landing, we can try to remember to remove the line after
packages have been pushed.

Change-Id: I07fb68b872e9a05565967929f81b67e9ea707e61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505933
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822181}

This reverts commit 8815d0ef.

Reason for revert: Likely cause of "Deterministic Android" failures


Original change's description:
> Reland "Enable JDK library desugaring by default"
>
> This is a reland of 8699ff59
>
> Original change's description:
> > Enable JDK library desugaring by default
> >
> > Bug: 1056751
> > Change-Id: Id517413e180ad7cc2f7688d47038587f2a3ecb5e
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2458853
> > Reviewed-by: Andrew Grieve <agrieve@chromium.org>
> > Commit-Queue: Ian Wells <iwells@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#817575}
>
> Bug: 1056751
> Change-Id: I7d6f7336057afd80960d3b6c6a37c595b7c84629
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493362
> Reviewed-by: Andrew Grieve <agrieve@chromium.org>
> Commit-Queue: Ian Wells <iwells@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#820353}

TBR=agrieve@chromium.org,iwells@chromium.org

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

Bug: 1056751, 1142478
Change-Id: I6dd83fd6888ada2ac3ec350eed3345062080e2b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507490Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822180}

For rational numbers this worked OK by chance when both the nominator and
the denominator were < 65536, because the error was cancelled by the
division. However, this doesn't work when the nominator/denominator are
larger than 65535.

Fixed the offset, and added a test with large nom/denom.

Bug: 1143645
Change-Id: Ic8e46c580437fb4585197807c89a48f43435852a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507110Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822179}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d7b7cafac212..b6d93e6c4293

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 parastoog@google.com,futhark@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-chromeos-chrome
Bug: chromium:1018739,chromium:1143646
Tbr: parastoog@google.com,futhark@google.com
Change-Id: Iddcdecf63f1384d38cc447af62f6563183814258
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507103Reviewed-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@{#822178}

https://dawn.googlesource.com/tint.git/+log/d2fa57d26dff..62bbc6f6c050

2020-10-29 dsinclair@chromium.org Fix doc tables

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/tint-chromium-autoroll
Please CC rharrison@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: rharrison@google.com
Change-Id: I3fe30e1d973fe478483c2f08260214af05fe9930
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507102Reviewed-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@{#822177}

Two old Histograms are coming up on expiry, and we haven't used them in
a long time. So I'm marking them Oboslete now:
  Compositing.SurfaceDependencyDeadline.Duration*
  Compositing.SurfaceManager.AliveSurfaces*

Bug: 1140020, 1140021
Change-Id: Ibbfd90c72edb2a206cf114b77682116061c613b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505965Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Auto-Submit: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822176}

In RTL case, the coordinate system is from right to left and the origin is the right upper corner. The coordinates for everything on the lock screen should be the same in both LTR and RTL cases and therefor mirroring is not needed.

The misplacement is due to doing mirroring in `ConvertPointToTarget` when finding the position of the bubble. We need to remove the mirroring effect in order to find the correct position for login bubble.

Bug: 937245
Change-Id: I4c4ce54ab7617a5c4c56e861afb7a103b045ef8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505869
Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org>
Reviewed-by: Roman Aleksandrov <raleksandrov@google.com>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822175}

Study.

Bug: 973801, 1137081
Change-Id: Ieab55af5ac66aa23f2e3c2392e80da6c80404507
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2492601
Auto-Submit: Chris Fredrickson <cfredric@google.com>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822174}

Rather than passing three bools, pass a SVGContainerLayoutInfo struct as
argument. Makes some of the callsites slightly more readable.

Change-Id: Ic71bb7d863de047bf8e20dfec02e30fee02a8d87
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505754Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#822173}

Bug: 1052476
Change-Id: I0c8a0280fe121b82e17e602098732895ac9100f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507451Reviewed-by: Eric Orth <ericorth@chromium.org>
Commit-Queue: Dan McArdle <dmcardle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822172}

Bug: 1136043
Change-Id: Icb3d8aa472ec1f6fb932369ce7e80ba69470fedd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506044
Auto-Submit: sebsg <sebsg@chromium.org>
Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org>
Reviewed-by: Sebastien Lalancette <seblalancette@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822171}

Profiles that are scheduled for deletion cannot be used to create new
browser windows.

Bug: 1141551, 1125474
Change-Id: I0239b4b51c09be7dc0ff2c3189972dfa75a2ca00
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2497446
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822170}

Bug: 1112385
Change-Id: Id75f093fde39d3abf1fc06481771015c5062eda0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506351Reviewed-by: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Auto-Submit: Tomasz Wiszkowski <ender@google.com>
Commit-Queue: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822169}

URLs which are secure contexts can use the origin isolation feature,
even if they're not HTTPS. The most important example of this is
http://localhost.

Fixed: 1142894
Change-Id: I0c8d1c73465c2c289ae2996695f0c42f78cf100c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503849Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822168}

Change-Id: I4134461984fff33f9e6470cb7b4982ba51802dab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505581Reviewed-by: Caleb Raitto <caraitto@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822167}

The purpose of this subclass is to move all specific API calls to their
appropriate subclass. This is being done as UNUserNotificationCenter is
going to be added to the XPC service so it needs to be able to support
both.

Bug: 1142497
Change-Id: I123fc0144f507c18ca30ae66c75129ab1410b7a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2498594Reviewed-by: Richard Knoll <knollr@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Mohamed Adel <adelm@google.com>
Cr-Commit-Position: refs/heads/master@{#822166}

needed in preparation to moving the chime DFM definition downstream.
followup cl downstream crrev.com/i/3364724

Bug: 1142775
Change-Id: I2b07234fdba5dc2fa49632d5710f5ebedf48439f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2501667
Commit-Queue: Mohamed Heikal <mheikal@chromium.org>
Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822165}

This reverts commit cca7402b.

Reason for revert: This made the FuchsiaCdmManager tests flaky. See crbug.com/1143067

Original change's description:
> [Fuchsia] Move CDM data file i/o off main thread
>
> The FuchsiaCdmManager needs to create directories for each origin to
> pass to the platform CDM services to fulfill EME origin isolation
> requirements. The FuchsiaCdmManager runs on the main thread and the
> calls to CreateDirectoryAndGetError are potentially blocking. This CL
> moves the directory creation step to a background task.
>
> Bug: 1140655
> Change-Id: I060edc909976e7b5a493afc3bc9a2a26e26994be
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500532
> Reviewed-by: Wez <wez@chromium.org>
> Commit-Queue: RJ Ascani <rjascani@google.com>
> Cr-Commit-Position: refs/heads/master@{#821353}

TBR=wez@chromium.org,rjascani@google.com

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

Bug: 1140655, 1143067
Change-Id: I06955764f82f32f3aa96443f91ffd566aede3b91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505977Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Auto-Submit: RJ Ascani <rjascani@google.com>
Cr-Commit-Position: refs/heads/master@{#822164}