GitLab

At least 2 unit tests were passing for the *wrong* reasons in this file.
The main focuses of this change are:

1) Changing credit cards to be the correct length.  The 12-digit numbers
in use in this file were failing card.IsValid(), dropping out of the
ImportCreditCard() path earlier than expected.

2) Calling base::RunLoop().Run() whenever the database is changed and
confirming that setup was correct.  The lack of this was causing credit
cards to not be added after setup.

3) Minor grammatical/consistency fixes

Bug: 
Change-Id: I313c18bd9ad8d9e89ff6681a19f4412e186657ec
Reviewed-on: https://chromium-review.googlesource.com/592509
Commit-Queue: Jared Saul <jsaul@google.com>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491485}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/1dc40944..bfb1b022

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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org

Change-Id: Ifa82d012c773ea9f84faa77797614ab241409a24
Reviewed-on: https://chromium-review.googlesource.com/598767Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491484}

In a previous CL: https://chromium-review.googlesource.com/c/581907, when
we access to the |composited_layer| inside the for loop, we didn't
perform any null check, and that's causing crash. This CL adds the null
check.

NOTRY=true

Bug: 751389
Change-Id: I5a0861d416b017af5c51ea82ce3add032b0b2316
Reviewed-on: https://chromium-review.googlesource.com/598123
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491483}

https://skia.googlesource.com/skia.git/+log/50f7a1e4abea..828930677138

