GitLab

The Permission UI for getting location permission from mac is completely
separate from the actual Core Location backend. Furthermore, once we
have location permission from macOS our Network Location Provider works
as intended. This CL separates those 2 independent workflows and allows
the Network Location Provider to monitor permission and act accordingly.

Bug: 1112630
Change-Id: I4e3141f756eadcb3d7ecc66c347fc24148505edc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2454307
Commit-Queue: James Hollyer <jameshollyer@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821050}

The Chai dependency prohibits the util from being used in WebUI tests
that are not configured to use Chai, like the PDF Viewer's.

Change the assertion to be part of a condition. The assertion was
already strong and unlikely to fail.

Change-Id: I008a6b6ccb1cd8c83d3ec2dcea3476243e89cb0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495506
Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821049}

Context:

Per-AgentSchedulingGroup task runners should be used where appropriate.

What this CL does:

Use per-AgentSchedulingGroup task runners for RenderFrameImpl's mojo interfaces instead of per-thread task runners.

Bug: 1105403
Change-Id: I8bb485e6d1ca97cdbf9f5dd0f32719f1d0ad2202
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2498024Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Minoru Chikamune <chikamune@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821048}

WebLayer: add support for navigating to a URL when the data is already available in a WebResourceResponse.

Bug: 1117626
Change-Id: I6d3bd9f4ec71a5e16390f072182a76fe36aca4b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369617
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821047}

Generate DIR_METADATA files
and remove metadata from OWNERS files
for //content/public.

Bug: 1113033
Change-Id: I4fc946e09255a6d8971a375c1da169233db53ec8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2472420Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Norman Rosas <normando@google.com>
Cr-Commit-Position: refs/heads/master@{#821046}

This is setup work for enabling cross device sync for the read later
feature.

Bug: 1109316
Change-Id: I172633ba826b8f520aa6f25273bd530b38782257
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2492920Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Reviewed-by: Peter Boström <pbos@chromium.org>
Commit-Queue: Caroline Rising <corising@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821045}

Generate DIR_METADATA files
and remove metadata from OWNERS files
for //content/browser/resources.

Bug: 1113033
Change-Id: Ic84b891c4f67830b63e3dad1dde6f5cdd5f26429
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2472590Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Norman Rosas <normando@google.com>
Cr-Commit-Position: refs/heads/master@{#821044}

This patch implements alignment within a grid-item's grid-area.
When creating the GridItemData we read of the containers, and
grid-item's style, or determine its alignment axis-edge, and if it
should be stretched, saving this information on the GridItemData.

When placing the grid-item it will use this to adjust the offset.

This doesn't implement baseline alignment which requires a secondary
pass to correctly determine the baseline for the column/row.

The other TODO relates to the constraint-space API, and how grid will
need a slightly new concept in order to do block-axis stretching
easily. By default non-replaced grid-items will stretch to the available
space. A new bit on the space can indicate that we should stretch to
the available space (if possible), this is similar to the shrink-to-fit
bit we have today.

This adds a self-start/self-end test as after implementing this now new
tests passed immediately, and I don't believe we had good test
coverage for inflow content with these keywords.

Bug: 1045599
Change-Id: I8c9cc51381c3d75519e52b32472b58ec96a6a85a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2492176
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#821043}

Roll Chrome Linux PGO profile from chrome-linux-master-1603735176-b32fad2c4d9cbe478f3c31f23cbc72f28c88ba53.profdata to chrome-linux-master-1603756748-18fcc653ee73e42ac2d8e9952f1488ef428e6efa.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: Id7a2ec7c00e1a1c10058431e795cc300e14b4b57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500903Reviewed-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@{#821042}

This CL:
- Makes BuildConfigGenerator.groovy and fetch_all.py agree with the
expected directory of the generated DEPS file
- Fixes cipd_path computation in ParseDeps() in fetch_all.py

BUG=None

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

Adds an UnhandledKeyboardEventHandler member to the BubbleWebView
to allow the WebView and embedder to deal with key events that
were not handled by the WebContents.

Sets allow_accelerators_ to true to ensure that embedders of the
BubbleWebView are able to capture and respond to accelerators.

Bug: 1138967
Change-Id: Ib629de2dbb0f1b6e41f4116fcff6d1413fc3061c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2496504Reviewed-by: Peter Boström <pbos@chromium.org>
Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821040}

The QuotaClient interface now guarantees that clients only get called
with StorageTypes that they were registered for. In particular,
AppCacheQuotaClient is only called with kTemporary. This precondition
has been covered by a DCHECK for a while.

This CL removes a check that cannot be true under the current
QuotaClient interface.

Change-Id: I2057935df768f657f13a7f4297864ab62cc7ce1a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500767
Commit-Queue: Victor Costan <pwnall@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Auto-Submit: Victor Costan <pwnall@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821039}

