GitLab

https://chromium.googlesource.com/angle/angle.git/+log/e708f004bce5..03bb2231a821

$ git log e708f004b..03bb2231a --date=short --no-merges --format='%ad %ae %s'
2018-05-03 oetuaho Add test for D3D11 nested floor() bug

Created with:
  roll-dep src/third_party/angle
BUG=chromium:838885


The AutoRoll server is located here: https://angle-chromium-roll.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=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=cwallez@chromium.org

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

Change-Id: I7a3928869f8b585f4dabc6eba57b7206f2f03bef
Reviewed-on: https://chromium-review.googlesource.com/1041325Reviewed-by: Philippe Hamel <hamelphi@chromium.org>
Commit-Queue: Philippe Hamel <hamelphi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555823}

There are no existing tests (or any imported that I could find) that
verify captions' BFCs behave properly.

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I56398bdd1ab6b993eaf8898e09b8aaa4b0ce0100
Bug: 635619
Reviewed-on: https://chromium-review.googlesource.com/1041219
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555822}

MojoAudioDecoderService, MojoVideoDecoderService and MojoRendererService
already hold a CdmContextRef to make sure the CDM attached to them will
always be valid. This CL brings this model to MojoDecryptorService to
make the code consistent. This will be used in the next CL when we host
MojoDecryptorService in MediaService.

Bug: 806018
Test: No functionality change.
Change-Id: I4f8f2fa519b00722252d2110a58fe2e6c2f8d56c
Reviewed-on: https://chromium-review.googlesource.com/1041658
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555821}

This ignores the computation error introduced when mapping to and from
the common planar of the layer and the chunk while the relative
transform between the layer and the chunk doesn't actually change.

Bug: 814711
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ie97b425eb3de601107328513b611b3f8676afa73
Reviewed-on: https://chromium-review.googlesource.com/1040537Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555820}

This Cl cleans up a TODO to remove an extra Layout call in Invalidate.
The extra call was a workaround for shifting text. I've identified some
unnecessary calls to SizeToPreferredSize() that was shifting the text.

This change should not cause any user visual changes.

This change may improve time to paint metrics.

Bug: None
Change-Id: I253b28e32c02d744a1e3d3c58b2522c04eefb323
Reviewed-on: https://chromium-review.googlesource.com/1041151Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555819}

Remove an obsolete API that allows a crazy linker client to set
a library load offset. This was intended for loading libraries
directly from zip files, but was never used as is.

Besides, a future CL will refactor how libraries are located
and loaded from zip files in a completely different way (i.e.
adding the zip file path to the library search path).

BUG=802068
R=pasko@chromium.org, lizeb@chromium.org, agrieve@chromium.org

Change-Id: I33e2c1fe50a5a1accb42494f3a29a4d1128d5ea3
Reviewed-on: https://chromium-review.googlesource.com/1041963Reviewed-by: David Turner <digit@chromium.org>
Reviewed-by: Benoit L <lizeb@chromium.org>
Commit-Queue: David Turner <digit@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555818}

This is a precursor to having the loading parts of bookmarks create
the TitledUrlIndex. This should result in no change as the index is
only used once loaded.

BUG=680698
TEST=covered by existing tests

Change-Id: Ia059a26509f09472021bcfb31f24e9dcccd07d59
Reviewed-on: https://chromium-review.googlesource.com/1041528
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555817}

Also removes no longer needed guard flag for GrBackendObject.

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,linux_chromium_dbg_ng;master.tryserver.chromium.linux:linux_vr
Change-Id: I228f6bf5bcb554f6dcf31889c210ca2043f5a837
Reviewed-on: https://chromium-review.googlesource.com/1040425
Commit-Queue: Greg Daniel <egdaniel@chromium.org>
Reviewed-by: Brian Salomon <bsalomon@chromium.org>
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555816}

This CL removes a now-unneeded workaround for the old bug
https://crbug.com/476610 that would treat any proxy that responds with
the Data Reduction Proxy Via header as the Data Reduction Proxy, at
least for bypass/retry purposes. This workaround isn't needed anymore
since the root cause of that bug was found and there's code that fixes
the root cause of that bug at startup time (see
DataReductionProxyChromeSettings::
MigrateDataReductionProxyOffProxyPrefsHelper).

This CL also removes the associated histogram,
DataReductionProxy.ResponseProxyServerStatus.

