GitLab

cc::UpdateTickingType::FORCE is only used in two circumstances:

1. From ElementAnimations::InitAffectedElementTypes.
2. From ElementAnimations::ElementRegistered.

Since InitAffectedElementTypes is only called when constructing a new
ElementAnimations, the call can be moved to the constructor such that we
can guarantee the keyframe_effects_list_ is empty and thus remove the
call to UpdateKeyframeEffectsTickingState(FORCE).

When called from ElementRegistered, we are about to set
has_element_in_active_list or has_element_in_pending_list which will
result in the keyframe effect having an element in a list giving the
same behavior that force was being used to provide. The other possible
side effects of force seem unintentional.

Change-Id: I6128793e953ad2e59fbc7657033995292c204f48
Reviewed-on: https://chromium-review.googlesource.com/c/1469070
Commit-Queue: Robert Flack <flackr@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632337}

This CL intends to allow integration tests (for HTTPS server previews)
to test end-to-end behavior of reporting to the right end point. Instead
of waiting a minute for the test to finish, having a faster delay is
preferable.

Bug: 931411
Change-Id: I828d51f1b2faecbbd8dc38fd75d6f39e8fa9655f
Reviewed-on: https://chromium-review.googlesource.com/c/1471214Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632336}

The in-suggestion side-button Pedals were experimentally
considered along with dedicated suggestions, but dedicated
suggestions were found to be preferred, so this CL simplifies
the Pedals code. The #omnibox-pedal-suggestions flag is
reduced from enum to bool, and related code is changed or
removed so that dedicated Pedal suggestions are the only kind.

Bug: 893183
Change-Id: I67864c4b9686372023aa9623b68d1fb1b985fc51
Reviewed-on: https://chromium-review.googlesource.com/c/1471251Reviewed-by: Kevin Bailey <krb@chromium.org>
Commit-Queue: Orin Jaworski <orinj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632335}

TBR=bpastene@chromium.org

Bug: 932036

Change-Id: Icb9ebd2b17560a843595d49cbee034f471ed8fa3
Reviewed-on: https://chromium-review.googlesource.com/c/1473831Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632334}

Relanding https://chromium-review.googlesource.com/c/1449151 with fixes.

Patchset 1 is https://chromium-review.googlesource.com/c/1449151

Patchset 2 is https://chromium-review.googlesource.com/c/1464228

Patchset 3 is the new fix. When you run a telemetry benchmark as a
reference, you are supposed to do
`run_benchmark benchmark_name --browser=reference`
but I thought that you were supposed to do
`run_benchmark benchmark_name.reference --browser=reference`
because I read the earlier code wrong.
I also added a end to end test for this behavior, which also
covers sharding code as well.

Patchset 5 is a unittest for
https://chromium-review.googlesource.com/c/1464228

Bug: 930879, 928928, 927507, 923628, 920002, 744736
Change-Id: If73d929b8e1b32c33d2bed7d2298b64d205658c1
Reviewed-on: https://chromium-review.googlesource.com/c/1467907Reviewed-by: Emily Hanley <eyaich@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632333}

Bug: 932141
Change-Id: I35665b81a01076297256a1631e6434433797061f
Reviewed-on: https://chromium-review.googlesource.com/c/1473331Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632332}

Add histogram to collect number of connection migrations exercised before receiving a public reset from the peer.

Bug: 929478
Change-Id: I0f72794bacadf8585cd498196153c670f6c13a41
Reviewed-on: https://chromium-review.googlesource.com/c/1471392Reviewed-by: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632331}

The code was static_cast'ing a WindowTreeHost to a WindowTreeHostMus. This
static_cast is not valid if the window is contained in another WindowTreeHost
subclass. Normally that shouldn't happen, but does if a Window created with
aura::Env::Mode::MUS is in the same hierarchy as those of
aura::Env::Mode::LOCAL. There are DCHECKs that prevent that from happening,
but sadly they aren't run on this bot.

This fixes the crash, but the real fix is to not mix the two types in the
same hierarchy.

BUG=930975
TEST=none

Change-Id: I89b13f719d773aa8521e1e1fff0b225f6d65f3ad
Reviewed-on: https://chromium-review.googlesource.com/c/1473813
Commit-Queue: Scott Violet <sky@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Auto-Submit: Scott Violet <sky@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632330}

Add the ability to turn on/off the InlineUpdateController based on
whether or not there are any active ChromeActivities that are running
(RESUMED).

BUG=922714

Change-Id: I30be4c9894f6be7352f75f2861b6ed5165dd5296
Reviewed-on: https://chromium-review.googlesource.com/c/1468403Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632329}

This CL fixes the size and the appearance of the cell, respecting the
choosen background color and letting its height be the same as the
Text cell.