Roll Chrome Mac PGO profile from chrome-mac-master-1603735176-39200681b7df83b17975b9debf912df318fc5920.profdata to chrome-mac-master-1603756748-67e6d78aa0117f6752ad92f968b3a41dbb1fa16d.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 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:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I08d06fa72160d4f6f8a9745bf99bb639a4e50846
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500902Reviewed-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@{#821038}

This change enables future UI changes based on the
'window-controls-overlay' display override by adding a new method,
`IsWindowControlsOverlayEnabled()`,to the web app controller that
indicates whether or not the WCO should be shown.

Explainer: https://github.com/WICG/window-controls-overlay/blob/master/explainer.md
Design Doc: https://docs.google.com/document/d/1k0YL_-VMLIfjYCgJ2v6cMvuUv2qMKg4BgLI2tJ4qtyo/edit?usp=sharing
I2P: https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/cper6nNLFRQ/hU91kfCWBQAJ

Bug: 937121
Change-Id: Ibe5615393e50edc09e2464abe9eaa09e52559be6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2486780Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Lorne Mitchell <lomitch@microsoft.com>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Commit-Queue: Amanda Baker <ambake@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#821037}

Parent CL has related mojo changes: crrev.com/c/2486525 .
Will need a separate CL to land for impl on Android side.
Explainer: https://github.com/WICG/digital-goods/blob/master/explainer.md#full-api-interface

Bug: 1140345
Change-Id: I06fa43dc79cf37b77edfe0c87817e697cbd1d4a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2497393Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Glen Robertson <glenrob@chromium.org>
Commit-Queue: Glen Robertson <glenrob@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821036}

This is the first cl in a set of CLs centred around moving navigation
order responsibility from launch.js to ReceivedFileList in receiver.js.

This cl does 3 things to set up ReceivedFile list to take over owning
open file functionality.
    * Loads a default file list into the media app on launch so we can
      have access to the openFile method regardless of if we were
      launched with files or not.
    * Moves the openFile function from clientAPIDelegate into
      receivedFileList.
    * Adds a currentFileIndex property. This is unused at the moment
      but needs to be on the api so observers can detect when the
      current file changes.

Once Google3 updates to use this openFile function and updates the
loaded file on a currentFile change, the old openFile code path can be
removed. Then the ReceivedFileList can be updated to no longer rely on
launch.js to do file navigation to the newly opened file but to do it
internally.

See go/bl-file-navigation-order for the full timeline for this effort.

Change-Id: Idbbddf1338b66d37917413e67767b54b9709a7a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2494181Reviewed-by: Trent Apted <tapted@chromium.org>
Commit-Queue: Zain Afzal <zafzal@google.com>
Cr-Commit-Position: refs/heads/master@{#821035}

This will help IME service show logs better from loaded ime decoder.

TEST=Betty with new built DSO.
BUG=b/162375823

Change-Id: I9a3fa61078dfeae5a029b912c339cd80bc724a8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2497352
Commit-Queue: Leo Zhang <googleo@chromium.org>
Reviewed-by: Keith Lee <keithlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821034}

After a successful payload transfer, BluetoothSocket::Close() will be
called multiple times (see crbug/1142071). In this CL, we check if the
underlying socket has already been disconnected and reset before trying
to disconnect and reset. Without this check, the Nearby process will
crash after a successful share.

Verified by manually testing Chromebook-->Android transfers.

Fixed: 1142071
Change-Id: I1b2fd0a092f1025f95c2eed5253862805e46b034
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500982
Commit-Queue: Josh Nohle <nohle@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Auto-Submit: Josh Nohle <nohle@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821033}

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

This reverts commit a2ecb05c.

Reason for revert: This is causing quality reductions compared to the software encoder. We will need to figure out a way to limit usage of the hardware encoder to higher bit rate situations. See https://crbug.com/1142273

Original change's description:
> Revert "Remove constrained baseline profile support for H264 in M86."
>
> This reverts commit 3234b57f.
>
> Reason for revert: AUD stripping patch from WebRTC has been rolled to Chromium: https://webrtc.googlesource.com/src/+/9345dcfeea73f9dd68dc83dee60255e86dac3f97 and https://source.chromium.org/chromium/chromium/src/+/76165ce5bf99790f8dbae685259723e867458337. CBP for H264 support can come back in.
>
> Original change's description:
> > Remove constrained baseline profile support for H264 in M86.
> >
> > Bug: 982799
> > Change-Id: Ibe20d74bfe6182b8464855106ca2d09f5dca087c
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363462
> > Commit-Queue: Chunbo Hua <chunbo.hua@intel.com>
> > Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
> > Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#799783}
>
> TBR=dalecurtis@chromium.org,chunbo.hua@intel.com
>
> # Not skipping CQ checks because original CL landed > 1 day ago.
>
> Bug: 982799
> Change-Id: Ib1c0212181d7efffe1cd4b82a0a1ddc9a603a0f3
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427573
> Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
> Commit-Queue: Chunbo Hua <chunbo.hua@intel.com>
> Cr-Commit-Position: refs/heads/master@{#811571}

TBR=dalecurtis@chromium.org,guidou@chromium.org,chunbo.hua@intel.com

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

Bug: 1142273
Change-Id: I29c06fcba297967bdac8dd188acb24c84c1053bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500446Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821031}

