GitLab

Fixes a couple of issues where frame capture becomes frozen or choppy,
with the following changes:

1. Move the "source dirty" logic out of VideoCaptureOracle and into
FrameSinkVideoCapturerImpl.

2. More-agressive response to frame refresh requests (needed for
improved mouse cursor update response).

3. Remove the distinction between passive and active refreshes from
VideoCaptureOracle. FrameSinkVideoCapturer now tracks source damage, and
can execute any refresh passively when there is no damage.

4. Add logic to ensure that FrameSinkVideoCapturerImpl provides
consumers with a refresh frame whenever key events occur; such as params
changes, capture target changes, etc.; that are known to require a full
update.

5. Re-enable the content_browsertests that were disabled due to
flakiness.

Bug: 785072, 754872
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I402f3f928de61e6754e04014327421e4f6917d5f
Reviewed-on: https://chromium-review.googlesource.com/884996Reviewed-by: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Xiangjun Zhang <xjz@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532161}

The driver bug's been fixed in 10.13.4.

Bug: 775202
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: Ie068990d23884956b614705aa9f7abf81953cec0
Reviewed-on: https://chromium-review.googlesource.com/889414
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532160}

Bug: 770324
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ib33f369309e59128a134e8f4120e46f647373d16
Reviewed-on: https://chromium-review.googlesource.com/869136
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532159}

font-feature-settings accepts an integer, but the code for parsing that
integer did not check for calc() values. Update the code to accept
calculated integers.

Bug: 397061
Change-Id: I33ed1538f8148257f22a3e67cbd3478e523a1ff5
Reviewed-on: https://chromium-review.googlesource.com/888161Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Chris Nardi <cnardi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532158}

The wrapper function is called only once, and doesn't wrap complicated
logic. Removing it makes the code easier to read.

Change-Id: If416aa671221d646fc60271e681a8d2eedc28834
Reviewed-on: https://chromium-review.googlesource.com/889640Reviewed-by: Ryan Landay <rlanday@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532157}

A deadline should never be set more than once for a CompositorFrame
unless a client explicitly requests a second shot. This CL resets
the deadline in frames to 0 on a SurfaceLayer after commit and after
activation from pending to active layer trees. If the client expliclty
requests a new deadline, then another shot will be taken. base::nullopt
signifies to use whatever default deadline the viz service decides.

Bug: 707510, 672962
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I856c74a2c50f287d1085b4b99330c42ba6bbeb64
Reviewed-on: https://chromium-review.googlesource.com/887743
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532156}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=anantha@chromium.org

Change-Id: Ib47ae6b7e46083290cad343b843fec4991cb4a25
Reviewed-on: https://chromium-review.googlesource.com/889963Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532155}

Bug: 806328
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ic11d57e15fdd3645365c07d80addd672b838ac3e
Reviewed-on: https://chromium-review.googlesource.com/889680Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532154}

For security reasons, it is not valid for script to call getClass, which would
allow it to reach the Java reflection APIs. Reject any attempts (but allow uses
of other methods named "getClass"), and report it to an auditing object.

Provide an implementation of the auditor intended for use in production, which
writes to EventLog. This is not inline in the class, as content_junit_tests doesn't
fully initialize the Android framework and so cannot call Process.myUid.

Bug: 794320
Change-Id: I56d2467e5d15c0d886ce46c63c1bdcc00cf8335c
Reviewed-on: https://chromium-review.googlesource.com/881555
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532153}

https://chromium-review.googlesource.com/c/chromium/src/+/775606 that is
causing collisions on cookie creation time.

This is a quick fix of problems
being seen in the field; a longer term fix is being tracked in
http://crbug.com/800414.

Bug: 800414
Bug: 795827
Bug: 794453
Change-Id: I0ff206fdc517e20f270cebadc6b64704f4c18d21
Reviewed-on: https://chromium-review.googlesource.com/889958Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Randy Smith <rdsmith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532152}

With mojo blobs a blob handle is passed all the way across from the
browser process to blink so there should be no need for blob acking
anymore.

Bug: 805597
Change-Id: I11a59f4af80df4c13c73ee5d7761a07a1a38129a
Reviewed-on: https://chromium-review.googlesource.com/883980Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532151}

This CL:
- introduces ChildURLLoaderFactoryBundle which is a subclass of
  URLLoaderFactoryBundle with support for a direct network loader factory and
  lazy initialization for certain factories. It is basically the combination of
  URLLoaderFactoryBundle and ChildURLLoaderFactoryGetter.

- replaces all usage of URLLoaderFactoryBundle and ChildURLLoaderFactoryGetter
  in renderer with ChildURLLoaderFactoryBundle.

Bug: 796425

TBR=jam@chromium.org
(for removing an include from chrome/renderer/net/net_error_helper.cc)

Change-Id: I1d3a1141bc35340ae586fc30df6496eb84a26c29
Reviewed-on: https://chromium-review.googlesource.com/882606
Commit-Queue: Yuzhu Shen <yzshen@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Yuzhu Shen <yzshen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532150}

This prevents animations from updating twice as fast for webview
plugins because plugins have their lifecycle run as part of the
containing plage, then have Paint() called on them.