Bug: 930887
Change-Id: I38cc9bfc037cc04e3d996a77649c00bdebf156f9
Reviewed-on: https://chromium-review.googlesource.com/c/1472570
Auto-Submit: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632328}

Also fix a bunch of compile errors in C mode in MOJO_STATIC_ASSERT
now that it compiles to something.

No behavior change.

Bug: 926235
Change-Id: Ia45197abb752d816c6aec0ec618940f6168396be
Reviewed-on: https://chromium-review.googlesource.com/c/1473617Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632327}

Now that overview windows are always stacked ontop of their caption
container views, we can remove the extra backdrop widget and
draw it as part of the caption container view.

It used to be separate widget because caption container view used to be
stacked on top of overview windows to block events and backdrop needs
to go behind.

Test: ash_unittest OverviewSessionTest.Backdrop
Bug: 914147
Change-Id: Ida145337a6fd3e405c8dc40314f92a629d165320
Reviewed-on: https://chromium-review.googlesource.com/c/1470730
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632326}

We want to share the caching logic between DrmOverlayManagerHost and
DrmOverlayManagerGpu (which doesn't exist yet). Move the cache into the
base class with minimal changes. Add virtual functions for sending
overlay validation request to the DRM thread and performing basic sanity
checks on OverlaySurfaceCandidate.

The only change to functionality is the addition of a ThreadChecker in
DrmOverlayManger functions that modify |cache_|.

Bug: 930173
Change-Id: I1fd51aeec36ac7d553a0b93c245e29c9daf67535
Reviewed-on: https://chromium-review.googlesource.com/c/1470393Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632325}

This is in preparation of removing the custom cr.EventTarget implementation in
favor of native EventTarget, which requires all subclasses to be ES6 classes,
ottherwise a runtime "Illegal invocation" error is thrown.

Bug: 854268,778674
Change-Id: I2747723bb70d0ee950d8a2514588dc79b8cff5f2
Reviewed-on: https://chromium-review.googlesource.com/c/1450538Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632324}

Move computation of Legacy static position to utility routine
that can be called by NGOutOfFlowPart.
Also, 2 minor const code cleanups.

This CL is part 1/X of placing Legacy contained OOF Elements by NG.


Bug: 907911
Change-Id: I80cbe9b84092ebb0ed6807f90e6ffd8586926272
Reviewed-on: https://chromium-review.googlesource.com/c/1471383
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632323}

r1462423 defined some identically named symbols in unnamed namespaces in
authenticator_client_pin_entry_view.cc and ble_pin_entry_view.cc, which
apparently broke jumbo builds for some people (I cannot reproduce this
on my machine, nor did it break any of the continuous builders AFAICT).
This extracts a MakePinTextField() helper and moves the colliding
symbols in that method's local namespace, which should hopefully fix
this issue.

Change-Id: I49450c6a3f47d9de882dacd38c7d21a7e51e9bae
Reviewed-on: https://chromium-review.googlesource.com/c/1473811
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Commit-Queue: Adam Langley <agl@chromium.org>
Auto-Submit: Martin Kreichgauer <martinkr@google.com>
Reviewed-by: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632322}

This is more clear than DefaultReportingAllowList because companies on
the list do NOT get reported.

Also added a unit test for the function.

R=csharp

Bug: 842296
Change-Id: I3ec6141d587f7e90782d7d6051f3a96a677ba2b6
Reviewed-on: https://chromium-review.googlesource.com/c/1464458
Commit-Queue: Joe Mason <joenotcharles@google.com>
Reviewed-by: Chris Sharp <csharp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632321}

This fixes the build with libstdc++ after commit 3a6cdd45 ('Improvements
in FlexLayout "stretch" cross-axis alignment handling'):

    ../../ui/views/layout/flex_layout_types_internal.cc: In member function ‘void views::internal::Span::Center(const views::internal::Span&, const views::internal::Inset1D&)’:
    ../../ui/views/layout/flex_layout_types_internal.cc:57:20: error: ‘ceilf’ is not a member of ‘std’
         set_start(std::ceilf(remaining * 0.5f));
                        ^~~~~
    ../../ui/views/layout/flex_layout_types_internal.cc:57:20: note: suggested alternative: ‘ceil’
         set_start(std::ceilf(remaining * 0.5f));
                        ^~~~~
                        ceil

ceilf() is not officially part of the C++14 standard even though libc++
exposes it. In this case, we're multiplying an int and a float, which means
we'll call ceil(float) anyway.

Bug: 819294
Change-Id: I24f16a5cd0462baef0eea07791758a3712ff2922
Reviewed-on: https://chromium-review.googlesource.com/c/1472673
Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Dana Fried <dfried@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632320}

This CL fixes how PFFFT does processor architecture detection.

The goal is to stop defining "PFFFT_SIMD_DISABLE" which disables SIMD
in favor of scalar code (which results in a huge performance hit).

