GitLab

Mojo doesn't allow removing an uncalled mojo callback while the message pipe is
still open.

On Android, SpellCheckerSessionBridge::RequestTextCheck() discards an incoming
request if it fails to initialize the Java object. In this case, this patch replies
the request with empty result so Mojo requirements are ensured.

Bug: 848483
Change-Id: Ic4e1528dd65d152ad522aa3eb49c76f90a4e66b9
Reviewed-on: https://chromium-review.googlesource.com/1093962Reviewed-by: Rachel Blum <groby@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567813}

TabStripModel is not re-entrant safe. Re-entrancy causes subtle bugs. This will
make it easier to catch those bugs.

Bug: 852997
Change-Id: I70e106b6a3c6f130afda14c493f17f97c8fe26ff
Reviewed-on: https://chromium-review.googlesource.com/1101844Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567812}

TBR=mariakhomenko@chromium.org

Bug: 851444
Change-Id: I13bb7f55dcc0ca4b6e7a0428b8ed71a8ddacb18a
Reviewed-on: https://chromium-review.googlesource.com/1103277Reviewed-by: Becky Zhou <huayinz@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567811}

TBR=robliao@chromium.org
NOTRY=true
BUG=853360

Change-Id: I5c3a4ee9a99af7cda1103d7def48685496462b49
Reviewed-on: https://chromium-review.googlesource.com/1103308Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567810}

We recently enabled Vulkan build by default. However, in the Vulkan code
is "mips" which is #define mips 1 on MIPS builds.

It is easy enough to just rename this instance to mip_levels. It is also
more descriptive anyway. And then it fixes builds targetting MIPS chips.

BUG=853174

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: I45b75b4deaa8c95fba47e8958d9283c49a5f405f
Reviewed-on: https://chromium-review.googlesource.com/1102672Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Chris Blume <cblume@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567809}

The original CL stopped requesting chrome dumps for
RequestPrivateMemoryFootprint, but there was a block in
QueuedRequestDispatcher::Finalize that assumed that the chrome dumps did exist.

> Most clients only need private memory footprint, but the existing methods would
> still query all the MemoryDumpProviders and then filter the results. This CL
> adds a new method that avoids querying MemoryDumpProviders.
>
> Bug: 851712
> Reviewed-on: https://chromium-review.googlesource.com/1098623
> Reviewed-by: Primiano Tucci <primiano@chromium.org>
> Reviewed-by: Nico Weber <thakis@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Commit-Queue: Erik Chen <erikchen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#567417}

Bug: 851712
Change-Id: Ibac7c2189ea74f2029458ba3088159259aab5096
TBR: dcheng@chromium.org, thakis@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1102724Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567808}

When adding an Window to an existing overview grid through
WindowSelector::AddItem(), we should only update its bounds when
necessary. Otherwise we may see a flash and the animation might not look
right. This is because the to-be-added window's bounds might not
consistent with its window state (which might be caused by several
reasons, e.g., tab dragging, tapping on the divider to resize snapped
windows, etc), so updating its window bounds before adding to overview
window grid may cause the window do the bounds change animation first,
and the followed by the overview transform animation.

Bug: 823769
Change-Id: I4a56349991663a20974c7bdc5c800b919241fcd4
Reviewed-on: https://chromium-review.googlesource.com/1102033
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567807}

Bug: 840952
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I58379298fe27ccebb75c043a1e1bd507efeb6baa
Reviewed-on: https://chromium-review.googlesource.com/1080798
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Roman Sorokin <rsorokin@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567806}

Purging will no longer infinitely loop when there are areas &
namespaces that are still bound, and cloning a session storage
namespace from browser commands will clone immediately and not wait
for a 'clone' from the renderer (which never comes).

Opening areas after purging also re-opens the correct storage area,
instead of opening a new storage area.

Bug: 848694, 848980, 849400
Change-Id: I63790d26efe9fad871e9127ef129c772848e7e56
Reviewed-on: https://chromium-review.googlesource.com/1098154Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567805}

