GitLab

The heap profiling service only runs in-process and its lifetime is
effectively managed by the heap_profiling::Supervisor singleton.
This removes the Service Manager from between the Supervisor and the
service implementation.

ProfilingClient receivers are bound in child processes through
|ChildProcess.mojom.BindReceiver()| instead of through a Connector
to the child process's Service impl. The necessary logic already exists
in child processes via ContentClient::BindChildProcessInterface(), so
no changes are needed in child process code here.

Some Service Manager dependencies remain only to acquire Resource
Coordinator interfaces before injecting them into the heap profiling
service implementation. These will be removed when Resource Coordinator
is moved off of Service Manager.

Bug: 977637
Change-Id: Ifb2c2cf404ac7e3db6a0e7b60fc99ed87dee097a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732696Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#683742}

Change-Id: I172fb7f98693cd2b8e46b7510b9160b4e49cdae2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733854
Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org>
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Auto-Submit: Fabrice de Gans-Riberi <fdegans@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683741}

https://swiftshader.googlesource.com/SwiftShader.git/+log/029a36c7cbfc..060fcf777159

git log 029a36c7cbfc..060fcf777159 --date=short --no-merges --format='%ad %ae %s'
2019-08-02 swiftshader.regress@gmail.com Regres: Update test lists @ f63c4e51

Created with:
  gclient setdep -r src/third_party/swiftshader@060fcf777159

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=swiftshader-team+autoroll@google.com

Bug: None
Change-Id: I1f7317a609dca70d1e5101de6958ae15e81aed8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733411Reviewed-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@{#683740}

Sessions should be saved when there are no webStates at all, right now
Chrome doesn't save the session if there is no active webState which
include cases where there are no webStates at all.

Bug: 989482
Change-Id: I96538dbf21be6d20730dd8800988379f0882c8d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730166
Auto-Submit: Mohammad Refaat <mrefaat@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683739}

Instead of the download icon, use a new icon with the outline of a
folder.

http://screen/e8nJioNs5bP

Bug: 990063
Change-Id: I01d31aaed41ab433460fe389dadf2b5b58ea615d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731104
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683738}

In the current version of AppMenu, the InMenuButtonBackground does not
depend on the state of other views, so there is no need to invalidate
all the other views (forcing a paint-all).
When the comment justifying the SchedulePaintInRect() override was
written, the MenuButtonBackground varied its painting depending on
the state of other views, left_button_ and right_button_.
Whenever the state of one of the other buttons changed, any other
views using a MenuButtonBackground needed to paint too, which is why
SchedulePaintInRect() very heavyhandedly forced a paint-all.

Change-Id: Id3030139ca0cb31e34d610078cfdd13e94494ce8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733460Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Annie Su <anniesu@google.com>
Cr-Commit-Position: refs/heads/master@{#683737}

MessageLoopForIO will go away soon use ScopedTaskEnvironment instead.

ScopedTaskEnvironment will per default start a ThreadPool, which should
be fine in most of the cases. If you believe your test needs to make sure
that no ThreadPool runs let me know and I will update the patch.

BUG=891670
This CL was uploaded by git cl split.

R=kylechar@chromium.org

Change-Id: Ib3a70b497ba1117d20f30399903e40ce204f996f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733534
Auto-Submit: Carlos Caballero <carlscab@google.com>
Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683736}

Bug: 988891
Change-Id: Ifcafee429c75da79a9f980b022a9524795922f48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726954Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683735}

The CrOS lock screen media controls can now be swiped up on to dismiss. If the
controls are dragged past a certain height or are swiped with a large enough
velocity, the controls will be animated off the screen and playback will stop.
The opacity of the controls changes as they are dragged up and down. If the
controls are not swiped high or fast enough, they will be animated back down
to their initial position.

See bug for video examples.

Bug: 965575
Change-Id: I2bc264ec45c82772a17a926dfbe3e04ad59d01a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730132Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Commit-Queue: Mia Bergeron <miaber@google.com>
Cr-Commit-Position: refs/heads/master@{#683734}

This CL fixes an inconsistent test spec.

Change-Id: Icd7e2b077915c4e27f348afd68d2ed71ab539d33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733578
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683733}

