GitLab

Currently SelectableItemView contains the logic for selection as well as
highlighting the UI. Separated the selection functionality into a base
class since in the new download home, different types of views will
implement different UI for selection.

Also added the ability to insert a RecyclerView into the SelectableListLayout
since in the download home the main view is created separately in DateOrderedListView.

The actual wiring will be in a follow up CL.

Bug: 850601
Change-Id: I33b1e68b27d6103d57c82322e5231dddfb6fd112
Reviewed-on: https://chromium-review.googlesource.com/1137332
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575809}

Bug: 863845
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I5da18cebf49709c6499bba94ea82bfabbef5a773
Reviewed-on: https://chromium-review.googlesource.com/1140510
Commit-Queue: Esmael El-Moslimany <aee@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575808}

This cl implements a new feature to read the latest opened
foreign tab on Chrome OS.

Bug: 843839
Test: manual.
Change-Id: Iab5e9e5eb092d8103497492c9f88bc79e323e9b5
Reviewed-on: https://chromium-review.googlesource.com/1134485
Commit-Queue: Tao Wu <wutao@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Jenny Zhang <jennyz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575807}

QUIC Connection Migration: do not check non-migratable streams when starting to probe an alternative network.

Instead, check and reset non-migratable streams when probe is successful and session is about to migrate to the probed path.

Bug: 791886
Change-Id: Icdff9b77d340fedbf64ab8e8eb05d1d99aaf0b65
Reviewed-on: https://chromium-review.googlesource.com/1139314
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575806}

This reverts commit dab53435.

Reason for revert: Couldn't reproduce the test failure on a local Win7
and the failure seems unrelated to my change. Try to submit it once more
and will investigate it further if it fails again.

Original change's description:
> Revert "Snaps after scrollbar clicking."
>
> This reverts commit e98df9c6.
>
> Reason for revert: suspect for webkit_layout_tests consistently
> failing, e.g.
> https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20Tests%20%281%29/81791
>
> Original change's description:
> > Snaps after scrollbar clicking.
> >
> > After user clicking on the scrollbar's track or arrows, we should snap
> > to the closest snap position of the container. This is done by simply
> > moving SnapAfterScrollbarDragging() from
> > ScrollableArea::MouseReleasedScrollbar() up to Scrollbar::MouseUp().
> >
> > This patch also rewrites the previous
> > snaps-after-scrollbar-dragging.html test using the gesture-util.js, and
> > adds the new clicking tests to it as well.
> >
> > Bug: 860768
> > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
> > Change-Id: I75267c3fc0917ecf5c14673a1eb480a047d03824
> > Reviewed-on: https://chromium-review.googlesource.com/1127153
> > Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
> > Reviewed-by: David Bokan <bokan@chromium.org>
> > Reviewed-by: Majid Valipour <majidvp@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#575191}
>
> TBR=bokan@chromium.org,majidvp@chromium.org,sunyunjia@chromium.org
>
> Change-Id: Iab3c3c489bda0fc6b150ba0e0a5bde8de9721798
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 860768
> Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
> Reviewed-on: https://chromium-review.googlesource.com/1138013
> Reviewed-by: Mikel Astiz <mastiz@chromium.org>
> Commit-Queue: Mikel Astiz <mastiz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#575202}

TBR=bokan@chromium.org,majidvp@chromium.org,sunyunjia@chromium.org,mastiz@chromium.org

Change-Id: Iaef646348cc6e1c0a6e8b0bca3deb9296f79a7e7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 860768
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Reviewed-on: https://chromium-review.googlesource.com/1138473
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Reviewed-by: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575805}

ServerGpuMemoryBufferManager is updated to support changing the GPU
service it is using, in case GPU process is crashed and restarted. If
this happens, it will retry pending allocation requests as soon as the
new GPU service is available.

BUG=733482

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I56fa97c7b74ec71d7e7a18e0e3036ffd7350e296
Reviewed-on: https://chromium-review.googlesource.com/1132679
Commit-Queue: Mohsen Izadi <mohsen@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575804}

-webViewSecurityFeaturesDidChange is meant to update the SSL status of
the last committed item. With WKBasedNavigationManager, on a back/forard
navigation, there exists a small window between web view starts loading
and -webView:didStartProvisionalNavigation is triggered that
WKBasedNavigationManager::GetLastCommittedItem() returns the pending
item instead of the last committed item.
-updateSSLStatusForCurrentNavigationItem must not be called in this
window, otherwise the wrong navigation item will be used.

