GitLab

Set 'mix-blend-mode' to 'normal' on the stroked rects that make up the
"edge cover". Hopefully this avoids aliasing artifacts on the edge cover
itself.

In blending-002.svg, localize the use of (non-auto) isolation to the
content of the test.

BUG=866928

Change-Id: I269e01a4d814f7fd8e202ffdf71c1a1d5dc48347
Reviewed-on: https://chromium-review.googlesource.com/1175825Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#583277}

This change prevents a hang when connecting to a Windows machine
which has curtain mode and 3d display mode enabled.  The root cause
of the hang is that creating a D3D11 device takes several seconds so
function calls which used to take a few milliseconds now take 5+
seconds.  I did not see a mechanism to control this display mode
programatically so I am adding code which can detect the condition
and the logic to prevent D3D usage when 3D mode is enabled.

Of note is the change in BasicDesktopEnvironment where I requery the
D3D apis.  DesktopEnvironmentOptions are queried in Session 0 and
then passed on to the Desktop process.  There is a non-obvious
problem with this as many D3D methods cannot be queried or will
not return reliable results.  This results in a base set of options
being set in Session 0 (which includes user / experiment overrides)
and then passed into a session where D3D will return new values.  In
this CL, I requery the D3D APIs and update the capturer options if
they should be disabled.

BUG=836007

Change-Id: Ib7a6e61fa7987bd093e93a6100b97cc49e3aff05
Reviewed-on: https://chromium-review.googlesource.com/1164403
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583276}

Bug: 873826
Change-Id: I9381fb88efd83933e30d5c14050f50500f241469
Reviewed-on: https://chromium-review.googlesource.com/1175084Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583275}

See failure here:
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Mac10.13%20%28retina%29/1465

TBR=wjmaclean@chromium.org
NOTRY=true

Bug: 869726
Change-Id: Id5e2c77e6c6eb001dbd2c8fcd1b9d5e3df02fb66
Reviewed-on: https://chromium-review.googlesource.com/1176061Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583274}

Bug: 873178
Change-Id: I700d6d710474b356e32f58b435d78e7e24cfb0ff
Reviewed-on: https://chromium-review.googlesource.com/1174537Reviewed-by: Paul Jensen <pauljensen@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Peter Conn <peconn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583273}

API is upgraded.
Optional method calls are updated to check for nullptr first.

Change-Id: Ibfe5bfc6b8e1f34e138ec3b9efcab981911d8491
Reviewed-on: https://chromium-review.googlesource.com/1175098Reviewed-by: Aldo Culquicondor <acondor@chromium.org>
Commit-Queue: Amirhossein Simjour <asimjour@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583272}

See failure here:
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Mac10.13%20%28retina%29/1461

TBR=wjmaclean@chromium.org
NOTRY=true

Bug: 869726
Change-Id: Ia74cfb2b6dfcbf5b7ca2b331701d6e2453d9090d
Reviewed-on: https://chromium-review.googlesource.com/1175849
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583271}

Currently, assigning custom controls to a video through a call to
setPictureInPictureCustomControls() passes in the data but does not
show the buttons on the PiP window. This CL makes it so that up to 2
buttons are added to the PiP window on the left and the right of the
play/pause button when this call is made.

Note: the desired icon that is passed in is not currently being
assigned to these new buttons, and they are currently using the play
and pause icons as defaults, for left and right respectively. This
will be updated to work properly in a future patch - this is just to
get the basic functionality set up.

Bug: 864271
Change-Id: I42d9cf47dcd22dd481675b1990e1bb9ae2265055
Reviewed-on: https://chromium-review.googlesource.com/1139110
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: apacible <apacible@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583270}

Refactoring to support https://skia-review.googlesource.com/c/skia/+/147113

Change-Id: Ic4d430ed29b4edab3febab4a4fe811881b5617e1
Reviewed-on: https://chromium-review.googlesource.com/1175438Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Mike Reed <reed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583269}

https://skia.googlesource.com/skia.git/+log/49bb9c17d713..137ca523a36e