In Refresh, FrameTopBorderThickness is 1 dip larger when the browser
is restored. OpaqueBrowserFrameViewLayoutTest needed to account for this
increase.

Bug: 846410
Change-Id: I4595c4d52ef955de53ef8f487fb181fb109d5f76
Reviewed-on: https://chromium-review.googlesource.com/1100382Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567804}

This CL improves accessibility of cr-input by automatically generating
aria-label on <input>, taking a best guess based on cr-input's aria-label,
label, or placeholders.

Bug: 832177
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I6847f16fa5ddca89691aca271ea077974ff5211e
Reviewed-on: https://chromium-review.googlesource.com/1097942
Commit-Queue: Scott Chen <scottchen@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567803}

In Refresh, when the omnibox receives focus it moves. The test was
assuming it would stay put, so this patch refreshes the click location
after the first click.

Bug: 846410
Change-Id: Iea0fe695efed257d679f87c55146b948f3360e0d
Reviewed-on: https://chromium-review.googlesource.com/1102117Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567802}

The wifi disabled message would show on toggle wifi off, but remain
when toggling wifi back on.

Test: manual
Bug: 823236
Change-Id: Ib232a917e45fea83a72792d0fbf30374661477d2
Reviewed-on: https://chromium-review.googlesource.com/1102896Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Xiaoyin Hu <xiaoyinh@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567801}

Per discussion with API owner, we want the behavior for invalid
params to be a bit stricter.  Prior to this change, if someone
called the API with at least one valid DomString, then we would
allow lock to be set.  This made sense when we were translating
the key_codes param into native key codes (where we couldn't
determine the difference between 'invalid for this platform' and
'invalid key for all platforms'.  Now that we use DomCodes, we
can do better validation.

The second change is to cancel any current keyboard lock requests
if the API is called with invalid params.  The scenario here
involves lock() being called correctly (request is registered) and
then a second lock call being made w/ invalid params.  Since we
reject the promise in this case, it didn't make sense to keep the
lock request since the intention by the caller was to override the
initial call.  In practice, we don't think this will occur often
but it is a case we wanted to handle better.

BUG=680809

Change-Id: I0ca54cca262761133739ab1d43f22e219792ca7c
Reviewed-on: https://chromium-review.googlesource.com/1099762
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567800}

This CL revives some of the checks from r512959 to ensure that most
extension URLs only commit in the correct extension processes.
There are several exceptions that must be accounted for.

BUG=770239, 840857

Change-Id: Id3dd2a7814041186d4de6f61e2dee440939b57d9
Reviewed-on: https://chromium-review.googlesource.com/1025075
Commit-Queue: Charlie Reis <creis@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567799}

host_->GetView() might be null.

Bug: 852264
Change-Id: I18af8aecdff6574a00283bae590aa6edacfbef94
Reviewed-on: https://chromium-review.googlesource.com/1100968Reviewed-by: Sahel Sharifymoghaddam <sahel@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567798}

Bug: 798612
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ie9bb7d1af812a96f11058c928cb32fa6491d96db
Reviewed-on: https://chromium-review.googlesource.com/981079
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567797}

Creates connections to remote devices over Bluetooth, using either the
listener role (BLE scans only) or the initiator role (a combination of BLE
advertising and scanning).

When a connection is attempted, it remains active until either an
AuthenticatedChannel is returned successfully or until the request is
explicitly removed via one of the Cancel*() functions.

Bug: 824568, 752273
Change-Id: Icda1cde32e3d4455742c1570df15b82979cd0ace
Reviewed-on: https://chromium-review.googlesource.com/1100133
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567796}

* Default Mac to 4 cores
* Add recipe names to non chromium recipes

Bug: 840631
Change-Id: Ib90206c80f41efa9e9d6aaed6977b39101a8f5a0
Reviewed-on: https://chromium-review.googlesource.com/1103221Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567795}