This is a collaboration of fdoray@ (Catan) and dfried@ (Top Chrome) to
improve how preview images are captured for tab hover cards and for
the new touch-enhanced tablet tab-switcher being developed by the
WebUI team in collaboration with the Views and Top Chrome teams.

Tab preview thumbnails are an integral part of our UX plan for tab-
switching improvements in the next few quarters. Previous
infrastructure was aimed at saving images for the NTP, which was a very
different set of capture situations than what we want for tab previews
(specifically, background-loaded tabs were never captured). This logic
allows the capture of tabs loaded in the background or restored from a
previous session by using a different capture mechanism.

This functionality is entirely behind a flag and is known to be slightly
buggy. We plan to use volunteers to teamfood the functionality and send
feedback/issues so it can be made ready for production.

Change-Id: Ie356b95dc42b75729860c772e9a01a19028d0fee
Bug: 981103
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1689397
Commit-Queue: Dana Fried <dfried@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683732}

TBR=corising@chromium.org

BUG: 990210
Change-Id: I15dc467182133ae8793a5174b1f84dfcfeb8429e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732332Reviewed-by: Chris Sharp <csharp@chromium.org>
Commit-Queue: Chris Sharp <csharp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683731}

Also removed the hover highlight of the new desk button.

Bug: 970328, 990044
Test: Manually
Change-Id: Iea844d9614d391f3bd5c53d2c50ff114cfeccd36
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732892Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683730}

WebGPUSwapBufferProvider::PrepareTransferableResource must use
GL_TEXTURE2D_RECTANGLE_RGB only on Mac.

Bug: 989818
Change-Id: I1bc11d3f0a8fab7d5de208e744a8c1aa24c47828
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730255Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Commit-Queue: Rafael Cintron <rafael.cintron@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#683729}

-Styled the in-page select, options, and optgroups via css.
-Modified the scrollbar to have rounded corners
(had to plumb the zoom factor through the Scrollbar so that the native
theme aura code can get the rounding correct at paint time)

Bug: 987292
Change-Id: Id11d1a47fe3d5b2be01aa578aa066f80577a9bbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715553
Commit-Queue: Allison Pastewka <alpastew@microsoft.com>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683728}

Make it possible to write pdf_unittests test cases that call
PDFiumPage::CalculateLinks() without requiring PPAPI initialization.

Change-Id: I8433baf810128039efa4705a8862b95f97efd9ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725427Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683727}

Fixes a bug in which in_subtree_layout was not properly updated due to the
possibility of ClearLayoutSubtreeRootsAndMarkContainingBlocks being true
when doing a re-layout in post-layout tasks.

Bug: 990225,462719,970224

Change-Id: I8d5b0a543646c5833850a2ec921affc4d71f4dd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733462Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683726}

No change to behavior.

This removes the kCheckByURLLoaderThrottle feature. This feature was
only relevant when Network Service was disabled. Since NS is enabled for
all platforms (and the legacy net path is no longer supported), we can
remove the feature entirely.

Bug: 989709
Test: double-check WebView safe browsing still works with the demo app
Change-Id: Ia62c503b66b30c97571e8fbc2ce351962f8b7b19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732391
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Nathan Parker <nparker@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683725}

NOTIFICATION_TAB_LANGUAGE_DETERMINED and NOTIFICATION_PAGE_TRANSLATED
waiters are removed in favor of a helper class that observes the tab's
ContentTranslateDriver.

Also, ChromeTranslateClient::translate_driver() is changed to return
a pointer instead of a non-const ref.

Bug: 268984
Change-Id: I450ace7f647cf9418a28ac36aef70bf1f97a3f17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724420Reviewed-by: anthonyvd <anthonyvd@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683724}

Adds toplevel.flow trace events for message pipe closure to link the
closure of one endpoint to the detection of that closure by its peer
endpoint. This allows pipe closures to be followed like other IPC
message events, since pipe closure is often an important type of IPC
in itself.

Bug: None
Change-Id: I78c928972eddebef26c1ea9765dd697c17807f63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733786
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683723}

removing HTTP authentication data.

