GitLab

Use non-deprecated ParseJson instead, which directly returns
base::Value anyhow.

Bug: 932873
Change-Id: I56c017db0dc8f902284d51a00b95e45509f4a07f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107367Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751423}

The text selection popup menu on Android is hidden while the user is
scrolling the page. It does this by listening to changes in the
GestureListenerManager which tracks the current state of scroll and zoom
on a page.

However, a page only has a single GestureListenerManager, owned by the
top level RenderWidgetHostView(Android). Unfortunately, it seems like
OOPIFs were never connected to it so the GestureListenerManager is
completely unaware of scrolling within isolated subframes.

This CL adds the plumbing to have child frames notify the root widget's
GestureListenerManager about the state of any gestures inside them. We
also remove the fling condition from IsScrollInProgress. This was
necessary in the past where a GestureFlingStart was sent to the renderer
after a GestureScrollEnd. However, today, a gesture sequence is entirely
framed by a GestureScrollBegin and GestureScrollEnd so we need only
listen for these events.

Bug: 977215
Change-Id: Ie33245c569c0ce1f6896c1889fcedd6ca31fe2c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101986
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751422}

This CL modifies PerformanceManagerImpl::DeleteNode() and
PerformanceManagerImpl::BatchDeleteNodes() so that the nodes are no
longer deleted if the task posted to the PM sequence is never run.

This is necessary to ensure the invariant of the graph are still held
during shutdown. At destruction, some nodes DCHECKs that their
properties are valid according to the invariant of the graph. If the
PM task runner has stopped executing its tasks, then those DCHECKs may
spuriously fail because a dependent task was not run.

This CL also fixes a lint warning by upgrading a loop to a range-based
for loop.

Bug: 1058705
Change-Id: I835c5aac5cfc9a12d52818e806ec5ba978af261c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106567Reviewed-by: Sigurður Ásgeirsson <siggi@chromium.org>
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751421}

These were both marked flaky in 2013. They pass locally, so let's try
re-enabling them and seeing if they still flake.

Bug: 85930
Change-Id: I6abe61923c8eb54360ae4ef5d93f08351262bd7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108627Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751420}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d390847cf65f..38a7906eeb00


Created with:
  gclient setdep -r src-internal@38a7906eeb00

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 jbudorick@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/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: jbudorick@google.com
Change-Id: Ie8ba1a82e0a9887601d964ec5ec379c4c54a6800
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108663Reviewed-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@{#751419}

Create a set of interpation tests for transforms which read the true
computed value (as opposed to the resolved value returned by
getComputedStyle() which differs drastically in the case of transforms,
see https://drafts.csswg.org/css-transforms/#transform-property).
As there is currently no universal way to get this value,
each test comes in 3 versions:

Two variants using computedStyleMap().get().toString() which is
supported by chrome. These also have duplicate versions where the zoom
property is set as it currently triggers some transform serialization
bugs in blink.

A version using commitStyles, which in implemented in both firefox and
chrome, but currently gives resolved values instead of computed ones
in chrome.

These assume that "computed value serialization", when referring to
a box-size dependent procedure, is used ion its historical context as
a deprecated term for what is now "resolved value" (as returned by
getComputedStyle()), and the serialization of the true computed value
follows the property infobox.  This interperetation is currently used
by both Firefox and Chromium.

A spec issue to update the language around resolved value is at
https://github.com/w3c/csswg-drafts/issues/4869

Change-Id: I59afcc9f73906051212cc71570631509920ddc32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103520Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: George Steel <gtsteel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751418}

The change enables top level target handler to auto-attach to service worker
when they are created and pause their execution until runIfWaitingForDebugger
is received from the client. This brings service worker functionality on par
with pages and will enable automation tools to configure a service worker
without attaching to every page that may use it.

Design document: https://docs.google.com/document/d/1hbTowhyfrf6CaYuNEHjY_OVx2KgZmnbp8kg_wUdGFiA/edit#

Bug: 1051687
Change-Id: I24ceb9398bce1ab00afbbe427c508e4fa5a7ead5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107792
Commit-Queue: Yury Semikhatsky <yurys@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Peter Marshall <petermarshall@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751417}

This CL refactors the test params provided by IncognitoDataTestUtils
into IncognitoToIncognito, RegularToIncognito and IncognitoToIncognito.


Bug: 1035770
Change-Id: Iea45dcb553684c129105252fbef5118eaf8dd747
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106177Reviewed-by: Rohit Agarwal <roagarwal@chromium.org>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Commit-Queue: Rohit Agarwal <roagarwal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751416}