git log 49bb9c17d713..137ca523a36e --date=short --no-merges --format='%ad %ae %s'
2018-08-15 robertphillips@google.com Remove prePathMatrix from SkDevice::drawPath
2018-08-15 csmartdalton@google.com Consolidate the scissor enums into one "GrScissorTest" enum


Created with:
  gclient setdep -r src/third_party/skia@137ca523a36e

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=kjlubick@chromium.org

Change-Id: I818d430b5622960332e554fd4155b3e3cdb9bc3a
Reviewed-on: https://chromium-review.googlesource.com/1174803Reviewed-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@{#583268}

In addition to existing limit of 200 messages in a single task also
limit it to 50 milliseconds to avoid starvation.

This logic will be removed when message-per-task mojo dispatching
will be implemented.

This patch also modifies maps_pixel_test to use requestIdleCallback
for detecting the end of the page load instead of three requestAnimationFrames.

BUG=867133,872239
R=mek@chromium.org,kbr@chromium.org

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
Change-Id: Ib2de605bc6d069c23c3a991edcc0dccc995a4632
Reviewed-on: https://chromium-review.googlesource.com/1167053
Commit-Queue: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583267}

The documentation of UploadList's ctor mentions a parameter
which the ctor no longer appears to take.

Bug: None
Change-Id: I8656b0c76d684ee87c1baa26cd79104c7b50b358
Reviewed-on: https://chromium-review.googlesource.com/1174382Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Elad Alon <eladalon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583266}

This patch makes it possible to run Wayland backend with a separate gpu process.
That is, WaylandConnection is not available on the GPU process side
and so buffers cannot be created that way.

To overcome this, a Wayland dmabuf based approach is used:
 - On the gpu process side, gl::Surfaceless is used, which is
   implemented by GbmSurfaceless. It differs from the one provided by
   the Ozone/Gbm backend (the difference is that there are no frame
   buffers, because DRM render node is used instead.) Basically,
   on the GPU side, a gbm_bo buffer is created and its file descriptor is
   shared with the WaylandConnection, which then imports a wl_buffer and attaches
   it to a requested surface.

TL:DR;
 - There are two communicating parties - WaylandConnection, which establishes
   a connection with Wayland, and a WaylandConnectionProxy, which serves
   the GPU process with a forwarding mojo connection to the WaylandConnection.
   In single process mode, WaylandConnectionProxy just forwards calls to
   WaylandConnection, and GLSurfaceEGL is used. In a multi process mode,
   the l::Surfaceless and dmabuf based approach is used instead.

 - The communication is established in the following way:
   when WaylandConnectionConnector receives a OnGpuServiceLaunched,
   it binds WaylandConnection and WaylandConnectionProxy interfaces, and
   calls to WaylandConnectionProxy to set a mojo ptr to the WaylandConnection.
   The WaylandConnectionProxy receives the pointer, stores it and also stores
   a task runner to make sure mojo is called on the right sequence.

How buffers are created:
 - Basically, the GPU process doesn't know about Wayland. What it does
   is that it creates a GbmBuffer utilizing a DRM render node (it can't use
   a drm card device, because authentication requires master access), takes
   a gbm_bo file descriptor and shares it via a mojo call with the
   WaylandConnection, which then uses the zwp_linux_dmabuf interface to
   import a wl_buffer, which can be attached to a needed WaylandWindow
   and commit-ed to show contents. That is, the gbm framework is used to share buffers
   between the browser and the GPU process, where the browser process can read from them and
   the GPU process is able to read and write using gl commands.

How buffers are committed:
 - GbmSurfaceless uses a normal procedure and submits frames on
   SwapBuffersAsync call: a frame is created and scheduled as an overlay plane,
   once scheduling is done, a widget is taken from that pending plane and
   WaylandConnection::ScheduleBufferSwap is called. In order to specify, which
   wl_buffer must be used, gbm bo handle is used as a buffer id.
   Once the WaylandConnection receives a buffer swap call, it finds a buffer by a
   buffer id and attaches that buffer to a WaylandWindow, which is also found
   by a widget passed to it. PresentationCallback is not used and will be
   enabled in the future.