Bug: 842151
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I57eb96f74c3a6a133b1fdad6559de093f5d125c5
Reviewed-on: https://chromium-review.googlesource.com/1141054
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575803}

Bug: 775644
Change-Id: I2e1558710c665322c1cbba93ed20176f6be83667
Reviewed-on: https://chromium-review.googlesource.com/1136984
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575802}

Change-Id: I29978aa75fe2a71490cdcb1fcc78e47ac672f185
Reviewed-on: https://chromium-review.googlesource.com/1141094Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#575801}

The SelectToSpeak class is messy and should be refactored to separate
the input handling, state logic, and output handling. This is the first
part of that refactor.

Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: If53dc7f85b223641e82533c82ab89aa50719d198
Reviewed-on: https://chromium-review.googlesource.com/1136842
Commit-Queue: Katie Dektar <katie@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575800}

And changes ws2 to ensure client is notified when scale-factor changes.
The conversion from ScreenProviderObserver to associated interface is to
ensure the ScreenProviderObserver is notified *before* the bounds change
because of scale-factor. To do otherwise means the client might use the wrong
scale-factor.

BUG=862409
TEST=none

Change-Id: I78333dcabe3e4adb1e2091cba784d53d9c27be1a
Reviewed-on: https://chromium-review.googlesource.com/1138866Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575799}

Point various OWNERS files for Cloud Print code to //cloud_print/OWNERS.

Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I0ba92831f62904415c5d5f4ddf8fcf0335e301b8
Reviewed-on: https://chromium-review.googlesource.com/1141072Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575798}

NetworkChangeNotifier::IPAddressObserver is being deprecated.
This CL migrates CloudPolicyRefreshScheduler to use NetworkChangeObserver
instead.

Bug: 754695
Change-Id: I4a3c1dd2320151ae78e504d732e6b67cec9bc78b
Reviewed-on: https://chromium-review.googlesource.com/1133333Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Lily Houghton <lilyhoughton@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575797}

ServiceWorkerProviderHost destructor destroys ServiceWorkerVersion,
which destroys ServiceWorkerEventDispatcher which some Mojo interfaces
are associated with. Namely, it causes ServiceWorkerObjectHost and maybe
ServiceWorkerRegistrationObjectHost's Mojo connection error handlers
to be invoked during ServiceWorkerProviderHost's destructor. The
error handlers attempt to use the halfway destroyed
ServiceWorkerProviderHost. Fix things by explictly destroying
the hosts in the destructor.

No test because I don't see a good way to test this.

Bug: 854993, 838410
Change-Id: I62f057c641738fa3ed9b780550fd3d4b730ef98a
Reviewed-on: https://chromium-review.googlesource.com/1139850Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575796}

This patch changes the size at which close buttons disappear from being
approximately 48 dips of content area to being a fixed constant. As a
first pass I've set the constant to 68 dips, which feels good to me.

This patch also ties the logic for when to show extra left padding to
the close button visibility, which addresses cases where the favicon
would "twitch" due to the alert indicator appearing.

Bug: 853788, 863027
Change-Id: I681f8b7d530b192f2fd5943436ae16bd93f33fba
Reviewed-on: https://chromium-review.googlesource.com/1125315Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575795}

This changes the default HTTPS security indicator to drop the "Secure"
verbose chip and only show the lock icon (for non-EV HTTPS).

This also updates the flag groups from crbug.com/803138 to account for
the new default, and add a "holdback" condition. The SecurityIndicatorTest
tests are updated to match.

Bug: 864606
Change-Id: I08acd2dc9431f8b70d6f932c977a831111d08e75
Reviewed-on: https://chromium-review.googlesource.com/1140674Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Christopher Thompson <cthomp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575794}

There are 3 changes make in overflow-scrollability.html:

1. update tests to use testharness.js
2. call rAFs before start input
3. use promise_test and gpuBenchmarking events

This should fix the overflow-scrollability.html flaky on virtual/threaded
test suites.

Bug: 841567
Change-Id: Ic098832a3ce685774d204d245f61809edee4a60b
Reviewed-on: https://chromium-review.googlesource.com/1131834Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Jianpeng Chao <chaopeng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575793}

This is a reland of 73716e90

Original change's description:
> Add histogram to measure usage of '#' in WebView loadData APIs
>
> The goal is to compare how often this histogram is logged with the
> existing kDataUriHasOctothorpe UseCounter for WebView, in order to
> determine what API path we might want to modify when doing a compat
> fix. The belief is that the histogram and UseCounter should be
> roughly comparable because the histogram will only be recorded at most
> once per site load (because the loadData APIs cause a site load).
>
> Bug: 823666
> Change-Id: I0ce63b8c86bc3bcd02d3b10ab7a38112fb520439
> Reviewed-on: https://chromium-review.googlesource.com/1112045
> Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
> Reviewed-by: Bo <boliu@chromium.org>
> Reviewed-by: Timothy Dresser <tdresser@chromium.org>
> Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#575268}

