GitLab

https://chromium.googlesource.com/external/github.com/google/googletest.git/+log/045e7f9ee4f9..08d5b1f33af8

$ git log 045e7f9ee..08d5b1f33 --date=short --no-merges --format='%ad %ae %s'
2018-05-09 jaeheonlee Use NULL instead of nullptr, for pre-C++11 builds.
2018-05-07 jaeheonlee Fix the bug where ad_hoc_test_result() functions of UnitTest and TestCase objects would return failures registered at TestCase and UnitTest scopes, respectively.

Created with:
  roll-dep src/third_party/googletest/src

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;master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.chromium.win:win_chrome_official;master.tryserver.chromium.linux:linux_chromium_cfi_rel_ng
Change-Id: Ifb056d881111f364644cd76331e833961ad9042d
Reviewed-on: https://chromium-review.googlesource.com/1061579Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559156}

This fixes the issue when ARC++ window goes in/out full-screen or
minimized/restored. In this case a window is removed deep inside
the top ARC++ window and this triggers the wrong logout time
activation.
On removing l
This CL checks removing window that belongs to tracked top windows and
ignored hierarchy change events for other child windows.

Test: Manually + unit test
Bug: b/79169326
Change-Id: I825dd9d16d32ce305d43003fb2e77194cfc5ca7c
Reviewed-on: https://chromium-review.googlesource.com/1045827
Commit-Queue: Yury Khmel <khmel@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559155}

https://chromium-review.googlesource.com/c/chromium/src/+/818075
moved the chromium.clang waterfall to generated json files.  It tried
to match the existing waterfall setup, but the difference in tests
wasn't really intentional (and I was on leave when that change happened
and nobody else familiar with the waterfall was cc'd on that change),
so undo most of the exceptions added there.

While here, also remove now-nonexistent bot 'ThinLTO Linux ToT',
and latency_tests to 'Linux Tests', run nacl_helper_nonsfi_unittests
on 'Linux Chromium OS ASan LSan Tests (1)', and metrics_python_tests
on 'Win7 Tests (dbg)(1)'.

On chromium.clang, adds
- nacl_helper_nonsfi_unittests
- services_unittests
- viz_unittests
- blink_heap_unittests
- blink_platform_unittests
- crashpad_tests
- webkit_unit_tests
- wtf_unittests
- net_unittests
- components_browsertests
- extension_browsertests
- gn_unittests
- native_theme_usertests
- nacl_loader_unittests
- storage_unittests
- latency_unittests
- mac_installer_unittests
- content_shell_crash_test
- metrics_python_tests
- device_unittests
- views_unittests
on at least one of the bots.

Most of these should pass at least, and since they run on swarming
hopefully they won't slow down the bots too much. Maybe I'll have
to undo some of this again as a follow-up though.

Bug: 843511
Change-Id: I3b6f0619c97d86d8768d10572a3c8beca20cea67
Reviewed-on: https://chromium-review.googlesource.com/1060293
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559154}

We no longer need Narrow dropdown UI experiment because it's been
adopted as part of the Material Refresh spec.

Bug: NONE
Change-Id: Iaf33efbd7e6f86321956290165d13dad69272c48
Reviewed-on: https://chromium-review.googlesource.com/1056148
Commit-Queue: Tommy Li <tommycli@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559153}

This adds a new component //gpu/vulkan/init that fills the same role as
//ui/gl/init. It will allow ozone ports to provide the factory functions
for surface types while still having a centralized entry point for
initializing vulkan.

Certain factory functions (e.g. VulkanSurface::CreateViewSurface) moved
into a new VulkanImplementation factory object; platforms override those
functions in order to build the right surface type.

Common code for surface creation moved into VulkanSurface from its single
anonymous subclass (VulkanWSISurface). This means VulkanSurface is not a
pure interface anymore, but neither are any of the other wrapper classes.
We could alternatively keep the pure interface and provide a "base"
subclass to inherit from, but it's not clear that such a separation is
useful.

