GitLab

ccameron is going to be tackling this :)

Bug: 716231
Change-Id: I56f04c4c8be9744eb0f8b4defc6dcd11cd3ec1aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586274
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654679}

This should let us parse some results even if something goes wrong
and the final results.json doesn't get generated for some reason.

Bug: 923426
Change-Id: I028896c9edc7aeb8b3ec6339b8867f0b29ae095f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575105Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654678}

Originally I wanted to revert the dragging operation as well, but seems
there is a test specifically to keep that functionality. Though it may
be obsolete now as there isn't a way to enter overview while dragging as
far as I can tell, but for now I will just hide the resize shadow.

Test: added test
Bug: 956184
Change-Id: I15ff202a52b779870c28047f455317796e8f8782
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586263Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654677}

Bug: 955783
Change-Id: Ica674d05503cbc96389b52d0fe554e9898b01e9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585549Reviewed-by: Katie Dektar <katie@chromium.org>
Commit-Queue: Anastasia Helfinstein <anastasi@google.com>
Cr-Commit-Position: refs/heads/master@{#654676}

Sets the offline pages prefetching feature flag to be enabled by
default.

Bug: 881120
Change-Id: I735723193fbb19100e6962b8861d4fd04933e4c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1562295Reviewed-by: Dan H <harringtond@chromium.org>
Commit-Queue: Ian Wells <iwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654675}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/7232e2246072..6841244fb6c0


Created with:
  gclient setdep -r src-internal@6841244fb6c0

The AutoRoll server is located here: https://autoroll-internal.skia.org/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=andruud@chromium.org,alexmos@chromium.org,horo@chromium.org,adithyas@chromium.org

Change-Id: I9db5a02bbc6a23b78ca9d4a3a5be44c5e2d74ddf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586387Reviewed-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@{#654674}

This change is meant for forcing theme property recalculation in M75.

Bug: 942135
Change-Id: Ie6c912234906702381ea5fc5fc5919eb1e14ad99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585321Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654673}

The output sample rate of APM should be the same as the input to it.
Cast platform is switching to the new behavior. Yet using Cast build
flag to avoid affecting legacy usage.

Bug: internal b/130197895.
Test: On device, see the output sample rate is correct.
Change-Id: I392a1490997057cb9fbfea1c1b60d1c689938a1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572807
Commit-Queue: Kehuang Li <kehuangli@chromium.org>
Reviewed-by: Max Morin <maxmorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654672}

Screenshot: https://drive.google.com/open?id=1yYp4LVAuevYbhrCS4vqmxztLxxAvmIjr

Bug: 954624
Change-Id: Ia537f4bf6e997793c5ebff3dcdc473e83c738b75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585166
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654671}

Test: manual
Bug: 957151
Change-Id: I111826d8ecbb096ae696173b6369228249c77b57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586256
Auto-Submit: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Malay Keshav <malaykeshav@chromium.org>
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654670}

This is a part of moving manifest implementation to blink.
This CL moves content::ManifestManager to blink and introduces
WebManifestManager in blink/public/web to expose to //content,
and removes WebManifestParser, WebManifestFetcher and
ManifestError.

Bug: 704441
Change-Id: I2de0dea6f4f4f269fd84a7df78e190586350b93c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573520
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654669}

Limit enabling the print-spooler-experiment feature flag
to the Canary and Dev channels.

BUG=b:130798103
TEST=android-sh -c getprop | grep ro.boot.arc_print_spooler

Change-Id: I7717801c570ff4cadd220a491deea85cc203bf2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586264Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Commit-Queue: Jesse Schettler <jschettler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654668}

This CL adds the notification shown metrics for update notification,
which informs the user to update Chrome in play store.

Bug: 952354
Change-Id: Id0a6c1a944ec2bdadfc782926591e8b51d9a616c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585233Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654667}

The main benefit of the CL is that it takes away an ability to disable
Site Isolation on desktop without triggering a "security/stability will
suffer" butter bar.

Most edits in the CL, hide processing of kDisableSiteIsolationForPolicy
behind #if defined(OS_ANDROID).

chrome/browser/chromeos/login/session/user_session_manager.cc can be
substantially cleaned up in this CL because 1) it is CrOS-only (and the
ability to disable Site Isolation after this CL is restricted to
Android) and 2) IsolateOrigins policy is handled at runtime (see
r644966).

Bug: 910273
Tbr: sky@chromium.org
Change-Id: Ie7c845e27c55b37a460050de07c3f44e8cee7b4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576295
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654666}