The missing feature is the software rasterization. That is, the gbm buffers cannot be
mmap'ed using unix mmap method. Thus, it's impossible to get a mapped memory range and let the cpu
write to it. I think this problem can be resolved in the downstream projects in different ways
but these solutions are not generic enough to be upstreamed.

Another missing feature is presentation feedback. This will be implemented in follow up
CLs.

COMPILE= compiles only with third_party minigbm now. For example, add use_intel_minigbm=true
if intel gpu is ozone_platform_wayland=true. Using system libgbm will be available soon.
TEST=run and compile ozone/wayland.
Bug: 820047

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
Change-Id: Id351edd9883a765d3e549543a50175299108c6ab
Reviewed-on: https://chromium-review.googlesource.com/1057468Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#583265}

This reverts commit b0490220.

Reason for revert: Breaks fuzzing builds: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Libfuzzer%20Upload%20Linux%20UBSan/20928

Original change's description:
> Update V8 to version 7.0.237.
> 
> Summary of changes available at:
> https://chromium.googlesource.com/v8/v8/+log/091d6f21..e756beb7
> 
> 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: I4d77df256a6f6a4a905a2b93e11a4c946a21ce30
> Reviewed-on: https://chromium-review.googlesource.com/1175700
> Reviewed-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@{#583252}

TBR=hablich@chromium.org,v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Ica5decafaab4827b642edd106a99165a2ddbcb83
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
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
Reviewed-on: https://chromium-review.googlesource.com/1174774Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583264}

This does not change the current working directory of the script, and
allows the subsequent 'git cl format' command to run in the correct
directory. (The 'git cl format' command was running in the "${SRC}"
directory incorrectly.)

If 'git cl format' fails, point out what command failed in the error
message. Allow the error output of 'git cl format' to be emitted.

R=johannkoenig@google.com,jzern@google.com

Change-Id: I18b7d8777a8ebb2cf09c32a35e7a5957fd1fa32a
Reviewed-on: https://chromium-review.googlesource.com/1169701
Commit-Queue: Wan-Teh Chang <wtc@google.com>
Reviewed-by: James Zern <jzern@google.com>
Reviewed-by: Johann Koenig <johannkoenig@google.com>
Cr-Commit-Position: refs/heads/master@{#583263}

The OverviewButtonTrayTests need to set the keyboard devices *after*
AshTestBase::SetUp() is called. This is is important in single-process mash
as Ash is the one creating the Env that the keyboard devices us. In
non-single-process-mash AshTestSuite is creating the Env these tests use.

The case ShellTest2.DontCrashWhenWindowDeleted is exercising is different
enough for single-process mash that I created a separate test.

Adding NOPRESUBMIT=true as this bot passed the trybots, and we're ok with
this test including Env::GetInstance().

NOPRESUBMIT=true

BUG=847992
TEST=test only changes
TBR=jamescook@chromium.org

Change-Id: I46fbfa9c78e8b28ac459b9863e34f3761a077c9a
Reviewed-on: https://chromium-review.googlesource.com/1175848
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583262}

Bug: 874047
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I627e2d5d51716d715699792946e8537f5d21ed09
Reviewed-on: https://chromium-review.googlesource.com/1174917Reviewed-by: edchin <edchin@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583261}

With the display-compositor moving into the gpu process, the shared
memory segment used for storing metrics needs to be larger. The UsedPct
metrics for the various processes are usually around 20-30%. But for
the gpu process with the display compositor, the usage shoots up to
~75% [1]. So increase the limit from 64K to 256K, to avoid overruns.

[1] https://uma.googleplex.com/p/chrome/variations/?sid=9dbcefdbd5a988d093ae8c4b66629c01

BUG=778749

Change-Id: I5328bae58ce9f031293ed01ccd2c011581daf853
Reviewed-on: https://chromium-review.googlesource.com/1173353Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583260}

aura::WindowObserver is invoked when an alpha shape is set for the
layer of a window.

In a future CL, aura::WindowOcclusionTracker will recompute occlusion
states when this method is invoked for a window in a tracked window
tree. Indeed, setting an alpha shape can affect occlusion.

Bug: 864508
Change-Id: If90d8cf143961655bc854d4217c867cc6d29e3be
Reviewed-on: https://chromium-review.googlesource.com/1173166Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583259}

Using wpt-import in Chromium ade2b1fa.
With Chromium commits locally applied on WPT:
7dad0f17 "Added new Sec-Metadata Web Platform Tests."


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/22762

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
bjonesbe@adobe.com:
  external/wpt/css/css-shapes
bugsnash@chromium.org, ericwilligers@chromium.org, meade@chromium.org, nainar@chromium.org, rjwright@chromium.org, shend@chromium.org:
  external/wpt/css/css-cascade
ericwilligers@chromium.org:
  external/wpt/css/motion
kojii@chromium.org:
  external/wpt/css/css-writing-modes
rego@igalia.com:
  external/wpt/css/css-ui

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa@intel.com

No-Export: true
Change-Id: I747f247d0701b131533058fcc71edc16ab78e16f
Reviewed-on: https://chromium-review.googlesource.com/1175841
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583258}