TBR=acolwell@chromium.org

Bug: 1089994
Change-Id: I290d0294499f620e30157ebcae3a68374fa46f68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500701Reviewed-by: Patrick Noland <pnoland@chromium.org>
Commit-Queue: Patrick Noland <pnoland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821030}

What: Remove blocklist service. The blocked status will be encoded in
the 7th bit in the sorting-lsh entries. Update the component format
version.

Why: This would save the overhead to check whether the versions match,
and would also save the component updater bandwidth.

Bug: 1138743
Change-Id: Id590d675efc0c5c54905564ad50cd64b88e21bb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2473547Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Commit-Queue: Yao Xiao <yaoxia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821029}

The test is modeled after Chrome's MediaRouterIntegrationTest. Other
test cases will be added soon.

The cast emulator service is moved from //chrome to //components. This
service (and an APK wrapping it) is necessary for the media route
chooser dialog to have entries in it. The selection of these entries
(creation of presentation, etc) is handled by MockMediaRouteProvider.

RouterTestUtils is also moved to //components/media_router. This
facilitates finding views in the chooser dialog.

Bug: 1057099
Change-Id: I0e8b67f3286b21bec5bc0f4581975fc1cca95b53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488088Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Clark DuVall <cduvall@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821028}

Change-Id: I557b2aa89ec0a737e1d5b315b3d06fe12148b778
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500271
Commit-Queue: Nate Chapin <japhet@chromium.org>
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Auto-Submit: Nate Chapin <japhet@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821027}

This is a reland of 0092862f