This reverts most of commit a51e3935.
The thread configuration for --enable-features=Mus doesn't exist anymore
and fixing mus introduced a different race for the non-mus configuration.
Since mus is no longer the plan of record, revert the initialization
order changes but keep logging and code cleanup.

Bug: 840474
Change-Id: Ifec0e3dd9601e3895d0549109be5d10387f3b8b4
Reviewed-on: https://chromium-review.googlesource.com/1101139Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567794}

NetworkConfigurationObserver::Source is no longer used for anything
useful in the code and should be removed.

TODO: NetworkConfigurationObserver itself is appears to only be used in
tests and could also be removed. The affected tests will need to be
re-factored however.

Bug: None
Change-Id: Iaee8bf535bcb24488d294a33867e1137d548eda0
Reviewed-on: https://chromium-review.googlesource.com/1099600
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567793}

This patch addes UI flag that enables by default support of CTAP2
security keys.

Bug: 780078
Change-Id: Ib182644ddf98ebc80e7ffe9fb4bc66c76c44a98b
Reviewed-on: https://chromium-review.googlesource.com/1101900
Commit-Queue: Jun Choi <hongjunchoi@chromium.org>
Reviewed-by: Kim Paulhamus <kpaulhamus@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567792}

Bug: 847265
Change-Id: I332cd4d5bd6996019e132abbd313e765f4e080d3
Reviewed-on: https://chromium-review.googlesource.com/1082662Reviewed-by: Owen Min <zmin@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Georges Khalil <georgesak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567791}

Change-Id: I670121d3b5de8720c626dedbf55218930bfd47fa
Reviewed-on: https://chromium-review.googlesource.com/1102830Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567790}

BUG=853330

Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ia30d658545ce7d3eb3397f1d1e282cbb7d581dc7
Reviewed-on: https://chromium-review.googlesource.com/1103117Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567789}

* Updates ContextualSuggestionsResult to carry finch trials
* Updates tests that use the result
* Register synthetic field trials with Chrome Metrics.

Bug: 833867
Change-Id: Id40dfc098e2165f0c6ef3228b77d47e10857ffa1
Reviewed-on: https://chromium-review.googlesource.com/1097940Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Patrick Noland <pnoland@chromium.org>
Commit-Queue: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567788}

They appear to map acceptably to kReplaceCurrentItem and kBackForward.

Change-Id: If727347cce399d0db74e28f014dd7f2e1bb1a95b
Reviewed-on: https://chromium-review.googlesource.com/1097592Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567787}

Merge internal change: 200745921

Clean up the QUIC end-to-end-test GetTestParams loop and comments.
Merge internal change: 200748036

Only run the stateless reject versions of QUIC end-to-end tests for a single test. Currently the end-to-end tests are parameterized in such a way that we run 60 different versions of each of the 80 tests in end_to_end_tests.cc. This is a *ton* of tests and contributes to net_unittests in Chromium taking a very long time.

One of the dimensions that these tests are parameterized by is stateless reject support:
* supported by the client?
* supported by the server?
* using cheap stateless rejects?
But this only affects the *handshake* and does not affect subsequent operations. So there's really no need to run all 80 tests with all the combinations of stateless reject-ness. This CL changes things so that only a single test runs with all the various stateless reject configurations and cuts the end_to_end_test runtime in half.
Merge internal change: 200763662

Change-Id: I83ac58d0b8d34692d9db309cb45cfd7c6c64622b
Bug: 806109
Reviewed-on: https://chromium-review.googlesource.com/1102895
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567786}

TBR=mahmadi@chromium.org

Bug: 852964
Change-Id: I37c1b3ef02b072abf139037d28f5fa43623ec1d8
Reviewed-on: https://chromium-review.googlesource.com/1101713Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567785}

instead of a raw pointer. Remove uses of std::unique_ptr constructor
in quic_test_packet_maker.cc.

Merge internal change: 198628722