Bug: 819066, 791849, 708029
Change-Id: Ica4e707866e0a81c17c3f6d3a27e068734e26744
Reviewed-on: https://chromium-review.googlesource.com/1040827Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Scott Little <sclittle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555815}

We prefer to paint background-attachment: fixed into the scrolling
contents layer if text quality is important (at the cost of repainting
on every scroll). This approach had a bug for the LayoutView if there
turned out to be no scrolling layer (e.g., in a non-composited iframe).
The counterscroll logic in FixedAttachmentPositioningArea should
only apply if actually painting into a scrolling layer. This patch
queries the background compositing state before applying the counter-
scroll. This is safe because it occurs during paint which is after the
compositing decisions have been made.

Bug: 835755
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ieebffb50579b28488ef802736dd1210b8b27b26d
Reviewed-on: https://chromium-review.googlesource.com/1036941Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555814}

This CL is a refactor with no intended behavior change.

Bug: 832879
Change-Id: I6d54051f50ed4b0c46f821872aafea1ba4b3fd32
Reviewed-on: https://chromium-review.googlesource.com/1040590Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555813}

https://boringssl.googlesource.com/boringssl/+log/cece32610b89549386b42b2032dd5d8a423af6c8..8e75ae488047c519f14f2c08b02a55bf7712fa1d

BUG=none

Change-Id: I36edb8ad89f019bddea940ca7b6433ea3d8ef86e
Reviewed-on: https://chromium-review.googlesource.com/1040588
Commit-Queue: Steven Valdez <svaldez@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555812}

Change-Id: I4185507af93c77d0e2514769dfbd66376591302f
Reviewed-on: https://chromium-review.googlesource.com/1042791Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555811}

Bug: 773295
Change-Id: Ibc2789d9d0202f4e36bbc88b472107a7d99e52bb
Reviewed-on: https://chromium-review.googlesource.com/1038244
Commit-Queue: Mark Pilgrim <pilgrim@chromium.org>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555810}

NOTRY=true  # tests are covered by CQ

Bug: 836446
Change-Id: I65548078aa4c280fa0be6f29ed236e41b4194ee3
Reviewed-on: https://chromium-review.googlesource.com/1042275Reviewed-by: Emily Hanley <eyaich@chromium.org>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#555809}

TL;DR for non-mojo reviews: No functional changes in your code. All
mechanical aesthetic changes.

This cleans up all message pipe, data pipe, and shared buffer APIs to
reflect the intended stable ABI of the initial mojo_core release, adding
extensible options structs where appropriate and homogenizing argument
ordering conventions. Also renames some badly named types and begins
eliminating the split C/C++ flag constant definitions in favor of using
C macros everywhere.

Documentation formatting is also made more consistent, and the thunk
table ordering is mostly finalized here.

The only functional change is a small drive-by bugfix in
MojoGetBufferInfo where the implementation was not filling in the actual
size of the MojoSharedBufferInfo struct. This has no effect on any
current production uses of the API.

TBR=miu@chromium.org
TBR=jam@chromium.org
TBR=kinuko@chromium.org

Bug: 819046
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I5c1019bf1fe95a9295a0d053544e867fdebadde8
Reviewed-on: https://chromium-review.googlesource.com/1041149
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555808}

In ContentViewRenderView, waiting an extra frame to remove the
background prevents flashes of black from Android's default Surface
content, and flashes of the compositor's default background.

Bug: internal b/73804884
Test: repro bug
Change-Id: Ib221403890200be6e842e0d85780d18db859d159
Reviewed-on: https://chromium-review.googlesource.com/1041185Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Thoren Paulson <thoren@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555807}

PaintLayer::GetBackgroundPaintLocation returns a mask of where the
background should paint and is used for determining if composited
scrolling can occur at all through:
PaintLayerScrollableArea::ComputeNeedsCompositedScrolling.

If composited scrolling is not used, callsites handle not actually
painting onto the scrolling contents layer, see:
CompositedLayerMapping::UpdateBackgroundPaintsOntoScrollingContentsLayer

This patch breaks the dependency cycle introduced by [1]. Instead of
querying compositing state, this patch special-cases the root layer
so that kBackgroundPaintInScrollingContents can be returned even if
there is no overflow because the root layer creates scrolling contents
layers in this case.

[1] https://crrev.com/9e0775c12ad12

Bug: 835755
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I139f2f85c68d267de80c7b1e534a9fcef9af3983
Reviewed-on: https://chromium-review.googlesource.com/1042529Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555806}