Bug: 1055876
Change-Id: I43f29d7d3cd139905fc397d7d0282a39e18dc133
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108524Reviewed-by: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Mila Green <milagreen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751415}

This CL makes stories in system_health_infinite_scroll benchmark more
janky by scrolling faster and in different directions. This is an
experiment to evaluate sensitiveness of jank metrics.

Bug: b/150125501
Change-Id: I57813de1ab2b0a78841a4e4c7b0997cc342a18a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108147Reviewed-by: Stephen Nusko <nuskos@chromium.org>
Commit-Queue: Mikhail Khokhlov <khokhlov@google.com>
Cr-Commit-Position: refs/heads/master@{#751414}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/56a118c8..6325afac

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

Per https://wicg.github.io/scroll-animations/#avoiding-cycles, snapshot
scroll timeline state once per frame. Changes made:
- Snapshotting is done by saving scroll timeline current time and
  phase.
- Snapshot scroll timeline state as part of the ScrollTimeline
  constructor.
- Every time ScrollTimeline needs to query current time or phase, use
  the snapshot.
- Any scroller layout change calls scroll timeline invalidation.
- When scroll timeline is invalidated outside of the document lifecycle
  update, its state is re-snapshotted and attached animations are
  marked as outdated. This is required to ensure correctness of user
  scripts that query animation properties after scroller updates, like
  the following:
    scroller.scrollTop = 100;
    console.log(anim.effect.getComputedTiming().localTime);
    console.log(timeline.currentTime);
- If scroll timeline is invalidated during lifecycle update the same
  procedure of snapshotting and marking the animations as outdated runs
  right after the lifecycle update.

Bug: 944449
Change-Id: Id4330a15501b3a1312803d06e4ab9e3130ee3ee1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005629
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751412}

Bug: 1058898
Change-Id: I0321b9d53a03c571463b7213eecd4ac8e9b99a44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107682Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Livvie Lin <livvielin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751411}

After https://chromium-review.googlesource.com/c/chromium/src/+/2079840,
the NativeThemeDarkAura was almost entirely replaced by a forced to dark
version of the platform native theme. This change cleans up the
remaining usages as well as removing the files and any straggling
includes and build references.

Bug: 1058945
Change-Id: I2e10f5467ab3f85ec2af9e254f8f7b6e89b04d1e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107686Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: John Smith <johnsm@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#751410}

When the number of builders with the same name goes from 1 to >1 or
vice-versa, transient infra failures occur because the scheduler
configuration will be updated while there are already builds running
that will attempt to trigger the old job name. This change removes that
as a problem.

Change-Id: I1547659f61912ef758edb53f86f2092e723a7c54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107805
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Aaron Gable <agable@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751409}

This patch adds a constant for Google Play Billing, which will have its
own logic added in upcoming patches.

Bug: 1062362
Change-Id: If47b970b2d0c062bb4622fa0de032b3b38165e5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106885Reviewed-by: Danyao Wang <danyao@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751408}

The goal of this CL is to make the OneGoogleBar as functional as
possible and allow collaboration with the OneGoogle team to make the
OneGoogleBar completely functional as well as provide the ability to
test end-to-end.

The OneGoogleBar is hosted by
chrome-untrusted://new-tab-page/one-google-bar. The WebUI NTP embeds
this using an iframe.

In order for OneGoogleBar overlays to work, this CL uses mouse event
forwarding. While this may not be the approach used for launch, it will
allow the NTP and OneGoogle teams to test the OneGoogleBar and iterate
towards a better approach.

The Gmail and Images links are also updated so they open in the top
frame. This is temporary until the OneGoogleBar updates those links to
use <a target="_top">.

Bug: 1039913
Change-Id: Ic265d5bfd5c8728c6ff3b6556cede51c92571863
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106739Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Commit-Queue: Esmael Elmoslimany <aee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751407}

No change to logic or user-facing UI.

Refactor resuable error messages for webview package error and crash
consent to be part of the layout file instead of adding them to the
activities views at runtime.

Bug: 1061164
Test: manually verify that error messages are shown/hidden as expected with no changes
Change-Id: I5939b8c308130c31133d9db9442dc66d327b5245
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107985
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Auto-Submit: Hazem Ashmawy <hazems@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751406}

Instead of finishing the Activity, this dismisses the dialog when the
user presses "cancel." This permits the user to see information about
other crashes, even if they don't want to upload them.