Bug: 823666, 864152
Change-Id: I7cbd818a9a427ab9497aa51bc1df8e91b38dc295
Reviewed-on: https://chromium-review.googlesource.com/1138893Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575792}

Change-Id: Ia24af4265badb67284c4151af813559ed7fbf7c1
Reviewed-on: https://chromium-review.googlesource.com/1140779
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575791}

In order to prevent Referrer chains from looping, add a timestamp
argument to both FindNavigationEvent and FindRetargetingNavigationEvent.
Then only allow the next event if it precedes the previous event
chronologically.

Bug: 864234
Change-Id: Ie5752096eb2571ecf24bdf22057ebc5c4d87adbd
Reviewed-on: https://chromium-review.googlesource.com/1141058Reviewed-by: Jialiu Lin <jialiul@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575790}

The code for initializing the memory mapping from a ruleset file was
not properly checking for IO errors from lower level mmap utilities.

This CL accounts for that by adding a factory method to
MemoryMappedRuleset which returns nullptr if initializing the memory
mapped file fails. This is tested via a global boolean which simulates
mmap failures by always returning nullptr from the factory method.

Bug: 734102
Change-Id: Id9372d09c0c1abdd4eb26a6486a84e11cd7cc245
Reviewed-on: https://chromium-review.googlesource.com/1138336
Commit-Queue: Asanka Herath <asanka@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575789}

Bug: None
Test: None
Change-Id: I18651c7a5aae4535cf0c7b652e68735126b3fe6c
Reviewed-on: https://chromium-review.googlesource.com/1139111Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Muyuan Li <muyuanli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575788}

Renamed targets under //webrunner as follows:
  service_unittests -> webrunner_unittests
  runner_pkg -> webrunner_pkg
  runner_exe -> webrunner_exe
  runner -> webrunner

Bug: 852145
Change-Id: Id92d021d29e7fada81153d70440b6376052e3abd
Reviewed-on: https://chromium-review.googlesource.com/1138992Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575787}

Bug: 837501
Change-Id: I2c3473b7198a3f8a172552dfda07b91fec19f5da
Reviewed-on: https://chromium-review.googlesource.com/1136020Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Quan Nguyen <qnnguyen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575786}

InspectorDOMSnapshotAgent: expose and book layout nodes owned by pseudo elements under their owners.

Currently, only support before, after and first letter pseudo types.

Change-Id: Ifb10fecad1dbfb6b987eaa0bd0e7ccb4a222d13f
Reviewed-on: https://chromium-review.googlesource.com/1125511
Commit-Queue: Hidy Han <hidyhan@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575785}

The new names for the affected bots are:
  mac10.13_retina-blink-rel
  mac10.13_retina-blink-rel-dummy
  WebKit Mac10.13 (retina)

Bug: 863070
Change-Id: I0a9cfb1e0378f6fe2f900c84e0d73c16f1094d8d
Reviewed-on: https://chromium-review.googlesource.com/1136883Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575784}

https://skia.googlesource.com/skia.git/+log/b609e6dc6a02..3229e65886a0


git log b609e6dc6a02..3229e65886a0 --date=short --no-merges --format='%ad %ae %s'
2018-07-17 jvanverth@google.com Revert "Add some optimizations to PolyUtils"
2018-07-17 ziadb@google.com SkAR Java: drawing planes as paths
2018-07-17 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-07-17 jvanverth@google.com Add some optimizations to PolyUtils
2018-07-17 kjlubick@google.com Add SkFloat2Bits and Region stub
2018-07-17 caryclark@google.com build for gdb on linux
2018-07-17 caryclark@skia.org fix bookmaker build bot
2018-07-17 robertphillips@google.com Restore SkLightingShader and associated classes
2018-07-17 allanmac@google.com Bug fixes and improvements to SKC and HotSort.  Vulkan is WIP.
2018-07-17 caryclark@skia.org remove unused untested parts of text blob
2018-07-17 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 6fb8ba4e8660..d691aeeb956f (1 commits)


Created with:
  gclient setdep -r src/third_party/skia@3229e65886a0

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

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=master.tryserver.blink:linux_trusty_blink_rel;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=bungeman@chromium.org