This change compiles Zucchini-apply into setup.exe this adds ~50 kB in
size (this works for raw, x86, and x64 PE file patches).

NOTE: this will not ship Zucchini patches yet but it makes setup.exe
capable of patching using Zucchini in addition to Courgette. The
release/diff infrastructure is configured so that Courgette and Zucchini
are used to generate patches in parallel; however, we will continue to
only ship Courgette patches to users. This will allow us to evaluate the
stability and benefits of Zucchini. Only after this evaluation period
will we begin the discussion of swapping over to Zucchini for the next
release (with Courgette as a fallback).

Bug: 729154
Change-Id: I3b9bc1f28f7c5a92fbe393e0d59bd9ac98946372
Reviewed-on: https://chromium-review.googlesource.com/1172445
Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Reviewed-by: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583257}

Notes:
1. The feature is hidden behind a switch enable-incognito-custom-tabs. Without it, the behavior should remain as before, i.e. only allow ICTs for payments flow.
2. ICT can be launched by adding extra com.google.android.apps.chrome.EXTRA_OPEN_NEW_INCOGNITO_TAB and only by first-party apps.
First-party apps also need to be maintaining a connection with CustomTabsService.
These limitations can be relaxed for testing purposes with the switch allow-incognito-custom-tabs-from-third-party.
3. The toolbar of ICT has grey theme color, and this can not be overriden by custom tab parameters.
4. ICT has menu item "Open in Incognito Chrome", which reparents the tab into Chrome. App picker is not shown.
Thus, unlike normal custom tabs, which either show an app-picker, or open default browser, ICT always opens Chrome.
5. "Close all incognito tabs" notification takes ICTs into account.
6. Taking screenshots of ICTs is not allowed, and no screenshots of them are seen in recents.

Bug: 871738

Change-Id: Ia5c7e9cd31bcacc5e8e30bc43d7b0f234ac007c4
Reviewed-on: https://chromium-review.googlesource.com/1171225
Commit-Queue: Pavel Shmakov <pshmakov@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583256}

This change ignores movements of less than 3px, which are small enough
to not be distracting.

It also adds an early exit for objects smaller than the jank region
granularity.  This is a performance optimization, since these objects
will not affect the jank region after snapping.

This should mostly eliminate JankTracker's impact on blink_perf.paint
benchmarks (already reduced by crrev.com/562327).

Bug: 581518,847252
Change-Id: I3979421e7a25654e67d3eeba7a2cd5d217ed3f03
Reviewed-on: https://chromium-review.googlesource.com/1175109
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583255}

This change:

1) Adds logic to EventMonitorMac so that if an event is marked handled by the
   client of EventMonitorMac, the event is not handled further - i.e.,
   EventMonitorMac can now eat events;
2) Renames the existing MenuPreTargetHandler to MenuPreTargetHandlerAura;
3) Adds MenuPreTargetHandlerMac which uses EventMonitorMac;
4) Adds MenuPreTargetHandler::Create to manufacture the platform-appropriate
   MenuPreTargetHandler instance.

Bug: 867127
Change-Id: I33f7c750598b0496fa291434098f8019e4b99c47
Reviewed-on: https://chromium-review.googlesource.com/1174568
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583254}