This also removes the VkInstance from the global scope. Nothing depended
heavily on the fact that it was global, and since the vulkan API supports
instancing of vulkan itself, it seems better to pass the instance
directly into any components where it is needed. This makes any sharing
explicit and makes instancing possible. Also, the VkInstance could not
previously be destroyed, but now this is supported and exercised by the
test suite.

The Android code is also moved into this scheme, although it seems
incomplete prior to this change, does not compile, and is therefore
untested.

Bug: 581471
Test: vulkan_tests

Change-Id: Icefe29b0bfd4fe5ff2c951cefc47b0472250bce7
Reviewed-on: https://chromium-review.googlesource.com/1055824
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559152}

The hashing algorithm changes depending on the authentication method, and also
possibly based on state in cryptohome (see cryptohome_authenticator.cc). A
cryptohome key can dynamically specify which hashing algorithm it uses.

Remove the SyncPasswordData mojom type; it will be computed automatically with
the plain-text password.

In the future, all cryptohome-related logic should be moved to ash. This will be
more feasible after webui login is gone. Then, we should be able to eliminate
the browser process ever having access to the plain-text or hashed password.

In terms of security, this causes no regression compared to webui-based login.

Bug: 826773
Change-Id: I9258be00afe151ffc0b8f61aafeb2b42ba8d12ff
Reviewed-on: https://chromium-review.googlesource.com/1052381Reviewed-by: Mattias Nissler <mnissler@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559151}

Viz hit-test doesn't work with mash completely yet so some
mash_browser_tests would fail (e.g. [1]) when we enable Viz
hit-test (feature VizHitTestDrawQuad) by default. Deleting
that codepath in this CL since it's not used anyway and will
revisit/debug when we need to add support for WS in Viz
hit-test.

[1] https://chromium-swarm.appspot.com/task?id=3d693515ea5b4310&refresh=10&show_raw=1

Bug: 842351
Change-Id: Id75b342427e231b209c90dbc1b603d65c5639fd0
Reviewed-on: https://chromium-review.googlesource.com/1058438Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Ria Jiang <riajiang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559150}

The Copy URL adjustment code interacts poorly with ZeroSuggest, because
it is subtly wrong.

To be specific: If the popup is open, it would use the current match's
URL even if the input text is not an exact match.

This mostly affected MacOS.

This CL fixes the bug and adds a test.

Bug: 838541
Change-Id: Ia6e5d58aa473033c8f17783ce7fbcbce3b687938
Reviewed-on: https://chromium-review.googlesource.com/1059857
Commit-Queue: Tommy Li <tommycli@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559149}

Crashes from Android indicate that the page_size being returned is
zero.  Set it to 1KiB for the check.  It's probably 4KiB but this is
sufficient for the test.

Bug: 836875
Change-Id: Ifedbcd648157ac4e39560640048c0640f97e5416
Reviewed-on: https://chromium-review.googlesource.com/1059728Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559148}

Bug: 714018
Change-Id: I6424da4665e0f5e4bdb8ad03b30ad5ff41d28b1f
Reviewed-on: https://chromium-review.googlesource.com/1061813Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Commit-Queue: Mark Pilgrim <pilgrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559147}

Bug: 823365
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Id64ba29f5105f8adb3e6f65fd1da5c8eec28dd89
Reviewed-on: https://chromium-review.googlesource.com/1061584Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559146}

As part of an effort to implement feature policies to improve performance
issues with images, "max-downscaling-image" policy restricts images
whose sizes are more than X times bigger than its containing block.

Images will be rendered with inverted color when violating this policy.

Bug: 837349
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I66d6e61b190d68750a458e2aa21a66683fd9d06a
Reviewed-on: https://chromium-review.googlesource.com/1033449
Commit-Queue: Luna Lu <loonybear@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559145}

This removes all std::unique_ptr<WebLayer> and pass around cc::Layer*
directly instead of WebLayer*.

R=pdr@chromium.org

Bug: 838693
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ic36930e83f8d5f64780c7f6b46632c9bd90888f6
Reviewed-on: https://chromium-review.googlesource.com/1060351Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559144}

ImageTransportSurfaceOverlayMac needs to notify its delegate when the
presentation-callback is run, because the delegate (implemented by
GLES2CommandBufferStub in regular chrome) is what ultimately sends the
IPC for presentation-callback back to the gpu/viz-host.