Based on the gperftools' Makefile, emergency_malloc_for_stacktrace.cc
is used only when ENABLE_EMERGENCY_MALLOC is defined. We don't define
this flag in Chromium, so we should build only with
fake_stacktrace_scope.cc, which provides dummy definitions of the same
symbols.

BUG=724399,b:70905156

Change-Id: I03404df00ef1d530bd04d35634f1c29fe8bb56db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586100Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Gabriel Marin <gmx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654665}

This CL renames WebappSplashScreenController and WebappSplashDelegate
so that the classes can be used by TWAs.

This CL also renames
WebappSplashDelegate#isWebApkNetworkErrorDialogVisible()
so that it is more appropriate for TWAs as TWAs do not have an offline
dialog.

BUG=817263

Change-Id: Ia94fd27d1d256e950c8dc500abbf7bd69194e4bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572097
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Reviewed-by: Pavel Shmakov <pshmakov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654664}

It has been replaced with --memlog* set of flags.

BUG=923459

Change-Id: I539c514b3f25decd0dccb827d1757e133403e9d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586535Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654663}

This automates the task of removing a benchmark from the shard maps,
and thereby ensures that no mistakes can be made that later cause
inconsistencies and make the resharding process harder.

We can build on this later to add a PRESUBMIT test to ensure consistency.


Bug: 936998, 954651
Change-Id: Idaa91c1c321a2fade28fb226eaf43de94beb1f04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576029
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Auto-Submit: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654662}

This CL adds CSS rules to only show the timeline and volume slider
thumbs when the slider is hovered.

On Android, we want the thumbs to always be visible. In order to make
that work this CL adds a new modernMediaControls_Android.css file that
is loaded on Android.

Bug: 955806
Change-Id: Ic4ab9c34183ece52e22b37ff3bf0bf4dbb8839c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584167
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654661}

Fixes the following warning message when --memlog is used.
"ERROR:settings.cc(119)] Unsupported value: "" passed to --memlog-stack-mode"

Change-Id: I33d80a29ea117777e935199f1ab83827c7b3fbb0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586539Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654660}

Bug: 955134
Change-Id: I20e27371313f414cd394c7450c703cec21e426ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585477
Commit-Queue: Andrew Xu <andrewxu@chromium.org>
Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654659}

https://swiftshader.googlesource.com/SwiftShader.git/+log/a195abb4e601..f5c8936c463e


git log a195abb4e601..f5c8936c463e --date=short --no-merges --format='%ad %ae %s'
2019-04-26 chrisforbes@google.com Support more formats for input attachments


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

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

BUG=chromium:b/131171141
TBR=swiftshader-team+autoroll@chromium.org

Change-Id: I1ce976669dc680db0d949843a08ca1a51cdec68b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586105Reviewed-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@{#654658}

https://pdfium.googlesource.com/pdfium.git/+log/d0f989e0073d..5fb2ca3384f7


git log d0f989e0073d..5fb2ca3384f7 --date=short --no-merges --format='%ad %ae %s'
2019-04-26 tsepez@chromium.org Add some stronger checks to TreeNode<>


Created with:
  gclient setdep -r src/third_party/pdfium@5fb2ca3384f7

The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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.


TBR=dsinclair@chromium.org

Change-Id: Idbafc76c9f2a519e46eb241cfaf1cfbc84373f15
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586244Reviewed-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@{#654657}

Elements with an inner text editor should honor a HitTestRequest's
stop node.

BUG=951384
R=chrishtr@chromium.org

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

Chrome crashes if web apps allocate more than 4 GB of memory. Raise the sandbox
memory limit for the gpu/renderer processes to 8 GB or 16 GB on Linux if the
system has enough memory. (Mac and Windows also have a memory limit > 4GB.)

Bug: 756834


Change-Id: I2b447079132398a257eb46ca51ff9c2371f67b2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1581829Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Chris Palmer <palmer@chromium.org>
Commit-Queue: Maggie Chen <magchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654655}

This lays the ground work in an effort to introduce SSML support
into Chrome. This change refactors Speak() to be a void function, which
takes a callback to run upon completion, instead of returning a boolean.
This needs to be done because the XML Parser necessary for SSML support
runs asynchronously and accepts a void callback function to run upon
completion. Follow-up changes will be made to implement the SSML
parser.

Bug: 88072
Change-Id: Icfdbfb4dc0354dc9855fc8403292f2922d3d879f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583324Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Akihiro Ota <akihiroota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654654}

The new metric is SiteIsolation.SavedUserTriggeredIsolatedOrigins.Size,
which measures the number of entries in the
site_isolation.user_triggered_isolated_origins user pref, recorded on
browser startup.