Bug: 1062500
Test: Manual
Change-Id: Iee6d8e159aa61e77b1de1c97c7621f69657e9f52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108165
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Hazem Ashmawy <hazems@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751405}

This change makes it possible to create a Node instance without having
access to the graph immediately. This will allow making the
PerformanceManagerImpl::Create*Node functions static, removing the need
to expose PerformanceManagerImpl::GetInstance().

This change also introduce OnJoiningGraph() and OnBeforeLeavingGraph()
that are meant to be overridden by derived classes instead of
overriding JoinGraph() and LeaveGraph(). This avoids the need for
subclasses to remember to call the base version of that virtual
function.

Bug: 1013127
Change-Id: Id443b8013e59a368fdfdc9a0df9a9929e814da52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107609
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751404}

Breadcrumbs rely on NavigationContext::GetError inside
WebStateObserver::DidFinishNavigation callback, so this CL allows to
log net error code for Breadcrumbs.

Additionally the change makes ios/web API more consistent as the same
error is passed to WebClient::PrepareErrorPage and
WebStateObserver::DidFinishNavigation.

Updated tests to check for underlying error and net error code.

Bug: 1046223
Change-Id: Ic048e8d6901455c8bdce1fc3e5a2ae7ed33bec10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108340Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751403}

NOTRY=true

Bug: 1062697
Change-Id: Icd9bb6aae9340c59577011ec19a75796bc5023c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107064Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751402}

The rebase was missing a file. Now it's fixed.

This is a reland of 7e0c31e0

Original change's description:
> Adding new parameter raster_mode to CreateSharedImageProvider
>
> Adding a new parameter, raster_mode, that determines if the newly
> created CanvasResourceProvider of SharedImage is GPU or CPU.
>
> In later changes we need to be able to specify this to be false, while
> it was defaulted to true inside the CreateSharedImageProvider.
>
> Here we are just adding the new parameter and fixing all callsites with
> true (as it was the earlier value).
>
> Bug: 1035589
> Change-Id: Ifb640dacf59b0c12ec098645f341bedc93a3ad96
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2104213
> Reviewed-by:
> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
> Reviewed-by: Khushal <khushalsagar@chromium.org>
> Reviewed-by: Fernando Serboncini <fserb@chromium.org>
> Commit-Queue: Juanmi Huertas <juanmihd@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#751185}

TBR=kbr@chromium.org

Bug: 1035589
Change-Id: I427fb7a48c55641ceb81c62cd5e97d9cdd4e1064
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108166
Commit-Queue: Juanmi Huertas <juanmihd@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751401}

This can be used to force parameter values for unit testing.

Bug: 1061485
Change-Id: Ic34dac0cb82bf82146b92869292f812dfebd84f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103259Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751400}

Otherwise MayBlock may never reach timeout.

Bug: 1038867
Change-Id: I6615b5e2447bd47aa22860c29eb87d000a85a77e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2105460
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751399}

The user-desired Windows color settings are getting lost when doing
PrintingContextWin::UpdatePrinterSettings().  This is due to the
color settings getting ignored by the GDI DocumentProperties()
call made from CreateDevMode().  The resulting default color setting
provided from GDI ends up propagating through to
PrintSettingsInitializerWin::InitPrintSettings().

Correct for this by patching the requested color settings into the
resulting DEVMODE structure after CreateDevMode() (as opposed to before
like for all the other supplied settings).

Bug: 789538
Change-Id: I2c4597dba10051150f92baf361103343c1249066
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107575Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Alan Screen <awscreen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751398}

When a dsym is present we can get the file that each initializer was from
and compare against a list of accepted files. This helps support code
coverage on the CQ, which adds 2 additional static initializers.

When a dsym is not available, we fall back to counting how many static
initializers there are and comparing that against a hardcoded number.

Bug: 1059432

Change-Id: I6a1df68371a34724822343198afb14fdd1f9cff8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106349
Commit-Queue: Sajjad Mirza <sajjadm@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751397}

The comment implies that this code prevents side effects from profile
changes past applicationWillTerminate from notifications, however no
code path seems to touch the profiles/identities at all.

Bug: None
Change-Id: Ic2a31426e941875f48c31742877ae69d7c75add4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107482
Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751396}

Bug: 1050649
Change-Id: I00606ad48007de35fb1d21420bf44dd042b4cf98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107057
Commit-Queue: Jun Liu <yjliu@chromium.org>
Commit-Queue: Christopher Thompson <cthomp@chromium.org>
Auto-Submit: Jun Liu <yjliu@chromium.org>
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751395}