Change-Id: I8680e0eeffa0615b25d1b0e5c8767c4ba199f02f
Reviewed-on: https://chromium-review.googlesource.com/1140417Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#575783}

Chrome-side change. Logs CL: http://cl/200254698

Bug: 849781
Change-Id: I4348263c7e7bbfb868626141bc6a142cb738375d
Reviewed-on: https://chromium-review.googlesource.com/1102165
Commit-Queue: Nathan Parker <nparker@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Tim Schumann <tschumann@chromium.org>
Reviewed-by: vitaliii <vitaliii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575782}

Bug: 859742
Change-Id: Ia6c15fac08867ccd81556e1cdf7e1b45620069a4
Reviewed-on: https://chromium-review.googlesource.com/1138991Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575781}

Since the downstream P code are upstreamed, this class becomes no-op.

part 1: http://crrev/c/1138815

Bug: 850652
Change-Id: Idfda4ec1cd583159fdabf8c1fedc35cf752c9099
Reviewed-on: https://chromium-review.googlesource.com/1137105
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575780}

Identical blocks are not forgotten across drains now.  Added test as well.

R: pmonette@chromium.org
Test: chrome_elf_unittests.exe, ThirdParty*
Bug: 769590
Change-Id: I1d3b7db15128746c25e6d8bcfce8f39d2251d67f
Reviewed-on: https://chromium-review.googlesource.com/1140512
Commit-Queue: Penny MacNeil <pennymac@chromium.org>
Reviewed-by: Patrick Monette <pmonette@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575779}

It appears to be unneeded and it causes the fast/css/opacity-float.html
LayoutTest to fail.

Bug: 689306
Change-Id: I704a22a40fbdbfbb9fd98d6676ec0ce244d4a0ee
Reviewed-on: https://chromium-review.googlesource.com/1140208Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575778}

Forcing LayerTreeHostImpl to always swap shouldn't be necessary for the
browser UI compositor anymore. LayerTreeHostImpl has been changed to
always submit a CompositorFrame if the set of referenced surfaces has
changed.

It appears |must_always_swap| isn't necessary for layout tests either as
they still pass without it.

Bug: 851616
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I032264a23ba3b8c880f10d777cbe7b24372f0347
Reviewed-on: https://chromium-review.googlesource.com/1136804Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575777}

This CL updates TableViewEmptyView to use NSAttributedStrings rather
than using the UILabel equivalents.  This allows ChromeTableView
subclasses to define custom text styling if necessary.

Bug: 851962
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ib41dedfcb659ddfbe974db7d88b8867d6d9d5c20
Reviewed-on: https://chromium-review.googlesource.com/1135760Reviewed-by: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575776}

This upstreams text-target.html, as well as a change to
client-rect.html. This also deletes the non-WPT copy of these
tests to avoid unnecessary test duplication.

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ic53b3be66ffa2b2dd5b77105eb2c8e02181bac81
Reviewed-on: https://chromium-review.googlesource.com/1136939Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Ali Juma <ajuma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575775}

dproy@ added histograms for longest input delays and timestamps in
http://crrev.com/c/1084058: this CL does the same for general input delays.

R=tdresser@chromium.org,rkaplow@chromium.org
CC=​​dproy@chromium.org

Bug: 862389
Change-Id: I4453b0b7338101098ca4521100abe3293add45c0
Reviewed-on: https://chromium-review.googlesource.com/1132108Reviewed-by: Steve Kobes <skobes@chromium.org>
Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575774}

https://chromium.googlesource.com/deps/inspector_protocol/+/0d4255502019144a5dec5669d7992165ae8924e7

Change-Id: I6a0f2fe8aae5cc79b7b01127c2d05cf296209e51
Reviewed-on: https://chromium-review.googlesource.com/1139098Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Johannes Henkel <johannes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575773}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/b1e14adb..3df683e6

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I29d40266031f416da6259fed1ca419b52169ec53
Reviewed-on: https://chromium-review.googlesource.com/1140687Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#575772}

Bug: 830892
Change-Id: Id148e1503564e86f220a6a775aa9055294e465b1
Reviewed-on: https://chromium-review.googlesource.com/1140198Reviewed-by: Joe Mason <joenotcharles@chromium.org>
Commit-Queue: Oliver Li <olivierli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575771}

This will be used in a subsequent CL to change the HTTP RTT
estimate of the count of end to end RTT observations is more than
a certain threshold.

Change-Id: I4268568e2c7df0c45651fdecb19ba59925430565
Bug: 834119
Reviewed-on: https://chromium-review.googlesource.com/1117771Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575770}