BUG=811961, 776877

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: Ic0538eae3dbe2bfbd92f1ffdc1a4d5bdf4b248a0
Reviewed-on: https://chromium-review.googlesource.com/1060741Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559143}

Improve the reliability of the windows virtual keyboard by using
the InputPane class. This Windows RT API takes care of figuring out
if the keyboard should be displayed or not (ie. if a hardware keyboard
is connected, or a touchscreen connected etc.)

BUG=817501

Change-Id: Ie310b7f485ff4096bb4f8943d43d84dced652ac6
Reviewed-on: https://chromium-review.googlesource.com/946152
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559142}

cookieStore methods receive individual UMA counters. The getters for
CookieChangeEvent and ExtendableCookieChangeEvent also receive UMA
counters, mostly so that we can count apps that call
subscribeToChanges() when a service worker installs, and then consume
the 'cookiechange' events, without calling another cookieStore method
ever again.

TBR=kinuko

Bug: 729800
Change-Id: I0c2aa37700cb6af7e1dc16b695e40dbffb33688f
Reviewed-on: https://chromium-review.googlesource.com/1060624
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559141}

Splitting this into its two constitutuent components (finding the highest
priority active configuration, and computing the activation decision).  This is
being done to aid with crrev.com/c/1058087, which looks at all of the highest
priority active configurations (for a redirect chain) and bases the activation
decision off of the highest amongst those.

Change-Id: Iee1c9d615e5008edd15a2ab363e602c6edd4d9e9
Reviewed-on: https://chromium-review.googlesource.com/1059893Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Commit-Queue: Eric Robinson <ericrobinson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559140}

This change adds a new platform style constant for whether focus rings should
should be preferred over ink drops to indicate focus.

Button subclasses can opt into this behavior by setting install_focus_ring_on_focus to true. This change includes this opt in for all top chrome buttons (as well as page actions).

Bug: 836961, 826294
Change-Id: I32239b88c4e3862d6f1029b375df7c678b5044a5
Reviewed-on: https://chromium-review.googlesource.com/1043011
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559139}

https://pdfium.googlesource.com/pdfium.git/+log/a68ee04cfdeb..99a046acd2d1

$ git log a68ee04cf..99a046acd --date=short --no-merges --format='%ad %ae %s'
2018-05-16 dsinclair Use CheckedNumeric in CFX_RTFBreak::AppendChar_Others

Created with:
  roll-dep src/third_party/pdfium
BUG=chromium:843096


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

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

Bug: 821000
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ic11a4756101fa597c2779e5b82c93e62738c657d
Reviewed-on: https://chromium-review.googlesource.com/1055742Reviewed-by: Helen Li <xunjieli@chromium.org>
Commit-Queue: Lily Houghton <lilyhoughton@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559137}

For some reason, maybe old fmod inconsistencies, the code
looked like this:

fmodf(fmodf(A, B) - B, B)

According to the definition of fmod, the inner fmod returns
f s.t. A = i * B + f for integer i, f same sign as A, and
|f| < |B|. So fmod(A, B) = A - i * B for some i.

Then, fmod(A,B) - B = A - (i+1) * B

And fmodf(fmodf(A, B) - B, B) = g s.t.  A - (i+1) * B = j * B + g

Rearranging, A = (j+i+1) * B + g

So we get exactly the same outcome just using fmodf(A,B)

R=fs@opera.com

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Icbe89c2922dfc4ff89463baf3c73089bc69d7a9c
Reviewed-on: https://chromium-review.googlesource.com/1061793Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559136}

This is the first step necessary prior to introduce a LinearGradientQuadRenderer.

Bug: 843239
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;master.tryserver.chromium.linux:linux_vr
Change-Id: I1be5e6265b99a153c3b7dba6e385f965952bac15
Reviewed-on: https://chromium-review.googlesource.com/1060120
Commit-Queue: Aldo Culquicondor <acondor@chromium.org>
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559135}