This reverts commit d80699f2.

Reason for revert: Broke swarming again:
https://ci.chromium.org/p/chromium/builders/ci/android-lollipop-arm-rel/783

Original change's description:
> Reland "Make java_deobfuscate not require being built first"
> 
> This reverts commit 0b8c0e6a.
> 
> Reason for revert: Fixed runtime deps
> 
> Original change's description:
> > Revert "Make java_deobfuscate not require being built first"
> >
> > This reverts commit 962e7030.
> >
> > Reason for revert: Failing on swarming
> > https://ci.chromium.org/p/chromium/builders/ci/android-pie-x86-fyi-rel/747
> >
> > Original change's description:
> > > Make java_deobfuscate not require being built first
> > >
> > > Makes the tool easier to use, and easier to document how to use by not
> > > requiring it to be built first. We have only a single non-prebuilt .java
> > > file, so it's easy enough to just check in the .class file for it.
> 
> Bug: 995290
> Change-Id: Ib1f396e07d6b0737133f03f1bded1a2d312ebfc8
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106972
> Commit-Queue: Andrew Grieve <agrieve@chromium.org>
> Reviewed-by: Sam Maier <smaier@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#751322}

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

Change-Id: I7510d193931940176178ad6f68122f634ed59e93
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 995290
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108612Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751394}

Bug: 1035589
Change-Id: I57ea8d46e10a1b2a06902d2e3c4216e1e7212114
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2104211Reviewed-by: Yi Xu <yiyix@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Juanmi Huertas <juanmihd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751393}

https://webrtc.googlesource.com/src.git/+log/4c07605f8d55..6798043d95ac

git log 4c07605f8d55..6798043d95ac --date=short --first-parent --format='%ad %ae %s'
2020-03-18 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 0fe8f345..1386d9f5 (751074:751294)
2020-03-18 mbonadei@webrtc.org Remove apk-patch-size-estimator from DEPS.
2020-03-18 phoglund@webrtc.org Proper fix to the summary options problem.

Created with:
  gclient setdep -r src/third_party/webrtc@6798043d95ac

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/+/master/autoroll/README.md

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

In third_party/blink/renderer/core/animation/timing.h,
there are static inline functions defined, which are harmful
from a PoV of namespace contamination.  (Static inline functions
in *.h are no good in the first place.)

Moves IsNull and NullValue into Timing struct, and removes
ValueOrUnresolved.

Change-Id: I777740c4ce020dc78350fb2b5c9322db10660705
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106988Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751391}

This makes it easier to read long URLs or other fields.

Change-Id: I33a943a82fe9a3a9a4d2f2f5ef30c8fbb6197bcd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107691
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751390}

Have AppShimTerminationManager call back into
AppShimManager::Delegate to determine if app windows are open.

This will allow us to remove all includes of platform_apps from
app_shim.

Bug: 1057195
Change-Id: I04d13efaca5f65fd507c0f949068e2a6d830e2fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108003Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751389}

WebStateObserver::PageLoaded triggers this call in
LanguageDetectionController, but it can be executed while a preloaded
WebState is finished in the background. Then, when that WebState
is swapped out as the active WebState, StartLanguageDetection()
will never be called in LanguageDetectionController. Thus,
the infobar never shows. Adding the call to the init method when
the WebState is swapped solves the issue.

Fixed: 947482
Change-Id: If6b6a77711039835596374bdc6121ece4642987c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095355
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Reviewed-by: anthonyvd <anthonyvd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751388}

If the setup fails for some reason, the test server may be null. Check
for null so that the test failure reason shows the startup error.

BUG=1062642

Change-Id: I2a7710da86f94ae50420f010c4ec74a8070381f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108602Reviewed-by: Lijin Shen <lazzzis@chromium.org>
Commit-Queue: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751387}

There has a chance that the |SynchronousCompositorProxy| will re-attach the new
compositor when the RWHWA was reused, and the |SynchronousCompositorControlHost|
will bind failed if the remote has been bound. The browser will hang when send
a |BeginFrame| through the new |SynchronousCompositorHost| but the
|BeginFrameResponse| was sent to the old host control.

Bug:1062576

Change-Id: I0bb953a265a1f1d5b8a445701702c168aa7316f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107333Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751386}

BUG=1027790
TBR=boliu@chromium.org

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

BUG=1060975
TBR=dmurph@chromium.org

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