$ git log 50f7a1e4a..828930677 --date=short --no-merges --format='%ad %ae %s'
2017-08-02 mtklein Revert "remove another SkConvertPixels "fast path""
2017-08-02 rmistry Update webpages_playback.py to use the new Golang impl of WPRs
2017-08-01 benjaminwagner Update all Debian bots to 9.1.
2017-08-02 fmalita Delete legacy radial gradient impl
2017-08-02 egdaniel Revert "Revert "Revert "Revert "Add support for semaphores to be inserted on GrContext flush""""
2017-08-02 fmalita Fix sweep gradient tiling w/ makeColorSpace
2017-08-02 skia-deps-roller Roll skia/third_party/externals/angle2/ b0761934b..df7d7c9ec (1 commit)
2017-08-02 liyuqian Reduce SORT_THRESHOLD to 256
2017-08-02 mtklein remove another SkConvertPixels "fast path"
2017-08-02 fmalita Fix sweep_tiling GM sizing

Created with:
  roll-dep src/third_party/skia


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

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=liyuqian@chromium.org

Change-Id: Ia063146367c3bbceff05a39d5fae1f7db5a8c629
Reviewed-on: https://chromium-review.googlesource.com/598497Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491482}

The factory will remain in the Android tree (it has to, to test against
the ChromeHome feature), while the service itself will move to a place
where it can be shared with Desktop.

I'm not expecting this code to be shared with iOS, which has its own
logo service for some extra caching behavior, so the Profile deps can
stay.

BUG=583290

Change-Id: I5f2840277a787f51cf4523b89bc23a6a0d8dae34
Reviewed-on: https://chromium-review.googlesource.com/597947
Commit-Queue: Chris Pickel <sfiera@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491481}

This is a simple refactor to allow more classes to accept FontSelector
instead of CSSFontSelector.
Most changes are due to s/FontSelector/GetFontSelector/ on StyleEngine.
This builds up ground so we can have a WorkerFontSelector.

Bug: 722393
Change-Id: Ib4e891706d306a6fd5d4cf6d3ebb9567f4f8cbfb
Reviewed-on: https://chromium-review.googlesource.com/596675
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491480}

It duplicates work done by wrapper tracing. This change:
- reduces time spent in a microbenchmark of add/removeEventListener
  by 30% (approximately, measured on Linux)
- simplifies code (including removing some custom callback epilogues)
- avoids the need for an additional internal field on EventTarget
  (other than Node) wrappers

Change-Id: I06023a6bb01ac54bb9e514def17c0aaf4ae50bf0
Reviewed-on: https://chromium-review.googlesource.com/576472
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491479}

Bug: 634443
Change-Id: I415c4d968b29325307401bf1c8b23c24ba977d37
Reviewed-on: https://chromium-review.googlesource.com/597409Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491478}

In https://chromium-review.googlesource.com/576567 we unifed some of
the default_user_image logic. In doing so it is now possible to call
GetDefaultImageUrl with a negative index. Rather than require all
callers to test their parameters or handle an empty image, this CL
returns the default avatar image for invalid input parameters which
should be handled correctly in the UI.

Bug: 751335,750577
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I3f52af21748d37b55fbed95f24ba2ec07e91e311
Reviewed-on: https://chromium-review.googlesource.com/598451Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491477}

Bug: 749251
Change-Id: I5d7ce0b08e979f861b3e560872de58ff6972bcc5
Reviewed-on: https://chromium-review.googlesource.com/598537Reviewed-by: Luna Lu <loonybear@chromium.org>
Reviewed-by: Luna Lu <lunalu@chromium.org>
Commit-Queue: Luna Lu <loonybear@chromium.org>
Commit-Queue: Luna Lu <lunalu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491476}

The handles_frame_sink_id_invalidation bit was introduced because in
the OOP display compositor case, each CompositorFrameSinkSupport handled
its own FrameSinkId invalidation. Now that HostFrameSinkManager has introduced
explicit RegisterFrameSinkId and InvalidFrameSinkId APIs, this bit is no longer
necessary. This CL removes it and updates unit tests accordingly.

Bug: 657959
TBR: jam@chromium.org for content stamp: already reviewed by boliu@ and kenrb@
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: I901614988ada0134cb029a7bbb98f58d94ada337
Reviewed-on: https://chromium-review.googlesource.com/598529
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Bo Liu <boliu@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491475}

Use base::UnguessableToken for random origin id. MediaDrmStorage will
persist the origin id in the origin map.

BUG=493521
TEST=shaka player demo

Change-Id: I01690c9f1985c5346306b1b19e60fb5d434a867e
Reviewed-on: https://chromium-review.googlesource.com/582212
Commit-Queue: Yuchen Liu <yucliu@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491474}

This CL hooks up the plumbing from chrome://memory-internals, so that pressing
"dump" causes a message to be sent to the profiling process, with the pid of the
process to dump, and a file ScopedHandle ready for writing. For now, the file is
always at {USER_DATA_DIR}/memlog_dump, and any existing file is overwitten.

Bug: 751302
Change-Id: I1c120aef5c19b67b652aadf2e90c198d577beb7a
Reviewed-on: https://chromium-review.googlesource.com/595113Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Reviewed-by: Brett Wilson <brettw@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491473}

Bug: 740175
Change-Id: Id391cbd1e60b34a5ef4cc4ac988f04d3a343e224
Reviewed-on: https://chromium-review.googlesource.com/587270
Commit-Queue: Robert Ma <robertma@chromium.org>
Reviewed-by: Jeff Carpenter <jeffcarp@chromium.org>
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491472}

The 2x icon had incorrect values in the PATH_COLOR_ARGB command.
Copied the correct values (30% opacity white) from the 1x version.

TBR=oshima@chromium.org

Bug: 751725
Change-Id: I582d393c22201678c16c9ba9a819850e5add01de
Reviewed-on: https://chromium-review.googlesource.com/598807Reviewed-by: Vladislav Kaznacheev <kaznacheev@chromium.org>
Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491471}

This adds code to query the process' debug symbol maps for offsets
and produces an externally symbolizable backtrace using that data.

R: thakis@chromium.org,wez@chromium.org
CC: jamesr@chromium.org
Bug: 706592
Change-Id: I7b3257ff154671b2eb1c90f7ab91947f55cfa873
Reviewed-on: https://chromium-review.googlesource.com/575290
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491470}

In order to clarify this requirement, this CL switches the callback to
use base::OnceCallback.

Bug: 722935
Change-Id: I9fb96cfa794e0aa3d5765e533c5a0f9ac34d995f
Reviewed-on: https://chromium-review.googlesource.com/598543Reviewed-by: Saman Sami <samans@chromium.org>
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491469}

The previous implementation only used the device scale to convert
from DIP to the screenshot bitmap coordinate space, which did
not take into account the scaling applied when the user presses
Ctrl+Shift+Plus or Minus.

The new implementation deduces the correct scale from the window's
transform.
    
Added unit tests for gesture recognition, with regular, rotated
and scaled displays.
    
Bounding boxes are now computed and kept as gfx::RectF and rounded
to gfx::Rect just once at the last possible moment. This ensures
predictable rounding and makes it possible to write readable
that do not have to work around quirky implementation details.

Bug: 750816
Change-Id: I0ef3fb258917c72220c31b8c0cf37ddb43037958
Reviewed-on: https://chromium-review.googlesource.com/595069
Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491468}

R=rockot@chromium.org

Change-Id: I151aa6ce13d9c3e60c96864b416af52dea2deb81
Reviewed-on: https://chromium-review.googlesource.com/587034Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Ben Goodger <ben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491467}

All of the corrupted histograms are from subprocesses so adding checks
where subprocess histograms are merged into the browser (called by
SubprocessMetricsProvider::MergeHistogramDeltasFromAllocator).

Bug: 744734
Change-Id: Ie6593f2d2ad5fa2e957307b153248bc882174458
Reviewed-on: https://chromium-review.googlesource.com/598189Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491466}

Change kMaxNumDelayableRequestsPerClient to
kDefaultMaxNumDelayableRequestsPerClient to be consistent with the
naming in cc.

Bug: 746640
Change-Id: I5d85e93099e92c437c61e87038a81d6296d327bd
Reviewed-on: https://chromium-review.googlesource.com/598493Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Devdeep Ray <devdeepray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491465}

This handles the types for which autofill won't offer validation, e.g.
Names.

Bug: 748223
Change-Id: I7bbee81d8eebfd843d962cf5eaa446e0f0b6e334
Reviewed-on: https://chromium-review.googlesource.com/598456Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491464}

The passed counts used to be a separate field inside the parent class
and so could theoretically diverge from the bucket-count. Now, however,
the passed counts _is_ the bucket-count so only a coding mistake can
cause the CHECK to fire and thus should be DCHECK.

Change-Id: I754e67f9c9684197fced94695a6ffa9d88552e1a
Reviewed-on: https://chromium-review.googlesource.com/596272Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491463}

Based on tkent@'s comment at
https://chromium-review.googlesource.com/c/593515#message-691de0a91dadbd213f5e762b32917f796c3e4aae

BLINK_IMPLEMENTATION is a macro for controlling symbol for component
build. See
https://chromium.googlesource.com/chromium/src/+/master/docs/component_build.md
Most of BLINK_IMPLEMENTATION occurrences should be replaced with
INSIDE_BLINK

As a bonus:
- Let BUILD.gn in Source/platform/heap/ and Source/platform/loader/ use
  the GN config rule Source/platform:blink_platform_implementation as
  recommended by
  https://chromium.googlesource.com/chromium/src/+/master/docs/component_build.md

Bug: 
Change-Id: I8e1b53b9dbb7e524282ceffcd82db1abf5e53a70
Reviewed-on: https://chromium-review.googlesource.com/597035
Commit-Queue: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491462}

There are no plans (or time) to re-enable the chrome.cast.streaming API tests on
debug builds.

TBR=miu

Bug: 396413
Change-Id: If1ad1ca9a0a75dc2c72273872e4bd60198e79378
Reviewed-on: https://chromium-review.googlesource.com/598647Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491461}

Allows control of whether the Cast Receiver is enabled or not, and
what it is named. Policies allow the administrators to force these
preferences.

Bug: 749436
Test: browser_tests
Change-Id: Ia4f200a7ae3269258b10f5545d812c90de30ca3c
Reviewed-on: https://chromium-review.googlesource.com/590490
Commit-Queue: Yves Arrouye <drcrash@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491460}

This CL is in preparation for converting the bluetooth pairing dialog
(BluetoothPairingUI) to use the MD Settings UI.

This CL:
* Eliminate Settings dependencies from the bluetooth dialog element
  and moves some dialog related error parsing into the dialog element.
* Moves some 'options' strings to settings_strings.grd in anticipation
  of removal of all options strings.
* Adds a new shared location for higher level shared chromeos
  elements: ui/webui/resources/chromeos. These elements are allowed to
  use I18nBehavior to simplify localization.
* Moves the bluetooth dialog element to the new shared location.

Bug: 748193
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I861730aa9cbbe5cb37a8df3d26f62d9f20429672
Reviewed-on: https://chromium-review.googlesource.com/592461
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491459}

testTopSitesTileAfterRedirect fails on "Plus" devices, and this CL
disables it on iOS to unblock running the test case on iPhone 6 Plus,
iOS 11.

Bug: 751224
Change-Id: Iebfac0c16c9f01a68169a19f439e04e828ba8de0
Reviewed-on: https://chromium-review.googlesource.com/598490Reviewed-by: Chris Pickel <sfiera@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491458}

This to fix application menu Close Window for mac views like
-- save info to restore closed window
-- check onbeforeunload event

Bug: 751018
Change-Id: I7a99def820f066fc1f47c3c2bae3a2abb49106ff
Reviewed-on: https://chromium-review.googlesource.com/591848
Commit-Queue: Boris Yusupov <boriay@yandex-team.ru>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491457}

The original CL was reverted because it caused some bots to become flaky.
This was tracked on bug 747125 and should be fixed.

This is a reland of 8a8b48bb
Original change's description:
> Enable field trial testing config for GuestViewCrossProcessFrames.
> 
> Bug: 655753
> Change-Id: I756aada2893846878657fe33b405bdb70b23df54
> Reviewed-on: https://chromium-review.googlesource.com/576207
> Commit-Queue: James MacLean <wjmaclean@chromium.org>
> Reviewed-by: Alexei Svitkine (slow) <asvitkine@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#487966}

Bug: 655753
Change-Id: I59b128cf163be9cc565973f804811e5993ca01be

TBR=asvitkine@chromium.org,wjmaclean@chromium.org

Change-Id: I59b128cf163be9cc565973f804811e5993ca01be
Reviewed-on: https://chromium-review.googlesource.com/591628Reviewed-by: Lucas Gadani <lfg@chromium.org>
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491456}

PaintLayerScrollableArea.

Bug: 748955
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I838699c551ff56ad287e5f1759196c17cf8b698e
Reviewed-on: https://chromium-review.googlesource.com/597016Reviewed-by: Walter Korman <wkorman@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491455}

This change adds a show password button directly in chrome://settings/passwords
to reduce the number of clicks necessary to view a given password.

Bug: 670986
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: If54c92d2ee6c2e64f90a5280e59a4c59af182740
Reviewed-on: https://chromium-review.googlesource.com/575143
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491454}

Clean up PointerEventManager::
ProcessCaptureAndPositionOfPointerEvent to replace
the last two parameters by a single WebMouseEvent
pointer which defaults to null.

Bug: 727333
Change-Id: I0af2277b0ecae48ade70d54fdaad4fac16ee23e3
Reviewed-on: https://chromium-review.googlesource.com/598113Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491453}

When an external display is attached a new RootWindowController and new
shelf are created for that display. Shelf alignment is loaded from prefs.
However, if the external display is marked as primary then the internal
and external displays are swapped. This means that the (new) shelf now
on the internal display never reloads its alignment from prefs. Since
the screen was locked at attach time, the shelf stays in the
bottom_locked state and never becomes visible.

Fix this by reloaded shelf alignment from prefs on display swap.

Bug: 748291
Test: added to ash_unittests
Change-Id: I5780dd3ca3b796b6f46fea9bc46fe875d123701e
Reviewed-on: https://chromium-review.googlesource.com/597410
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491452}

Fix disabled stroke color processing to ensure the non-Harmony disabled color is properly lightened.

Bug: 737271
Change-Id: Ie6bb767b8138472037ffb685091cab8c8986b662
Reviewed-on: https://chromium-review.googlesource.com/581630
Commit-Queue: Allen Bauer <kylixrd@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Reviewed-by: Allen Bauer <kylixrd@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491451}

Fuchsia is initially trying to get a headless build up and
running so idle detection is unnecessary.

Bug: 743296
Change-Id: I497f42d533e853ce397eeae3ced19a490742c0ee
Reviewed-on: https://chromium-review.googlesource.com/596505
Commit-Queue: Scott Graham <scottmg@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491450}

Fuchsia is initially trying to get a headless build up and
running so cursors are unnecessary.

Bug: 743296
Change-Id: Ia2093400215a00f8dabfbd1365baa4b5f58a556b
Reviewed-on: https://chromium-review.googlesource.com/596950
Commit-Queue: Scott Graham <scottmg@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491449}

Bug: 750830
Change-Id: Ifb5ced5c4dd314b17c0bd1466a5d6bd740753da8
Reviewed-on: https://chromium-review.googlesource.com/598092Reviewed-by: Nick Carter <nick@chromium.org>
Commit-Queue: Nick Carter <nick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491448}

Bug: None
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Icab535f6157bd313cb2fe95ad0a54dd11e6e2da9
Reviewed-on: https://chromium-review.googlesource.com/596682Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Scott Chen <scottchen@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491447}

avoid_stencil_buffers blocks MSAA support in Skia.  If the compositor requests
MSAA surfaces, rendering will fail.

R=ericrk@chromium.org
BUG=749438,713854

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I887888845a2c1ee18dbccff6e96aa6cd1eac3df2
Reviewed-on: https://chromium-review.googlesource.com/597321Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: Victor Miura <vmiura@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491446}