When we first built out the IdentityManager C++ class and backed it via
//components/signin classes, we wanted its interaction with those
classes to mimic eventual interaction with the Identity Service as much
as possible. As part of this design goal, we implemented it to handle
callbacks from SigninManager by posting tasks to set its internal state
and notify observers; this mimics the fact of receiving these
notifications asynchronously from the Identity Service.

This mimicking has proven useful, as it has ferreted out issues with
tests assuming that signin state can be changed and have those changes
observed synchronously. However, it has also proven problematic:

1. By delaying the change to IdentityManager's internal state, we could
end up with clients getting inconsistent views of the user's signin
state from SigninManager and IdentityManager (cf.  crbug.com/804410).

2. We then changed IdentityManager to change its internal state before
SigninManager sends its callbacks, but still delay notifying its
(IdentityManager's) observers by posting a task. However, we have
gotten feedback from developers of clients of IdentityManager that this
behavior is problematic semantically: these developers want to be able
to make changes to internal state in response to IdentityManager
callbacks and have the invariant that those changes to internal state
are made atomically with the change in IdentityManager's internal state.
By decoupling the change in IdentityManager's internal state from the
notification of its observers, these developers are forced to handle
additional intermediate states in their code (e.g., "IdentityManager
has changed to have the user be signed in but hasn't yet notified its
observers").

In consequence of (1) and (2), we are abandoning the asynchronous
notification at this time. However, once the codebase is converted away
from direct usage of SigninManager entirely to IdentityManager, it could
be a good idea to reintroduce the implementation described in the top
paragraph above; reintroducing that implementation would be a good
intermediate move to switching in the Identity Service-backed
implementation.

This change should not introduce any behavioral changes, as nothing in
the codebase relies on these callbacks being fired asynchronously (or
is even aware that they're fired asynchronously).

Bug: 843510
Change-Id: Id1bc40fccbe1c4481d0c4968f90d7c15d1af154a
Reviewed-on: https://chromium-review.googlesource.com/1061494
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559134}

Regression of crrev.com/c/1056447.

Bug: 733662
Bug: 843451
Change-Id: Ia123a20a0c6fff9ddb20697e10e8423b3f04b949
Reviewed-on: https://chromium-review.googlesource.com/1061835Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jiaquan He <hejq@google.com>
Cr-Commit-Position: refs/heads/master@{#559133}

Bug: None
Test: compiles
Change-Id: I53a62885d30d8ba8bc5695277fc73fdf857628ba
Reviewed-on: https://chromium-review.googlesource.com/1060636Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Qiang Xu <warx@google.com>
Cr-Commit-Position: refs/heads/master@{#559132}

1. Skip checking for enterprise whitelisted downloads
If enterprise admin has configured "SafeBrowsingWhitelistDomains" policy,
and the any URL in this download's |GetUrlChain()| matches any of these
whitelisted domains, download protection will not check the URL(s) and
content of this download.

2. When user opens a dangerous download, trigger |OnDangerousDownloadOpened|
private extension API calls. (This private extension API call is only used by
enterprise reporting extension.)

Bug: 811467, 811454
Change-Id: I7e716a6a10900bc894ad721368edb9c82802efd4
TBR: benjhayden@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1054832
Commit-Queue: Jialiu Lin <jialiul@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Nathan Parker <nparker@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559131}

This is a (very) partial reland of
https://chromium-review.googlesource.com/c/chromium/src/+/738395,
restoring only the changes to LayoutTests. This should be safe since
'%23' always has been a correct encoding of '#' and so should work with
the data URI code as it is today. It will also make any future re-land
of the core original CL easier.

Bug: 123004
Change-Id: I87126ea0e3fd39756e571a8e6cf966107e7f7209
Reviewed-on: https://chromium-review.googlesource.com/1048287Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559130}

BUG=chromium:809093

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: I9b061df95987130aeaacc46fa3feca943c781a9d
Reviewed-on: https://chromium-review.googlesource.com/1060277Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559129}

https://skia.googlesource.com/skia.git/+log/4c2a34e4804e..510e9e399b3d

$ git log 4c2a34e48..510e9e399 --date=short --no-merges --format='%ad %ae %s'
2018-05-16 caryclark Reland "Reland "remove obsolete color defines""
2018-05-15 jcgregorio [docker] Move to testing-slim as the base image.
2018-05-15 borenet [recipes] Move 'gclient runhooks' from flutter build to core
2018-05-15 kjlubick Fix UBSAN warnings in SkPerlinNoiseShaderImpl
2018-05-16 angle-skia-autoroll Roll third_party/externals/angle2/ 10e7e5013..80c32ccbb (1 commit)
2018-05-16 caryclark Documentation refresh

Created with:
  roll-dep src/third_party/skia


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

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

This is a follow-up to https://chromium-review.googlesource.com/975562,
testing subresources as well.

Bug: 824209
Change-Id: Ie8ebe5d105bfd266f7f99e5851bdabc8f0323540
Reviewed-on: https://chromium-review.googlesource.com/1060033
Commit-Queue: Benoit L <lizeb@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559127}

These are old leaks, so suppressing seems appropriate.

Bug: 831667
Change-Id: Ic5efd1d06bb220d99edad1f9d44db5e7371f6ed5
Reviewed-on: https://chromium-review.googlesource.com/1061501Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559126}

Tbr: kojii@chromium.org
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_layout_ng;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I987a89c3401656712f0ccee78b6ef12b9b16e997
Reviewed-on: https://chromium-review.googlesource.com/1060080Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559125}

Bug: 810890
Change-Id: I5230aaf33ea5d90e61a4a20e77a08b46d457a275
Reviewed-on: https://chromium-review.googlesource.com/1059950Reviewed-by: David Turner <digit@chromium.org>
Commit-Queue: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559124}

Cherry-picked from https://github.com/xiph/opus/pull/87

Change-Id: I328f08be0396597d83ef09b13624f2a236fe0263
Reviewed-on: https://chromium-review.googlesource.com/1060739Reviewed-by: Henrik Andreasson <henrika@chromium.org>
Commit-Queue: Felicia Lim <flim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559123}