This CL is part of a larger project to remove the LOAD_DO_NOT_* privacy load
flags and replace them with the allow_credentials setting. See
https://crbug.com/799935,
https://docs.google.com/document/d/1ntn9N7Ce2jozvvpWI0XbzJ7lJdwUjJXK07wp7rxrIN4,
and
go/allow-credentials-tracker
for the motivation and progress of this change.

This CL handles a third of cases where LOAD_DO_NOT_SEND_COOKIES and
LOAD_DO_NOT_SAVE_COOKIES were set, but LOAD_DO_NOT_SEND_AUTH_DATA was not.
This CL will set allow_credentials = false instead, which will make two changes
to the requests:

- The request will no longer participate in HTTP auth if the server requests
  it. HTTP auth credentials identify the user, so private requests should
  not send them. Note this only affects server auth, not proxy auth. Unless
  the server your feature speaks to requests HTTP auth, this is a no-op.
- The request will be pooled with sockets used for uncredentialed requests,
  rather than credentialed requests. This is not expected to meaningfully
  change behavior.

If your code requires HTTP authentication, let me know. You may need to allow
credentials for your request.

Bug: 799935
Change-Id: I48c22f202d5221b33dadf0d66c8f2e3435238a71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1580582Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Andrew Moylan <amoylan@chromium.org>
Reviewed-by: Henrik Grunell <grunell@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Parastoo Geranmayeh <parastoog@google.com>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: oysteine <oysteine@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Reviewed-by: sebsg <sebsg@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Jesse Selover <jselover@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683722}

Using this + the DoNotInline fix (crrev.com/c/1730845), we go from 47 to 37
RetryVerifcationAtRuntime classes.

Bug: 965189
Change-Id: Ibbe9da08c0f0756fc9fc5c915c246e0352c32819
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731771
Commit-Queue: Sam Maier <smaier@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Auto-Submit: Sam Maier <smaier@chromium.org>
Reviewed-by: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683721}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9873ee0de15a..116752315474


Created with:
  gclient setdep -r src-internal@116752315474

The AutoRoll server is located here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