TBR=xidachen@chromium.org

Bug: 874370
Change-Id: Iefa082753ae148d2bd72a6a1925124d6360aa1a7
Reviewed-on: https://chromium-review.googlesource.com/1175844Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583253}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/091d6f21..e756beb7

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: I4d77df256a6f6a4a905a2b93e11a4c946a21ce30
Reviewed-on: https://chromium-review.googlesource.com/1175700Reviewed-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@{#583252}

Bug: 805612
Change-Id: I6887eeb37f88c94b2e53b4fa6b1aad8ed95f2b76
Reviewed-on: https://chromium-review.googlesource.com/1173251Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Weidong Guo <weidongg@chromium.org>
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583251}

See failure here:
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Win10/39305

TBR=wjmaclean@chromium.org
NOTRY=true

Bug: 832274
Change-Id: I085d84dedb9cb68814dc6c58dd71da7a1619468f
Reviewed-on: https://chromium-review.googlesource.com/1175846Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583250}

In GpuBenchmarking, for mouse wheel and touchpad scroll, we want to add
"has_precise_scrolling_deltas" scroll option to
GpuBenchmarking::SmoothScrollBy.


Bug: 871970
Change-Id: I456db492e2a7fdab35263efe931d089b400a9e3d
Reviewed-on: https://chromium-review.googlesource.com/1166165Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Sahel Sharify <sahel@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583249}

https://skia.googlesource.com/skia.git/+log/32c7d4dfcdca..49bb9c17d713


git log 32c7d4dfcdca..49bb9c17d713 --date=short --no-merges --format='%ad %ae %s'
2018-08-15 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 2363356f52f6..21e5e85a4976 (1 commits)
2018-08-15 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-08-15 bungeman@google.com Update CCPRGeometry to use pool for op.
2018-08-14 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-08-14 reed@google.com add tests for cubicmap
2018-08-14 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 35bc74d6d139..2363356f52f6 (1 commits)
2018-08-14 mtklein@google.com implement SkConvertPixels color xform with steps
2018-08-14 reed@google.com inline strcmp for faster json parsing
2018-08-14 bungeman@google.com Update FreeType to use isSubpixel and isVertical.
2018-08-14 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-08-14 brucewang@google.com Implement SubPixel mode support for FreeType COLR/CPAL
2018-08-14 robertphillips@google.com Remove unused parameter from drawPathWithMaskFilter
2018-08-14 fmalita@chromium.org [skottie] Eliminate some temp SkString allocations
2018-08-14 mtklein@google.com pass sprite opacity to color xform when blitting.


Created with:
  gclient setdep -r src/third_party/skia@49bb9c17d713

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=kjlubick@chromium.org

Change-Id: I085fe37fc263d923c45377767089449dca924f32
Reviewed-on: https://chromium-review.googlesource.com/1174802Reviewed-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@{#583248}

This reverts commit bea6537a.

Reason for revert: clusterfuzz found many issues
crbug.com/874396
crbug.com/874420
crbug.com/874431
crbug.com/874425
crbug.com/874430
crbug.com/874429
crbug.com/874423
crbug.com/874404

Original change's description:
> Change SMILTimeContainer::scheduled_animations_ to use ephemeron
> 
> WeakMember as part of a HashMap entry can cause unexpected clearing when incremental marking is enabled.
> 
> This CL changes SMILTimeContainer::scheduled_animations_ to use a epehemeron instead.
> 
> Bug: 870306
> Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
> Change-Id: I8b653825de0bc683a5151576385716141c78c454
> Reviewed-on: https://chromium-review.googlesource.com/1166753
> Commit-Queue: Keishi Hattori <keishi@chromium.org>
> Reviewed-by: Philip Rogers <pdr@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#583156}

TBR=pdr@chromium.org,haraken@chromium.org,keishi@chromium.org,mlippautz@chromium.org

Change-Id: Id727b6da2d0a42341bde5d9f6c2c9f32a43d447e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 870306
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/1175881Reviewed-by: Keishi Hattori <keishi@chromium.org>
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583247}

On pause when we get expression for popover we by mistake include
spread operator when we should not.