Original change's description:
> Reland "Mojo JS: Use BigInt consistently for 64-bit int fields"
>
> This is a reland of ea79bdd2
>
> Fix is in the delta from PS1 -> PS3
>
> Original change's description:
> > Mojo JS: Use BigInt consistently for 64-bit int fields
> >
> > This changes 64-bit integer fields to be deserialized as
> > BigInt values consistently, rather than sometimes being
> > BigInts and sometimes being Numbers.
> >
> > Fixed: 1102217,1009262
> > Change-Id: I9cc8d767058938e9c39f62f139737e512f47cdb2
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2466398
> > Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
> > Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
> > Reviewed-by: François Doray <fdoray@chromium.org>
> > Reviewed-by: Becca Hughes <beccahughes@chromium.org>
> > Reviewed-by: Shik Chen <shik@chromium.org>
> > Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
> > Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
> > Commit-Queue: Ken Rockot <rockot@google.com>
> > Cr-Commit-Position: refs/heads/master@{#818611}
>
> Change-Id: I393a33b44b1a3e1746f7b9ee021dbe06c3ff7b07
> Tbr: shik@chromium.org
> Tbr: fdoray@chromium.org
> Tbr: ryansturm@chromium.org
> Tbr: mahmadi@chromium.org
> Tbr: beccahughes@chromium.org
> Tbr: oksamyt@chromium.org
> Tbr: ortuno@chromium.org
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485749
> Reviewed-by: François Doray <fdoray@chromium.org>
> Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
> Reviewed-by: Dan H <harringtond@chromium.org>
> Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
> Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
> Reviewed-by: Becca Hughes <beccahughes@chromium.org>
> Commit-Queue: Ken Rockot <rockot@google.com>
> Auto-Submit: Ken Rockot <rockot@google.com>
> Cr-Commit-Position: refs/heads/master@{#819004}

NOPRESUBMIT=True

Change-Id: I51f628aa5898f66d26ff1d8c7ef3ade3d0f91045
Tbr: shik@chromium.org
Tbr: fdoray@chromium.org
Tbr: ryansturm@chromium.org
Tbr: mahmadi@chromium.org
Tbr: beccahughes@chromium.org
Tbr: oksamyt@chromium.org
Tbr: ortuno@chromium.org
Tbr: harringtond@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2489666
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Reviewed-by: Shik Chen <shik@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Dan H <harringtond@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Auto-Submit: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#821026}

This CL creates an exception to be reported by the error callback when
decoders encounter a error. The error is also logged as a message in the
DevTools media tab.

Bug: 1139089
Change-Id: Ib8f71505303cb7ff535928055df05163bc57c267
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2499422
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821025}

Introduces a concept of partially initialized HoldingSpaceItem - this
state will be used when loading items from persistent storage in case
the item file system URL cannot immediately be resolved (e.g. if the
associated mount point hasn't been loaded yet).
HoldingSpacePersistenceDelegate will deserialize persisted items into
partial state when they are first loaded from the storage, and
"finalize" them when their file system URL can be resolved.

Compared to an alternative approach where items whose initialization has
to be deferred, this approach keeps the order in which items are added
to the model.

Updates holding space UI not to show partially initialized items.

BUG=1140150

Change-Id: Ie19997ec02f6323434f4053f6ba41a2998e72efa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493323
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Reviewed-by: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#821024}

The MatchingPattern's negative pattern type from std::string to base::Optional<std::string> has been changed and the resulting changes have been made. This fixes that every pattern's negative pattern vacuously matched.

Bug: 1142579
Change-Id: Ida580b33e9a4f0f42accdfcce082aa428ad12275
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500221Reviewed-by: Christoph Schwering <schwering@google.com>
Commit-Queue: Christoph Schwering <schwering@google.com>
Commit-Queue: Mariia Shvedchenko <mariiash@google.com>
Cr-Commit-Position: refs/heads/master@{#821023}

This is not needed

Merge-With: eureka-internal/472392
Bug: NONE
Test: Locally on device
Change-Id: Ia64527d24c0fc7062cd9da8aa51c00d304d0fd6a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485277Reviewed-by: Sean Topping <seantopping@chromium.org>
Commit-Queue: Shawn Gallea <sagallea@google.com>
Cr-Commit-Position: refs/heads/master@{#821022}

Bug: 800764
Change-Id: I3a7afb3095b5f686664d5061cfe11dd906116980
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2484699
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821021}

It's a fixup for https://crrev.com/c/2426583. We've decided to have burunduk@
at the main histogram owner, but forgot to upload a patch for that.

Bug: None
Change-Id: I4cb2777e931376a2f9dbc7a2c28dc64618e0c03c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2498566
Auto-Submit: Oleg Davydov <burunduk@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821020}

We want to be able to identify and display price updates
in the Tab Grid Switcher. This change to the infrastructure
will provide us with the capability to do that.

Bug: 1139459
Change-Id: I7588b377bc1fd1532a67373835c4204201723fdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2481010Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Commit-Queue: David Maunder <davidjm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821019}

These messages were identified as occasionally exceeding the soft
message size limit. No functional changes here, only suppressions and
TODOs.

Bug: 1141980,1141985,1141987,1141990,1142000,1142008,1142011,1142013
Change-Id: Icd1a060b9bd082bfa204f44a3a12a43c8812c0fb
Fixed: 1142019
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495789
Commit-Queue: Ken Rockot <rockot@google.com>
Auto-Submit: Ken Rockot <rockot@google.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821018}

Bug: 1142645
Change-Id: I8c26e00a7239f2f37180ddbb37f52e92b9973bd8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2497433
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821017}

Blink impl: crrev.com/c/2497393
Explainer:
https://github.com/WICG/digital-goods/blob/master/explainer.md

Bug: 1140345
Change-Id: Idc6cfd23abcdf1ce696ed26d54804912304108bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2486525
Commit-Queue: Glen Robertson <glenrob@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821016}

The blink-dev thread for deprecation is here:
https://groups.google.com/a/chromium.org/g/blink-dev/c/7XWZ-J7HZHw

Bug: webrtc:6625
Change-Id: I10b1f320a7b82fd75d184c487ef3afb18888533a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2289831Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821015}

CookieStore.

Change-Id: If6a77b1d8e71e9187f72735acaba6845b2de6b90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2498132
Commit-Queue: Chris Fredrickson <cfredric@google.com>
Reviewed-by: Eric Orth <ericorth@chromium.org>
Auto-Submit: Chris Fredrickson <cfredric@google.com>
Cr-Commit-Position: refs/heads/master@{#821014}

Split off of
https://chromium-review.googlesource.com/c/chromium/src/+/2442359 as
these fixes will be useful even when that CL gets inevitably reverted :)

Espresso wraps and re-throws Exceptions, so we catch Exceptions whose
cause is a CriteriaNotSatisfiedException as well so that the polling
actually works when using Espresso to check Criteria.

Bug: 1134178
Change-Id: I7c9cdb7e637b306b0c6cb9ecb42a237d99091cb8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491117Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821013}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/c54539538ed6..77cd4b459b10

2020-10-26 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@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: ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com
Change-Id: I85727b4f538d190fc3a8e35eb80f728121e3b371
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500249Reviewed-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@{#821012}

Bug: 1137468
Change-Id: I7380b5e1de6cd1af7b7c9577c1972003c4d99384
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500443Reviewed-by: Wenbin Zhang <wenbinzhang@google.com>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821011}