Change-Id: I94208e9684606a5415db12c84250696b2b33fa09
Reviewed-on: https://chromium-review.googlesource.com/1080068Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567784}

See mock:
https://gallery.googleplex.com/projects/MCHbtQVoQ2HCZQkoNXdY_I0T/files/MCHbtQVoQ2HCZQdO-rPhnZZs
and
https://gallery.googleplex.com/projects/MCHbtQVoQ2HCZQkoNXdY_I0T/files/MCFZleLj6_wSjPNtk9TKJWXx

See recorded video:
https://drive.google.com/open?id=1Dyz1kLKM0pbzMV3H2gXCNKrnjZmjJnIq

Bug: 823769
Change-Id: Iad378e342477ba42fbf506dba751396f2f14b943
Reviewed-on: https://chromium-review.googlesource.com/1100378
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567783}

Navigation may not occur right away after tapping on links, causing
WaitForWebViewLoadCompletionOrTimeout to return immediately.

Bug: 851472
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I5bf173f696dceeebc0118105a74fd0b19ebb27c9
Reviewed-on: https://chromium-review.googlesource.com/1103008
Commit-Queue: John Wu <jzw@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567782}

The .Main alias is meant for the launcher activity triggering
only, so we want to ensure we don't pollute that with intents
from within Chrome.

The two sources found thus far are bookmarks and history.

BUG=789732

Change-Id: I90dc10019a2d07076439f80f3f280d4635f2e02e
Reviewed-on: https://chromium-review.googlesource.com/1102573Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567781}

Pass inactive image, overlay images, frame colors over mojo.

For the frame colors, it's easiest to verify it's working with a
theme that doesn't have frame images but does set colors. These are
relatively rare but here's an example:
  https://chrome.google.com/webstore/detail/simple-silver-aero/cnjlfhkndhkliabjhkikpnmkadfcndnd

Bug: 836992
Change-Id: I7141c6c79e1ee1229eb430e8178271ecc4673689
Reviewed-on: https://chromium-review.googlesource.com/1081161Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567780}

The layout_gravity value center does the same thing as
center_vertical|center_horizontal. This CL makes use of center.

Change-Id: I625ffe5dc5b147ed39d986d862f38ee432fbfa7a
Reviewed-on: https://chromium-review.googlesource.com/1102909Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Pedro Amaral <amaralp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567779}

From version 1.13.0 to 1.14.0
And also remove the disable deprecated warning workaround.

Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I6b7297c224fd8da40e11d0c7043671f3979f6905
Reviewed-on: https://chromium-review.googlesource.com/1101561Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567778}

TBR: tandrii
Bug: 	840631
Change-Id: Iddeb2dc15402138468ad66552c148be1304dd96c
Reviewed-on: https://chromium-review.googlesource.com/1103066Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567777}

Previously disabled because failing in asan in mash. Change to use local
functions instead of event generator and runs locally.

Test: run tests
Bug: none
Change-Id: I9aeb99fef0da41b44074cf40608db5c29bfef137
Reviewed-on: https://chromium-review.googlesource.com/1101964Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567776}

https://skia.googlesource.com/skia.git/+log/5540528f81c0..6ae5d74e8671


git log 5540528f81c0..6ae5d74e8671 --date=short --no-merges --format='%ad %ae %s'
2018-06-15 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader a62cf68ca10c..700a1a67d569 (1 commits)
2018-06-15 stephana@google.com Refresh clang_win asset
2018-06-15 egdaniel@google.com Add to include path for vulkan memory allocator so SkTypes can be found.
2018-06-15 egdaniel@google.com Fix unused propFlags in GrVkMemory.


Created with:
  gclient setdep -r src/third_party/skia@6ae5d74e8671

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

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

This provides an entry point for adjusting the display color matrix.

Bug: internal b/77489352
Test: CQ
Change-Id: I6cd67bdef8c41d2e5b0e219250de6a3bcedee301
Reviewed-on: https://chromium-review.googlesource.com/1087330Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Sean Topping <seantopping@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567774}