Bug: chromium:None,chromium:None,chromium:None,chromium:None
Change-Id: Ic2ca0c522c0e5803e6b16be17580cbccd0521b71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733787Reviewed-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@{#683720}

No significant code changes other than imports.
Moving existing code out of https://chromium.googlesource.com/enterprise/cel/+/refs/heads/master/test/chrome_ent_test/ent_tests/

Also updated the infra package with a version that has those files
deleted (https://crrev.com/c/1726909).

We're moving these files here because they're not used in other repos
and need to be edited frequently for tests here (and updating the
package is a tedious process).

This move will improve our engineering productivity for those changes.

It will also make some refactorings a lot easier:
  https://crbug.com/986439
  https://crbug.com/986444
Will be sending those out shortly.

Validation:
  https://ci.chromium.org/p/chromium/builders/try/win-celab-try-rel/46

Change-Id: I7343ccb7f50d1f203d4dd38013bb1de723599f97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727229
Commit-Queue: Mathieu Binette <mbinette@google.com>
Reviewed-by: Owen Min <zmin@chromium.org>
Auto-Submit: Mathieu Binette <mbinette@google.com>
Cr-Commit-Position: refs/heads/master@{#683719}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/4af1fe027b83..be9e4bf1b538

git log 4af1fe027b83..be9e4bf1b538 --date=short --no-merges --format='%ad %ae %s'
2019-08-02 mmortensen@google.com Fix call to ArchiveFilesFromImageDir.

Created with:
  gclient setdep -r src/third_party/chromite@be9e4bf1b538

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel
TBR=chrome-os-gardeners@google.com

Bug: None
Change-Id: Id894857ca5897d54861b8f3e58e02a804616d07f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733708Reviewed-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@{#683718}

CodecBufferWaitCoordinator is null in overlay mode. Add missing null
checks while accessing TextureOwner from it.

Bug: 990321,990273
Change-Id: I02b638fb505b8e3d0dc33def5a43e651f96a5894
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733746
Auto-Submit: vikas soni <vikassoni@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Commit-Queue: vikas soni <vikassoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683717}

RenderWidget objects are re-used for same-domain navigations, meaning
the input handler lives on. The lifecycle state of the input handle
must be reset on navigation to correctly report input timing.

We also increment the histogram name to reflect the change in data
measurement. And rename some of the methods to better match other parts
of the code.

Bug: 958424
Change-Id: Ic43e3a1256000ca3d99e119b3cb8ceee66dc8499
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729794
Auto-Submit: Stephen Chenney <schenney@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683716}

https://dawn.googlesource.com/dawn.git/+log/54b4df706968..ef4f3bd17474

git log 54b4df706968..ef4f3bd17474 --date=short --no-merges --format='%ad %ae %s'
2019-08-02 idanr@google.com Add external memory and semaphore extensions

Created with:
  gclient setdep -r src/third_party/dawn@ef4f3bd17474

The AutoRoll server is located here: https://autoroll.skia.org/r/dawn-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
TBR=cwallez@google.com

Bug: chromium:976495
Change-Id: I7b2286d630068880f1cb3cf9f4285b1064f307a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733728Reviewed-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@{#683715}

https://chromium.googlesource.com/catapult.git/+log/4f68ff26e4e9..1dc9ce56c488

git log 4f68ff26e4e9..1dc9ce56c488 --date=short --no-merges --format='%ad %ae %s'
2019-08-02 bsheedy@chromium.org Reland "[Telemetry] Fix GetRecentMinidumpPathWithTimeout log spam"

Created with:
  gclient setdep -r src/third_party/catapult@1dc9ce56c488

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=rmhasan@google.com

Bug: chromium:985530
Change-Id: Ib01952086415de6959032c39fd6b77c679e1907a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733515Reviewed-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@{#683714}

Other build and distribution systems are not yet setup to handle another
jar. To avoid having a missing target, move the util library target
inside the common jar, so that it will build properly and be able to be
found by the Java platform implementation of Cronet.

Bug: 669707
Change-Id: I8b98d5f09fb789075734962934a5d9b52a9a561d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733433Reviewed-by: Paul Jensen <pauljensen@chromium.org>
Commit-Queue: Benjamin Kirchman <kirchman@google.com>
Cr-Commit-Position: refs/heads/master@{#683713}

This change updates the property JSON to allow day of month the full
range of values from 1 to 31. This reflects the existing implementation
that handles monthly rollovers.

BUG=924762
TEST=Unit tests.

Change-Id: I9672ccc77a33118e9c668c9ff05459354889dbc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732433Reviewed-by: Lutz Justen <ljusten@chromium.org>
Commit-Queue: Abhishek Bhardwaj <abhishekbh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683712}

This is a reland of 76c1237a
with stale #includes removed (see PS1->PS2)

Original change's description:
> Remove "chrome" and "chrome_renderer" services
>
> This eliminates the existence of the "chrome" and "chrome_renderer"
> services as well as general support for embedder-provided process-wide
> browser and renderer Service Manager services.
>
> Remanining browser<->renderer interfaces which used these services have
> been migrated to use direct receiver binding via
> content.mojom.ChildProcess or content.mojom.ChildProcessHost messages.
>
> Change-Id: I74f012aafe77fdcbbba8d93d193d3ded8d63d445
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729968
> Reviewed-by: Luke Halliwell <halliwell@chromium.org>
> Reviewed-by: Bo <boliu@chromium.org>
> Reviewed-by: Tom Sepez <tsepez@chromium.org>
> Reviewed-by: Avi Drissman <avi@chromium.org>
> Commit-Queue: Ken Rockot <rockot@google.com>
> Cr-Commit-Position: refs/heads/master@{#683650}

NOPRESUBMIT=true

Change-Id: I03c7a26fc2f5085078de12a4642837f8f7b28c8b
Tbr: avi@chromium.org
Tbr: boliu@chromium.org
Tbr: halliwell@chromium.org
Tbr: tsepez@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733577Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#683711}

TBR: estevenson - OOO right now
Bug: 990411
Change-Id: I43a64422eaa8345991fa255084b95e2e119fa494
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733021
Commit-Queue: Sam Maier <smaier@chromium.org>
Auto-Submit: Sam Maier <smaier@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683710}

This CL removes ExtensionService::GetExtensionById().

TBR=atwilson@chromium.org
TBR=battre@chromium.org
TBR=benwells@chromium.org
TBR=dtrainor@chromium.org
TBR=estade@chromium.org
TBR=lazyboy@chromium.org
TBR=reillyg@chromium.org
TBR=sky@chromium.org
TBR=stevenjb@chromium.org
TBR=tapted@chromium.org
TBR=thestig@chromium.org

Bug: 489687
Change-Id: I3919bd1b0b76f32190750a63f3088cfe528e6a03
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1704521
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683709}

https://skia.googlesource.com/skia.git/+log/149f3f197897..17b9d1d1deaf

git log 149f3f197897..17b9d1d1deaf --date=short --no-merges --format='%ad %ae %s'
2019-08-02 fmalita@chromium.org [skottie] Initial Hue/Saturate effect support
2019-08-02 mtklein@google.com x86 store16
2019-08-02 robertphillips@google.com Increase specificity of GrColorType computed for YUV planes
2019-08-02 reed@google.com fix bicubic to not be confused by rotated ctms
2019-08-02 robertphillips@google.com More SkAutoPixmapStorage
2019-08-02 csmartdalton@google.com Extract a GrRenderTask base class from GrOpList
2019-08-02 mtklein@google.com x86, load16
2019-08-02 halcanary@google.com experimental/editor: cleanup
2019-08-02 mtklein@google.com x86 uniform8

Created with:
  gclient setdep -r src/third_party/skia@17b9d1d1deaf

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=benjaminwagner@google.com

Bug: None
Change-Id: Ie948c2ff528da2ba0399b78309b9818c0726ae78
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733729Reviewed-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@{#683708}

We are now using SharedImage to hold the image for the video renderer,
https://chromium-review.googlesource.com/c/chromium/src/+/1616978.
That change, together with the change that made the video be deferred, and
therefore, use the paintRecorder, let us safely remove the workaround.

We are adding some comments to explain that removal, in case that this is
stopped being deferred at any point.

Bug: 974656
Change-Id: If050f1f12b098709e20547cb56709d4e5381af90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733438
Commit-Queue: Juanmi Huertas <juanmihd@chromium.org>
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683707}

Any CCT intents at this point are internal CCT intents, possibly coming
from the WebApk itself opening a new tab, so we shouldn't redirect them
back into the WebApk.

Bug: 983769
Change-Id: If0fb0b3c3a9a2641955e6226709fcb01475ae050
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732877Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683706}

This is still used in integration testing.

Bug: 969949
Change-Id: I5b89c617324f541fb7429748f4f7b7c2e1f76207
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728435
Auto-Submit: Robert Ogden <robertogden@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683705}

https://swiftshader.googlesource.com/SwiftShader.git/+log/59d55a331c46..029a36c7cbfc

git log 59d55a331c46..029a36c7cbfc --date=short --no-merges --format='%ad %ae %s'
2019-08-02 capn@google.com Omit null initialization of sampler cache pointers

Created with:
  gclient setdep -r src/third_party/swiftshader@029a36c7cbfc

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=swiftshader-team+autoroll@google.com

Bug: chromium:b/137649247
Change-Id: I769884a0b1dceab9d31a1efd8f91b67678d1b996
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1733574Reviewed-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@{#683704}

We currently rely on all SSLConfigService-managed parameters being
passed into the socket pools identically from HttpNetworkSession.
Instead, abstract that behind SSLClientContext.

SSLClientContext now consumes the SSLConfigService OnSSLConfigChanged
signal itself and exports its own signal for the callers. This means the
socket pools can use one observer interface to invalidate everything.

As part of this, split SSLConfig in two: SSLConfigService manages a
smaller SSLContextConfig which is shared across the whole context, while
SSLConfig is per-socket configuration.

Bug: 951205
Change-Id: I018a26bbc2a57f954df48249a8e4bc8b55a1ad26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1703205Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Reviewed-by: Matt Mueller <mattm@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683703}