R=einbinder@chromium.org

Bug: chromium:797296
Change-Id: I9a5eaa5df045874ec82056081e01e4c4a308ae87
Reviewed-on: https://chromium-review.googlesource.com/1041276
Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Reviewed-by: Joel Einbinder <einbinder@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583246}

TBR=wjmaclean@chromium.org
NOTRY=true

Bug: 520736
Change-Id: I56a80554562d29ee0b638ed95e9d0e1e713105c2
Reviewed-on: https://chromium-review.googlesource.com/1175436Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583245}

Add function on perf_data_generator to keep the list of active platform
configurations in //docs/speed/perf_lab_platforms.md up to date.

Bug: 871746
Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi
Change-Id: I8d95651ad0480f7eb21b8aa6c95af5b75d37da94
Reviewed-on: https://chromium-review.googlesource.com/1166919
Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#583244}

This CL:
 - Creates a new feature/flag to allow customization of the text
   and background colors when a field shows an Autofill suggestion;
   Each color is defined by its own parameter in the study.
 - Moves the previous style from html.css and build the CSS rules
   instead in LayoutTheme::ExtraDefaultStyleSheet using either the
   colors defined by the parameters (when the feature is enabled)
   or the current preview colors as a fallback (default and
   invalid color cases).

Variations provided for the new chrome://flags entry correspond to
the experiment palletes proposed by UX (see details on the bug).

One alternative that I considered:
 - Define a single param in the study for the experiment group
   (so flag variations and param values would have a 1:1
   correspondence);
 - Define a separate CSS file for each variation, similar to what's
   currently done LayoutThemeDefault::ExtraDefaultStyleSheet.

That alternative would be less flexible, but it would be more
similar cases handled in blink (in fact, I couldn't find any place
where the CSS is built in the code). Please let me know if you think
that alternative should be used instead.

Bug: 874094
Change-Id: I257c72b9a3db32a2945ec4048e46b23e4b5dd2be
Reviewed-on: https://chromium-review.googlesource.com/1174710
Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583243}

TBR=chrishtr@chromium.org

Bug: 866165
Change-Id: I476ba02235677f81f76dc9899e01c6436d4c5aac
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1175828Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583242}

TBR=wjmaclean@chromium.org
NOTRY=true

Bug: 874417
Change-Id: Ide6bc7a1fd7d8cc25d96204a2e43f446d2782c3d
Reviewed-on: https://chromium-review.googlesource.com/1175842
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583241}

Bug: 874152
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester
Change-Id: I45441e5fdd8eaa4b0e39144cd94d610d3f98f368
Reviewed-on: https://chromium-review.googlesource.com/1174935
Commit-Queue: Paul Jensen <pauljensen@chromium.org>
Reviewed-by: Paul Jensen <pauljensen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583240}

Adds some mojo interfaces for configuring audio processing, intended for
both WebRTC and system-level echo cancellation, though the latter will
be less configurable.

There are two parts to this change:
1. AudioProcessingSettings in media/audio, used to configure audio
   processing when done in the audio service. At one point, the similar
   AudioProcessingParameters in content will be replaced by this one.
2. AudioProcessorControls in media/webrtc; an interface used to control
   auxiliary audio processor functionality, specifically getting stats
   and starting/stopping AEC dumps.

For an outline of the project this CL is part of, see: https://docs.google.com/document/d/1u4POff_ts_1LE3WDLA_wDDFnUswdlsuHL5DsiTE0a3U/edit?usp=sharing
It's accessible to everyone @chromium.org.

Bug: 851959
Tbr: tommi@webrtc.org
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
Change-Id: I0c8c934b35b93aa728a0d1b60ae76063e925ee6c
Reviewed-on: https://chromium-review.googlesource.com/1167848
Commit-Queue: Tommi <tommi@chromium.org>
Reviewed-by: Tommi <tommi@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583239}

TBR=wjmaclean@chromium.org
NOTRY=true

Bug: 874444
Change-Id: Idce66af34aa8a41d8cd300df559a48fca8409040
Reviewed-on: https://chromium-review.googlesource.com/1175699Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583238}