|childWindowsDidChange| was removed from the delegate, so these methods
are now noops.

Change-Id: I5becdd5797c0adc14a9c2f53d0f78d5ce684ceea
Reviewed-on: https://chromium-review.googlesource.com/1040946Reviewed-by: Sidney San Martín <sdy@chromium.org>
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555805}

It has another cert for OCSP tests not used by the EmbeddedTestServer.

Bug: 755309
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ic43314cf9f8e2978848a75764a4323ce34b0006a
Reviewed-on: https://chromium-review.googlesource.com/1033192
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555804}

Updates to the media_router WATCHLIST:
- Add c/b/ui/media_router/
- Fix the path for c/common/media_router/

Change-Id: I286bbae96da0f801997e69634642a19001e46ac6
Reviewed-on: https://chromium-review.googlesource.com/1042276Reviewed-by: Adam Parker <amp@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555803}

Since b66db7c4, WebView can now get the
channel. Variations uses this to filter experiments.

Stand-alone WebView will report "unknown" channel. Experiments which do
not specify any channel will apply to stand-alone WebView; see
CheckStudyChannel in study_filtering.cc.

BUG=758290

Change-Id: I6174b63c6995cb950e5ec349891ad579d24e7396
Reviewed-on: https://chromium-review.googlesource.com/1041206Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Paul Miller <paulmiller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555802}

TBR=nednguyen@google.com
NOTRY=true

Bug: 839494
Change-Id: Idd671cbbf0cdd81f7a3417573d03e4e6cda6e4c6
Reviewed-on: https://chromium-review.googlesource.com/1042282Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555801}

Bug: 598073

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I59722f8aa6c1946c3f2cf00bbbad0d8c96e0d12f
Reviewed-on: https://chromium-review.googlesource.com/1041486Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555800}

In crrev.com/c/1013221, we want to disable TouchpadOverscrollHistoryNavigation
on Windows and Linux. But we also disable it on CrOS because I forgot checking
OS_CHROMEOS. In this patch, we enable TouchpadOverscrollHistoryNavigation on
OS_CHROMEOS which is same as today stable.

TouchpadOverscrollHistoryNavigation is Aura only, OS_MACOSX does not check
this flag.

Bug: 838741
Change-Id: Ib9362bc74af1cb800fab665079017fbcb7880402
Reviewed-on: https://chromium-review.googlesource.com/1039867Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Jianpeng Chao <chaopeng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555799}

TBR=nednguyen@google.com
NOTRY=true

Bug: 839470
Change-Id: I7010d53bfdc84b9ac540735df8be060c9e5c2735
Reviewed-on: https://chromium-review.googlesource.com/1042279Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555798}

Add a third earcon for dictation cancelled, and modify which earcon
plays when so the user is more aware of the current dictation state.

Bug: 801398
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I3af2dd619e493e7697be5b5628539d9f6a56c7f1
Reviewed-on: https://chromium-review.googlesource.com/1040364Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Zach Helfinstein <zhelfins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555797}

Known issues:
 * Skia doesn't support creating promise image from YUV textures.
   https://crbug.com/skia/7902
 * Skia doesn't support drawing YUV textures directly, we have to
   convert YUV textures to a RGB textures first. https://crbug.com/skia/7901
 * Skia doesn't support alpha channel for YUV format.
   https://crbug.com/skia/7903

Test: Test it with YouTube
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;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Ia9fdc3d3ce972035025d3aec3813eef97619c6ed
Reviewed-on: https://chromium-review.googlesource.com/1003228Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555796}

These policies are intended to allow developers to control which image
formats are supported on their pages (and on the pages they embed,) and
to enforce that images used are well compressed and not full of
metadata which does not contribute to the displayed image.

Explainers for these features can be found at
https://github.com/WICG/feature-policy/blob/gh-pages/policies/optimized-images.md

Bug: 837348, 837350
Change-Id: Ie92517291a453286ca0d745f8dc497f040c06592
Reviewed-on: https://chromium-review.googlesource.com/1033726Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555795}

Part of ongoing effort to get automation tree working
in chromecast.

PS 1 is baseline for copied files. Modifications on top
of that in PS >=2.

Bug: 73383411
Test: None
Change-Id: I30328354dd523f1dc5aadbf7eda708e6be4ba5d2
Reviewed-on: https://chromium-review.googlesource.com/1035447Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Randy Rossi <rmrossi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555794}