This fixes one more race condition for OEM folder creation where it is
created on demand on ash side first. This also fixes issue when OEM
folder may appear in ash as normal folder. Plus does refactoring by
discarding passing redundant oem_folder_id.

Test: Manually
Bug: 839024
Change-Id: I3844e8fbf24fc12c806f25f7c87973eebe167d02
Reviewed-on: https://chromium-review.googlesource.com/1060166Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Yury Khmel <khmel@google.com>
Cr-Commit-Position: refs/heads/master@{#559122}

Register WorkerSchedulers with NonMainThreadScheduler similar to how
PageSchedulers are registered with MainThreadScheduler.

R=alexclarke@chromium.org
BUG=776416

Change-Id: I824cccfaafb4cea701807f60e3f0b70014e1b423
Reviewed-on: https://chromium-review.googlesource.com/1061461Reviewed-by: Alex Clarke <alexclarke@chromium.org>
Commit-Queue: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559121}

- Canvas2D.addPath
- CanvasPattern
- PaintRenderingContext
- removes currentTransform

Bug: 651798
Change-Id: If4c94253d6b060964c1575eb7f189979b42486e5
Reviewed-on: https://chromium-review.googlesource.com/677643
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559120}

This cl is a workaround for handling events on windows/ozone.
A PlatformEvent is a ui::Event when ozone is enabled while windows
specific code assumes that an Event is an MSG. This cl introduces
utility functions that help windows code convert MSGs into ui:Events and
vice versa.

Change-Id: Ic811bc12fdcd0d6ff0cebd174ad4c87aa689b930
Reviewed-on: https://chromium-review.googlesource.com/1011109Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Mustafa Çamurcu <camurcu@google.com>
Cr-Commit-Position: refs/heads/master@{#559119}

Bug: 840803
Change-Id: I73adf2f8279ba491200cd027e29a493b45d6590d
Reviewed-on: https://chromium-review.googlesource.com/1060602
Commit-Queue: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559118}

Annotates RegisteredEventListener class as final.

Change-Id: Ie2ec4d9686e27ca74a6535440259e7088ef20697
Reviewed-on: https://chromium-review.googlesource.com/1061714Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559117}