Bug: webrtc:9577
Change-Id: I49f59791ae2b6f5e6d0790f11bd0bc8dff7aa2ee
Reviewed-on: https://chromium-review.googlesource.com/c/1473173Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632319}

Deflakes VrBrowserNativeUiTest#testKeyboardAppearsOnUrlBarClick and
testOverflowMenuAppears, both of which were flaky due to some pixels
being slightly (not user-visibly) off.

This change adds the ability for RenderTests to set a threshold for how
different pixels can be before being considered different and uses this
functionality in the two affected tests with small thresholds.

Bug: 930840, 930296
Change-Id: I55ae10811c3fd8c69588cb4c22034199c019e029
Reviewed-on: https://chromium-review.googlesource.com/c/1464172
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632318}

Now that --enable-passthrough-raster-decoder protects the raster decoder from
being used unepxectedly with ANGLE, we don't need to always disable it through
a blacklist.

BUG=829435
BUG=882580

Change-Id: I0ffc97237810f891d34f0b15835aa60efde85247
Reviewed-on: https://chromium-review.googlesource.com/c/1464110Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632317}

* pandas is not available.
* Disable tests using pandas
* Add testing to bootstrap_deps

BUG=921762
TEST=tools/perf/run_tests

Change-Id: Id2011521027b03902cca8fecd176b2116aa1a271
Reviewed-on: https://chromium-review.googlesource.com/c/1473175Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632316}

Removed unnecessary indirection and allocation via std::unique_ptr for
storage of value types in cached image data (both gfx::Size and
gfx::ImageSkia are value types).

Added unit tests checking assumptions and ensuring that we will not
break said assumptions about how image data is cached/image data
duplication is prevented in the future.

Change-Id: I59a70aa1ccb2e00fbc1a69ad92e48374643b6d20
Reviewed-on: https://chromium-review.googlesource.com/c/1471514Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Dana Fried <dfried@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632315}

iOS should use titlecase capitalization instead of sentence case.

Bug: 913958
Change-Id: I50a46a369afd062180d3d6691a87f0e2682b98de
Reviewed-on: https://chromium-review.googlesource.com/c/1472626Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Robbie Gibson <rkgibson@google.com>
Cr-Commit-Position: refs/heads/master@{#632314}

- Don't make js call to setUserImageURL when unified consent is enabled.
- Change the unsafe js call to setUserImageURL to a safe call.
- Add unit tests for when unified consent is enabled.

Bug: 917367
Change-Id: If6cfaa3138b2d0deca715e3a627e22073345e26d
Reviewed-on: https://chromium-review.googlesource.com/c/1473151Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Auto-Submit: Thomas Tangl <tangltom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632313}

This CL was uploaded by git cl split.

R=binji@chromium.org

Bug: 926235
Change-Id: I8a5fcd94a99c05826850084090372a619d309672
Reviewed-on: https://chromium-review.googlesource.com/c/1463399
Auto-Submit: Nico Weber <thakis@chromium.org>
Commit-Queue: Sam Clegg <sbc@chromium.org>
Reviewed-by: Sam Clegg <sbc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632312}

1. Updated web.Frame.CreateView() to take ExportToken - all callers
   should be using CreateView2, so it's safe to update this method.
2. Updated all other places that pass view tokens to use ExportToken
   type instead of zx::eventpair.
3. Removed viewsv1::ViewProvider implementation from WebComponent.
4. Removed other vestigial dependencies on viewsv1.

Some APIs still use eventpair instead of ExportToken - they will be
updated later.

Bug: 899348
Change-Id: Ic08485573e6d75e1b45249467a9eb5a57f046057
Reviewed-on: https://chromium-review.googlesource.com/c/1471227
Auto-Submit: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632311}

We could show ClientLoFi on POST, but it's not worth all the plumbing.

Cleans up the LitePageRedirect specific check for this behavior.

Bug: 931991
Change-Id: Iec22cda9fbbe0639516b6bc7960a26c6563118a6
Reviewed-on: https://chromium-review.googlesource.com/c/1473540Reviewed-by: Doug Arnett <dougarnett@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632310}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/aea01e376748..ffa447f419e1


git log aea01e376748..ffa447f419e1 --date=short --no-merges --format='%ad %ae %s'
2019-02-14 evanhernandez@chromium.org cros_branch_unittest: Lingering rename func tests.


Created with:
  gclient setdep -r src/third_party/chromite@ffa447f419e1

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I65dbfa5fe45b66eb27ed923e7a3897d0c554d7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1473473Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#632309}

The problem was that when a user runs Android Chrome initially,
experiments are randomized using the low entropy source because
metrics consent has not been received yet (and a client id has
not been generated). Even if the user has the checkbox enabled
in the first run wizard, it's already too late for field trial
randomization.