Bug: 814860
Change-Id: I53c9de7111efb35e73317245647e3659e3bc4a6d
Reviewed-on: https://chromium-review.googlesource.com/1040271
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555793}

The raw pointer returned by GetNetworkContext() shouldn't be hold onto. This
CL adds documentation to the method and fixes devtools_server.cc to not hold
onto the raw pointer as a member.

Bug: 821000
Change-Id: If6e1a7c9a6742980755ffabd4c3b0d8fe0fa392e
Reviewed-on: https://chromium-review.googlesource.com/1042352Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555792}

This Cl is the first in a 3 CL series to move the NavigationRequest
creation to the NavigationController. The end goal is to have Navigator
take a NavigationRequest as an argument to Navigate instead of the
pending NavigationEntry.

Summary of the changes in this CL:
1) Navigator
 - NavigatorImpl::RequestTransferURL becomes NavigateFromFrameProxy. It calls
   NavigationControllerImpl::NavigateFromFrameProxy instead of creating a
   NavigationEntry and navigating to it directly.
 - NavigatorImpl::NavigateNewChildFrame becomes
   StartHistoryNavigationInNewChild. It calls
   NavigationControllerImpl::StartHistoryNavigationInNewChild instead of creating
   a NavigationEntry and navigating to it directly.

2) NavigationController:
 - StartHistoryNavigationInNewChild is a new function that contains code that
   used to be in NavigatorImpl::NavigateNewChildFrame. It is called when creating
   a subframe during a history navigation. It will try to perform a history
   navigation in the child frame.
 - NavigateFromFrameProxy is a new function that contains code moved from
   NavigatorImpl::RequestTransferURL. It creates a NavigationEntry and a
   NavigationRequest for the navigation, and asks the Navigator to perform them.

Bug: 803859
Change-Id: I45891c21dc8f1e86e3f1bc1829ee3a92af1a5bfb
Reviewed-on: https://chromium-review.googlesource.com/959012
Commit-Queue: Camille Lamy <clamy@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555791}

https://webrtc.googlesource.com/src.git/+log/01042067beb1..a1f566b28a69

$ git log 01042067b..a1f566b28 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc
BUG=chromium:838672,chromium:None,chromium:755920


The AutoRoll server is located here: https://webrtc-chromium-roll.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.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

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

This prevents builders of different archs from overwriting each
other.

Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester
Change-Id: I5a1e88601e0872e51282d52bb5151fcedd02ab3b
Reviewed-on: https://chromium-review.googlesource.com/1042354Reviewed-by: Andrei Kapishnikov <kapishnikov@chromium.org>
Commit-Queue: Paul Jensen <pauljensen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555789}

When the target element of a paint worklet has an associated link, then
the 'paint' function will be invoked when the link's href is changed
from a visited URL to an unvisited URL (or vice versa).

This CL changes the behavior by detecting whether the target element
of a paint worklet has an associated link or not. If it does, then don't
paint.

TBR=haraken@chromium.org

Bug: 835589
Change-Id: I5fdf85685f863c960a6f48cc9a345dda787bece1
Reviewed-on: https://chromium-review.googlesource.com/1035524Reviewed-by: Xida Chen <xidachen@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555788}

Add a browser test for extension updater when an extension is uninstalled
in the middle of an update session.

This is to verify changes in https://chromium-review.googlesource.com/1033468
and https://chromium-review.googlesource.com/1037906.

Bug: 837371
Change-Id: I9754b21b0afb67b158c2b36b795898fb584d432e
Reviewed-on: https://chromium-review.googlesource.com/1041161
Commit-Queue: Minh Nguyen <mxnguyen@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555787}

TouchscreenScroll user action used to show the frequency of GSBs
with touchscreen source; it's not needed anymore since the performance
scrolling metrics for ScrollBegin show the frequency.

Bug: 838700
Change-Id: If74fc0ad2cda1ac4e2a3ae14939b04e468b2b35d
Reviewed-on: https://chromium-review.googlesource.com/1017015Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555786}

https://chromium.googlesource.com/catapult.git/+log/a87e87c2a7f4..19282cf9d32d

$ git log a87e87c2a..19282cf9d --date=short --no-merges --format='%ad %ae %s'
2018-05-03 simonhatch Dashboard - Remove find_change_points_exp
2018-05-03 nednguyen Update method names in cache_temperature_unittes to be consistent with Telemetry code style

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-roll.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.


TBR=sullivan@chromium.org

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