Bug: 737787
Change-Id: I7596d2d0dd74f5733a8d32e8d381662a88708eba
Reviewed-on: https://chromium-review.googlesource.com/888170
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532149}

Merge internal change: 183282622

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

Also remove last usage of these deprecated constructors (mostly in tests,
where just passing a dangling mojo message pipe works fine).

Bug: 769024
Change-Id: I38b390e64552abc971035eec97d090a85ec701f9
Reviewed-on: https://chromium-review.googlesource.com/883570Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Chris Mumford <cmumford@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532147}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/508734bf..2fce0c43

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,sergiyb@chromium.org

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

https://chromium.googlesource.com/chromium/src/+/e76e0e99dc3b8b2b7ad502603331ea7104745a1a

This reverts commit 8e96399b.

The original CL was reverted because of two consecutive unconditional returns within the same function, which was causing Windows MSVC build failures. This CL adds the preprocessor command to avoid this issue.

TBR=rohitrao
for mechanical changes to ios/c/b/a/*

Change-Id: I823b815ae29f154df25391c21c0c43ec485192d5
Reviewed-on: https://chromium-review.googlesource.com/889698Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Gheorghe Comanici <gcomanici@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532145}

This makes DisposeContext consistent with DisposeAllContexts in that
it cancels out the implicit Enter of the "main" context. Two tests that
relied on this not happening need to be tweaked for it.

This resolves an LSAN failure in another patch.

Change-Id: Iac7312610cb63feed2c2eb20227d40d6a2197460
Reviewed-on: https://chromium-review.googlesource.com/887658
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532144}

Fixes a bug where Renderer4.LockExistingCachedImage.Software.SOON and
Renderer4.LockExistingCachedImage.Software.EVENTUALLY were overcounted,
and removes a redundant check from a test.

Bug: 177475
R=danakj@chromium.org

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I531d3f661c4d893412fb074b7f1b9a3c8ba8bc41
Reviewed-on: https://chromium-review.googlesource.com/889719Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532143}

This CL creates a button that enters window repositioning mode. There
is still a great deal of work to be done -- the behavior once we're in
the mode is not what we ultimately want -- but this gets some of the
infrastructure out of the way. Subsequent patches will refine the
repositioning UX.

Bug: 799270
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I826a5868d17ee2d1ed5e69b7e1c75eb81142623e
Reviewed-on: https://chromium-review.googlesource.com/888540Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532142}

This CL removes the DeleteSoon()s for  |decoder_| and |*_accelerator|s
as a speculative fix for the second bug below crbug.com/799204 that
tracks a crash on the field.

It leaves most of the SEQUENCE_CHECKER usage, since this is useful
as documentation-in-code, and leaves a few TODO()s to figure out,
if DeleteSoon() proves the culprit, why doing the right thing leads
to crashes.

from crosvideo.appspot.com, compiled with dcheck_always_on=true

Bug: 789160,799204
TEST: Tested via simplechrome on Soraka playing back VP9 videos
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: I6dace88a448a08bdf441725701347968326442ac
Reviewed-on: https://chromium-review.googlesource.com/889143Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532141}

Change-Id: I8e7854752054f0e4ac1c88fe9b9ec5e9e9547876
Reviewed-on: https://chromium-review.googlesource.com/885422
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532140}

Bug: 177475
R=sky@chromium.org

Change-Id: I50a90b6d627f831e31819abca4494c1b2d54600d
Reviewed-on: https://chromium-review.googlesource.com/889844
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532139}

Bug: 177475
R=tdresser@chromium.org

Change-Id: I4e7c08b812cdc818ec51f3cf1b68ed4e8b63d39b
Reviewed-on: https://chromium-review.googlesource.com/889722Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532138}

Bug: 177475
R=dtrainor@chromium.org

Change-Id: Iae75d4ee55a8246d599dff7b8519bc5115b40c9c
Reviewed-on: https://chromium-review.googlesource.com/889785Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532137}

This CL adds gl_unittests to chromium.gpu.fyi, hence making it
run, among others, on the Mac nVidia bot that caused the original
CL to be reverted.

There's more information on the bug but, in a nutshell, the
original CL was reverted due to a specific nVidia bug that
manifested itself on the chromium.gpu.fyi mac bot; however,
it doesn't show up in the mac_optional_gpu_rel. So, this CL
has no specific nVidia provisions, just reenables the test,
and we'll see what happens in the chromium.gpu.fyi waterfall :-)


Bug: 803473
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: I71c0451d2e3b53baa3bd24bafdf1f7a5f1210363
Reviewed-on: https://chromium-review.googlesource.com/886543Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532136}

Bug: 177475
R=oshima@chromium.org

Change-Id: Id75257a2890576c0ff7c913fcb3daccf8296839a
Reviewed-on: https://chromium-review.googlesource.com/889778Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532135}

We're going to use blink::CreateElementFlags in more header files, and
would like to avoid to include huge Document.h.

This CL has no behavior changes.

Bug: 805280
Change-Id: I64c89995cda3f76f1e75b6cf20af05f0e8eb2e24
Reviewed-on: https://chromium-review.googlesource.com/888191Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532134}

They are no longer necessary now we move everything to GPU side.

Also, remove process_crash_count from GPUInfo because this is valid
in browser process only, but it's mis-used on renderer side.

BUG=744658
TEST=bots
R=kbr@chromium.org,piman@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: I896c299e72554dae6c9698f56a808425a738c9be
Reviewed-on: https://chromium-review.googlesource.com/887349Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532133}

Add 2 policy settings for PhishGuard.
PasswordProtectionWarningTrigger controls if we show the model dialog warning.
PasswordProtectionRiskTrigger controls if we do event logging for at-risk account.

If there is no policy for these for settings, then PhishGuard works the
same way as for non-enterprise users. With the exception that, for
GSUITE users, PhishGuard warning and at-risk account flagging is off by
default.

Bug: 804490
Change-Id: I6ff1cc71222217c168ca0bbebf36dac4be946a43
Reviewed-on: https://chromium-review.googlesource.com/879429
Commit-Queue: Jialiu Lin <jialiul@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: Bartosz Fabianowski <bartfab@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532132}

Bug: 177475
R=bajones@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: I0034f33d1d5b307d61bcc04dabb624bfe6a0bace
Reviewed-on: https://chromium-review.googlesource.com/889819
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532131}

Bug: 177475
R=kbr@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: I3048cd151bc720d0edbacbec698723f07b65842a
Reviewed-on: https://chromium-review.googlesource.com/889760
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532130}

Bug: 177475
R=palmer@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_arm64_dbg_recipe;master.tryserver.chromium.android:android_compile_mips_dbg;master.tryserver.chromium.android:android_compile_x64_dbg;master.tryserver.chromium.android:android_compile_x86_dbg
Change-Id: I361d9b71990cbb9870760709748d1928055b779c
Reviewed-on: https://chromium-review.googlesource.com/889787
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Chris Palmer <palmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532129}

Fixes two issues with how incognito extension prefs changes are
dispatched when the extension is in split incognito mode:
 1. If an extension was incognito split, but not incognito enabled, the
    incognito prefs changes were dispatched to the the extension's
    original profile instance (even though extension in the original
    profile generally cannot access incognito prefs). This CL does not
    dispatch incognito pref changes to extensions that are not
    incognito enabled.
 2. If an incognito pref change was dispatched to an incognito split
    extension when OTR profile was not around, in order to restrict
    the preference to the OTR profile, DispatchEventToExtensions()
    function would call Profile::GetOffTheRecordProfile which would
    create an OTR profile instance. This cl avoids this issue by
    dropping  the events that are expected to be restricted to a
    non-existent OTR profiles
    (Note: if the pref value changed in the original profile, and there
     is no incognito specific pref value, the value change is reported
     for the incognito pref, too),

BUG=796814,805480

Change-Id: I093949c9f9123e3baaab56932903f4f2be55903c
Reviewed-on: https://chromium-review.googlesource.com/882508
Commit-Queue: Toni Barzic <tbarzic@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532128}

Bug: 177475
R=miu@chromium.org

Change-Id: I7aa7196b1b325b0741e6c7bb60822ac6d59dc295
Reviewed-on: https://chromium-review.googlesource.com/889780Reviewed-by: Yuri Wiitala <miu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532127}

Save sync password hash when user clicks "Sign in again" button in the
account menu. This sync password hash is used to detect gaia password
reuses.

Bug: 790824
Change-Id: I420162773e03fb5b99341a6da6c96a49a2a1efba
Reviewed-on: https://chromium-review.googlesource.com/879468Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Jialiu Lin <jialiul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532126}

The interface is used from chrome os camera hal for jpeg decoding. For
the compatibility issue between the Mojo versions of chrome os and
chrome. Shared buffer handle serialization is not supported between
the old version and the new version. We create a new DecodeWithFD in
GpuJpegDecodeAccelerator Mojo interface.

BUG=chromium:780009
TEST=Run gpu_jpeg_decode_accelerator_unittest to check Mojo
interfaces.
Decode a real jpeg image from chrome os by the Mojo interfaces.
Run camera app.

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: I8e7df9543dd532dc2457f334245593b6722a71fb
Reviewed-on: https://chromium-review.googlesource.com/670541Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Christian Fremerey <chfremer@chromium.org>
Commit-Queue: Hsu Wei-Cheng <mojahsu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532125}

Bug: 874525
Change-Id: I1da32dc0179563938875f8a740635a10287570a4
Reviewed-on: https://chromium-review.googlesource.com/877504Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532124}

Bug: 738611
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Iad8fde7df949176ce836671916de50db6fa7099e
Reviewed-on: https://chromium-review.googlesource.com/882465
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532123}

TouchSelectionForCrossProcessFramesTests/TouchSelectionControllerClientAuraSiteIsolationTest.BasicSelectionIsolatedScrollMainframe/1 fails on all the platforms.

TBR=tdresser@chromium.org

Bug: 805017
Change-Id: I1ea7c82a4c8fc2fa8e83c83ac47ef65f98cd985f
Reviewed-on: https://chromium-review.googlesource.com/888753Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532122}