This change fixes this by provisionally generating a client id
on first run for field trial randomization. If metrics consent
is received from the user, this id becomes the actual client id
- otherwise it is cleared. This way, when the user proceeds
through the FRE and keeps the metrics checkbox checked, they
will no longer have their experiments become re-randomized on
the second run.

Bug: 927063
Change-Id: I3b3de4076c06f5afb7ce3466b346aa5a485ca48c
Reviewed-on: https://chromium-review.googlesource.com/c/1392269
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632308}

Adds FeatureLibrary::BatteryPower, which is a boolean feature for
whether the device is on battery power or not.

Change-Id: I8dd609380c9e6d5768179cd60be73945e3e303e5
Reviewed-on: https://chromium-review.googlesource.com/c/1471224Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632307}

This is a reland of ab8cc613

Original change's description:
> Use 32 cores on 'win-asan'
> 
> https://crrev.com/i/828938 added a new bot which has 32 cores. This CL
> should make the builder use that machine instead of the old 8 core
> machine.
> 
> Bug: 919189
> Change-Id: I3cf8894e73c21a9d590ce709c3fa3b40ca23d0f2
> Reviewed-on: https://chromium-review.googlesource.com/c/1470991
> Commit-Queue: Stephen Martinis <martiniss@chromium.org>
> Commit-Queue: John Budorick <jbudorick@chromium.org>
> Auto-Submit: Stephen Martinis <martiniss@chromium.org>
> Reviewed-by: John Budorick <jbudorick@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#631830}

Bug: 919189
Change-Id: I9a39bdb6efebf9d635e8d52067a80ff319a6d5f7
Reviewed-on: https://chromium-review.googlesource.com/c/1471389Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632306}

Change-Id: I5645cca6efa5e9436dcab3a9173b2cb0882e8562
Reviewed-on: https://chromium-review.googlesource.com/c/1471450
Auto-Submit: Piotr Bialecki <bialpio@chromium.org>
Commit-Queue: Brandon Jones <bajones@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632305}

Bug: 780980
Change-Id: Iaba6912351c43f38e59c613998ccfd7d1c11a682
Reviewed-on: https://chromium-review.googlesource.com/c/1473618Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632304}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/3b1e64245a0b..452a49f4b699


git log 3b1e64245a0b..452a49f4b699 --date=short --no-merges --format='%ad %ae %s'
2019-02-14 dmcardle@chromium.org Fix colorized branch alignment in 'git cl status'


Created with:
  gclient setdep -r src/third_party/depot_tools@452a49f4b699

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=agable@chromium.org

Change-Id: I89c984e83482326903601715b42906f45d198dcc
Reviewed-on: https://chromium-review.googlesource.com/c/1473553Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#632303}

Bug: 931338
Change-Id: I22aaa131ed4b719e8d3683f6d28deb1d4eccab2a
Reviewed-on: https://chromium-review.googlesource.com/c/1470394Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632302}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/e9d7dbcd..f806ca6b

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=luci.chromium.try:linux-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: I5b57303d2f7729e9e767598cba4bfb44ac595284
Reviewed-on: https://chromium-review.googlesource.com/c/1473397Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#632301}

This reverts commit 6cf9dcc6.

Reason for revert: Looks like this caused pointer event tests to fail in Linux Trusty:

https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/WebKit%20Linux%20Trusty%20Leak/30147

Original change's description:
> Use testdriver Action API in WPT pointerevent touch tests
> 
> In order to run the web-platform-tests automatically, we will use
> testdriver Action API in all the wpt to simulate inputs. Here we are
> changing some pointerevent touch input tests which are doing scrolling.
> 
> Bug: 606367
> Change-Id: Ibdabcbb973ac641174ca6faadccd737fa8c678b4
> Reviewed-on: https://chromium-review.googlesource.com/c/1461504
> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
> Commit-Queue: Lan Wei <lanwei@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#632251}

TBR=lanwei@chromium.org,nzolghadr@chromium.org

Change-Id: If3d25e3e679ad345c6a3566d2bf6a0a962ba5568
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 606367
Reviewed-on: https://chromium-review.googlesource.com/c/1473973Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632300}

Until all MRPs support empty-source sink queries, QueryResultManager::
AnyMediaSinksObserver may return an incomplete list of sinks. This CL
makes QueryResultManager keep track of sinks with sources and sources
returned by AnyMediaSinksObserver separate, and take their set union
when notifying observers.

Bug: 929225
Change-Id: I33f8caf789ce8033c5481b9fa86691e9d7f3f537
Reviewed-on: https://chromium-review.googlesource.com/c/1459338
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632299}

Bug: 923083
Change-Id: I2685559c1078d11a45de5a1ae090924857aa43d7
Reviewed-on: https://chromium-review.googlesource.com/c/1473670Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#632298}