Bug: 944640
Change-Id: I9b23b3edd1ee9f22d412518810613d9355957291
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583130
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654653}

This will be used by OverlayManager to drive the presentation of UI
for requested overlays.

Bug: 941745
Change-Id: I3f7f19e4131d349a12bedb27a5e9caac918ad37c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1559367
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Auto-Submit: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654652}

DevTools was using CompositorFrameMetadata for screen capture.
This change refactors things so that:
- Metadata update and actual capture are split into two steps.
- When SurfaceSync is on we use RenderFrameMetadata for update.

Bug: 955042
Change-Id: I7479305c1bcbcecf94587cb69960da7bb6ff01a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584923
Commit-Queue: Eric Karl <ericrk@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654651}

+ Update the 9-patch layout tab shadow to be the tab shadow for dark
  mode (and incognito when tab switcher background is the incognito
  primary color).
+ Use smaller alpha on light mode.

Bug: 951235
Change-Id: I9beeeada7fb3205579fafdc2c81547ce0e5cce5c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583440
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654650}

While editing a style value in SSP,
- Text input event triggers an update to queryRange,
  but no currentSuggestion yet, if loadCompletions() is slow
- At this point, 'textWithCurrentSuggestion()' == '', even
  though the prompt 'text()' has real user input
- Immediately press 'Tab', we commit the edit, which applies
  'textWithCurrentSuggestion()', which is empty. Applying
  empty text will abandon the new property, erasing user
  input.

This CL fixes textWithCurrentSuggestion so that quickly
pressing tab after a letter does not erase the property.

Bug: 931145
Change-Id: Ib3989d91e4b70e99ba2082ba46239a1b932a2f57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586223Reviewed-by: Joel Einbinder <einbinder@chromium.org>
Commit-Queue: Erik Luo <luoe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654649}

For LargestImagePaint and LargestTextPaint, the frame property lives in
event.args.data.frame, while telemetry expects every metric event to have the
frame property in event.args.frame.

This CL is to fix it in favor of telemtry.

Bug: 953712
Change-Id: Ibd385e4403a4ec422d53cc11457763afa788cab8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585989Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654648}

- In ElementAnimations::UpdateClientAnimationState(), only get animation
  scales when there is transform animation. This fixes the main reason
  of the regression caused by crrev.com/c/1547131.

- Combine HasOnlyTranslationTransforms(), AnimationStartScale() and
  MaximumTargetScale() of KeyframeEffect into one function to avoid
  duplicated code/executation when called separately from one place.

- Remove unused HasOnlyTranslationTransforms() from AnimationHost
  and ElementAnimations.

Bug: 951912
Change-Id: I5cc858fb012f0b7c0280b9935d84bc2aa4cf4d7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1580551
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654647}

This CL simplifies the test logic by removing Mac specific code.
Bug: 949486

Change-Id: I14c3e48db5593bb77e73d16fc40da886c098d118
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585886
Auto-Submit: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Peter Beverloo <peter@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654646}

If a target element is inline, then the hit testing code traverses
through the line box tree of the containing LayoutBlockFlow, which
won't check the stop node set on the HitTestRequest.

If the hit test result is an inline element inside the target node,
that should be treated the same as hitting the target node.

BUG=951384
R=chrishtr@chromium.org

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

Bug: 953384
Change-Id: If9988ab78a2ac80613dec065f35dd6f8f266c790
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1580766Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654644}

We should use one consistent file path style for all conformance test names.
We should use the linux style paths, which are already used within the
test times JSON results.

Bug: chormium:955099
Change-Id: I141799947a2ec292a4dc0a30e168025969f49c7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585554Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Rakib Hasan <rmhasan@google.com>
Cr-Commit-Position: refs/heads/master@{#654643}

As a manager-wide property, removed from ContextHostResolver.  It can
now only be called directly on the manager.

Since much of the usage was just setting an initial value, added
|dns_config_overrides| to ManagerOptions. This is especially needed for
stand-alone resolver cases where such an intial value is needed, but
there are no references to the underlying manager.

Bug: 934402
Change-Id: Ic653d5fe2082c1191c5a23e3a2b143f1ff4c803b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582438
Commit-Queue: Eric Orth <ericorth@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654642}

to the "Google" variants of the QUIC connection close error histograms.

Change-Id: I156dd9cff57fff298095ee692cf8da9f1a5a955d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585175Reviewed-by: Nik Bhagat <nikunjb@chromium.org>
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654641}

Bug: 841899
Tbr: thakis@chromium.org
Change-Id: I0761150154d6762609638a4abe0ca4523fde9769
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585958
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#654640}