GitLab

changes:
Per crbug.com/740268, we get all launch review YES. Remove behind-flag
--ash-enable-persistent-window-bounds switch.

Bug: 805046
Test: device test
Change-Id: I33dfec4dd97e01c7ba159ab005cfd97cff51e215
Reviewed-on: https://chromium-review.googlesource.com/954067Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Qiang Xu <warx@google.com>
Cr-Commit-Position: refs/heads/master@{#542267}

StackLayout#setActiveStackState() is used by StackLayout to set the currently
active tab stack. This method currently takes a boolean (true for the incognito
stack, false for the normal stack). This CL changes this method to instead take
an integer representing an index, so we can support more than two tab stacks.

This CL also changes this method to return void (previously it was returning a
boolean: true if the active stack was actually changed, and false if it wasn't),
since the return value is never actually used.

Bug: 648314
Change-Id: Ief119b4a1a92f8345b2b3556f9003cf4e3092f61
Reviewed-on: https://chromium-review.googlesource.com/957274
Commit-Queue: Ryan Landay <rlanday@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542266}

The bounds of displays in display::Screen space must have the display
rotation applied. This ensures that the geometry of screen
(display::Screen) space corresponds to the geometry in physical space,
and in particular ensures that all displays have the same rendering
orientation in screen space. This patch makes cast's usage follow this
rule, which fixes the --display-rotation flag in circumstances where it
currently does not work (e.g. DRM platform with 90 or 270 degree
rotation).

As an added complication, some components such as WindowTreeHost,
PlatformWindow, and DRM platform internals use a third space called
"host" space within which each display is also allocated pixel bounds,
but in its neutral orientation instead of its screen space (== rotated to
align with physical space) orientation. This is also the space in which
drawing surfaces are allocated. This space has nothing to do with
physical space or screen space when display configuration is enabled and
exists mainly as a way to match windows with drawing surfaces and
displays when we need to produce fullscreen buffers for direct scanout.

To determine bounds of the primary display in host space for our case, we
can simply assume a rectangle positioned at 0,0 whose size is the display
bounds in screen space with the display scale and rotation cancelled back
out. Multi display setups cannot be supported with this method, but we
don't need that. Ash has a great deal of code to deal with
transformations between host space and screen space that we avoid by
using this simplified method. Code that needs to map between screen space
and host space (such as CastWindowManageAura) must make this
transformation.

All of this is fairly confusing and there are a number of hacks in the
system due to account for the different orientations of displays in host
space and screen space, but until things are cleaned up we need to follow
the conventions in order for display rotations to work properly on Cast.

Bug: internal b/74248568
Test: Pass various --display-rotation flags and get rotated output.

Change-Id: I12a8f23cd1d4b01675dd78cf364ccb8c27b706af
Reviewed-on: https://chromium-review.googlesource.com/957476Reviewed-by: Sergey Volk <servolk@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542265}

Because apparently the compass doesn't work so well and is what causes
spinning when using the thing indoors sometimes.

Bug: 695937
Change-Id: Id0e94520b1f509f133161e2c99edb9bd9775c616
Reviewed-on: https://chromium-review.googlesource.com/957471
Commit-Queue: Anna Offenwanger <offenwanger@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542264}

Looks like crbug.com/807627 has been fixed by the recent roll of wpt tools,
in which case this test won't be flaky any more.

Bug: 805463
Change-Id: I184560ed406a082c661f313047830d79d5d152d1
Reviewed-on: https://chromium-review.googlesource.com/957223Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542263}

Bug: 819761
Change-Id: I7d34886e5d12b1a77287463a6d15daf054192858
Reviewed-on: https://chromium-review.googlesource.com/956965Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542262}

Allow apps to reload themselves, and ensure the ShellDesktopControllerAura
keeps app_shell alive long enough for the app to come back up.

Add browser tests for ShellDesktopControllerAura and
chrome.runtime.reload() in AppShell.

Bug: 762642,759867
Change-Id: If09ad83e6d3073461ebf8b53afa69a6c2aab7e15
Reviewed-on: https://chromium-review.googlesource.com/912752Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542261}

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context: https://crbug.com/805539

The AutoRoll server is located here: https://afdo-chromium-roll.skia.org

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

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


TBR=gbiv@chromium.org

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

Change-Id: I5bc8b67bae8ecca593efa977270374ce6bf8fd9d
Tbr: sashab@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/956649
Commit-Queue: Joel Hockey <joelhockey@chromium.org>
Reviewed-by: Sasha Morrissey <sashab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542259}

Will be used in AXPosition and AXRange to adjust AX selection and move AX positions to valid DOM objects.
See https://chromium-review.googlesource.com/c/chromium/src/+/954182 for the selection changes.
R=dmazzoni@chromium.org, aboxhall@chromium.org

Change-Id: I798e353262e6fea3166b74e20ef09e327ccfcd4d
Reviewed-on: https://chromium-review.googlesource.com/955728
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542258}

We used to fake out the Gpu::Capabilities in TestInProcessContextProvider with some custom logic.
This logic appears to be redundant with the actual capabilities we can get from the real context.
Additionally, as this code is used in pixel tests, having fake capabilities that mismatch with the
real capabilities seems risky, so if the real caps are working it feels like we should use them.

Also cleans up some other unused code.

R=enne

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I1bf82739387a358e95372efb1dac571d7ed15cbe
Reviewed-on: https://chromium-review.googlesource.com/957315Reviewed-by: enne <enne@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542257}

Bug: angleproject:2396
No-Try: True
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: I72f61722121e4580b5d24331cf7d19c54f16b396
Reviewed-on: https://chromium-review.googlesource.com/957310
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542256}

Changes:
1. Add a HorizontalPageContainer between AppsContainerView and its
   parent view, ContentsView. The HorizontalPageContainer serves as a
   container for a list of HorizontalPage. It enables pagination and
   supports switching pages via gesture scrolling.
2. Make AppsContainerView extend HorizontalPage to become one of the
   surface page.
3. In the future, more surface pages can be easily added in
   HorizontalPageContainer without the need to handle switching page
   themselves.

BUG=820205

Change-Id: I8c75b41b475af8ab67044571bbed8a8f73dac92c
Reviewed-on: https://chromium-review.googlesource.com/947050Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542255}

GpuMemoryBufferVideoFramePool was initially used by VideoRendererImpl,
and it assumed at most one copy at a time would be requested.
If a new copy was requested before the previous one finished, there
was no guarantee that the frame ready callback would be called in the
same order as the copy request.

crrev.com/947383 moved the copy to GMB, and the pool, in an earlier
stage of video playback. Now more than on copy could be requested,
and the pool might deliver videoframes out of order.

This patch adds the guarantee that GMBVP will deliver frames in the
same orders the copy were requested.

Bug: 819635
Change-Id: Ic8fd5e95bcda59c836e6be65eaa3891ace0b1aa7
Reviewed-on: https://chromium-review.googlesource.com/955912
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542254}

This is split out from the CL to test all widgets and views for nameless
focusable objects. See crrev.com/c/951933.

Bug: 819350
Change-Id: Ie5e8a17f1656ce1c7545dadacee163499563da70
Reviewed-on: https://chromium-review.googlesource.com/952330Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542253}

This change updates the DeleteEntry method on SmbFileSystem to use
GetDeleteList. When a DeleteEntry call comes in from the Files API,
SmbFileSystem first makes a call to GetDeleteList in order to get an
ordered list of entries that need to be deleted, and subsequently
calls DeleteEntry on each entry in the list.

If there is an error generating the delete_list, delete will still
be attempted on any entries in the delete_list, and the error will
be returned. Otherwise (ie generating the delete_list succeeds), the
error_code from performing the deletes willbe returned.


Bug: chromium:757625
Test: verified recursive delete still works on Eve
Change-Id: I1afb3498ee51280d70291dd31f50a550129c4381
Reviewed-on: https://chromium-review.googlesource.com/937881Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542252}

When preparing hit-test data for browser and renderer, use the inverse
of render_pass->transform_to_root_target as the transform from the root
target. This transform is identity in most cases but not in very
complicated cases (e.g. https://codepen.io/anon/pen/WMqxrE by weiliangc).

Bug: 806144
Test: viz_unittests
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I08e46b45a49da1b42ae1c32f6aafaf7a54aabf42
Reviewed-on: https://chromium-review.googlesource.com/951842Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: weiliangc <weiliangc@chromium.org>
Commit-Queue: Ria Jiang <riajiang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542251}

Opening a link in a new tab on low end devices freezes the tab to be
lazily loaded when the tab is used for the first time. Opening links
with intents from a frozen state causes us to override the URL handling
with the external intent which results in an app being launched on
selecting that tab, or the picker being shown, instead of seeing the
contents at the URL displayed in the tab.

This patch treats the page transition type sent to #loadUrl as RELOAD
whenever we're loading a URL for the first time in a frozen tab which
avoids starting another activity.

Bug: 758027
Change-Id: I89e63fb51b00d1c62b12c8f6d827e3e907e463b1
Reviewed-on: https://chromium-review.googlesource.com/956558Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Commit-Queue: Troy Hildebrandt <thildebr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542250}

The logic was incorrectly reversed.

Change-Id: I565779c96fd6cc55dfbb81f629df6b3a7864caa4
Reviewed-on: https://chromium-review.googlesource.com/957522Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542249}

This change implements a GetDeleteList function on
SmbProviderClient that maps to the GetDeleteList fn
on the SmbProvider daemon.

Bug: chromium:757625
Change-Id: I7e4e4a8f0e7f21a92c8dd9edd72ad4e26bd6cd07
Reviewed-on: https://chromium-review.googlesource.com/937815Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542248}

This reverts commit 886289a7.

Reason for revert: Compile error when building chrome for Caroline using simple Chrome flow. See crbug.com/820601 for details.

Bug: 820601

Original change's description:
> libgestures_glue: Send MSC_TIMESTAMP if available
> 
> If an event from libevdev includes a MSC_TIMESTAMP field, send that
> timestamp to the gesture library. This field will be used by the gesture
> library because it has more accurate time deltas than CLOCK_MONOTONIC.
> 
> BUG=b:65041115
> TEST=Tested manually on lux and eve, using CL:742488 and CL:938751.
> MSC_TIMESTAMP is passed to gesture library if available.
> 
> Change-Id: I05e5a6615e10d33bd0e290b6bb8ff11c2f05f2fc
> Reviewed-on: https://chromium-review.googlesource.com/817979
> Reviewed-by: Michael Spang <spang@chromium.org>
> Commit-Queue: Sean O'Brien <seobrien@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#542190}

TBR=spang@chromium.org,seobrien@chromium.org

Change-Id: Iec92ec30b9451d0a95ac7600c803850912492675
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: b:65041115
Reviewed-on: https://chromium-review.googlesource.com/957603Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542247}

This changes the previous 1:1 TQ:thread relationship and associates
WebRTC task queues with Chromium's thread pool.

The effect of this is that PeerConnection objects, will start
to share threads for "rtc_event_log", "EncoderQueue" and
"call_worker_queue".

Constructing an instance of PeerConnection will be much less
costly and likely not cost any extra thread creation at all,
which is why we currently have a limit on the number of
instances that we allow creating.

Change-Id: Ifd218c5e14e2ce634fd428606e9713a815bd8205
Bug: 808801
Reviewed-on: https://chromium-review.googlesource.com/890738
Commit-Queue: Tommi <tommi@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542246}

This is split out from the CL to test all widgets and views for nameless
focusable objects. See crrev.com/c/951933.

Bug: 819350
Change-Id: I4eb266d06d6468657b2cf00873a601efb976166c
Reviewed-on: https://chromium-review.googlesource.com/952327Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542245}

Fix ios-device-xcode-clang compilation error introduced by https://chromium-review.googlesource.com/c/chromium/src/+/956843

The compilation error appears to be due to clang bug
https://bugs.llvm.org/show_bug.cgi?id=21629 , which has been fixed recently,
but apparently has not made it into the clang used by ios-device-xcode-clang.

R=rch@chromium.org

Bug: 820529
Change-Id: Iaac1d28f2209502c4ce4683b3f590d9140fe3141
Reviewed-on: https://chromium-review.googlesource.com/956299Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Michael Warres <mpw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542244}

The cancel button on the navigation bar is currently overlapping the
notch on the top of the screen on iPhone X. The issue is that we didn't
make the navigation bar respect to the safe area when laying it out.

This CL fixes this by laying out the navigation bar on the top of the
safe area rather than on the top of the view.

Bug: 820547
Change-Id: I41494d01ab7f12a00b8a5bd4f3523245d3362e60
Reviewed-on: https://chromium-review.googlesource.com/957132Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542243}

This CL implements the needed changes for the toolbar buttons,
and the app menu button. The browser actions container will be
done in a follow-up CL.

BUG=818034

Change-Id: I0d8ec316aa98e553e77bef34d4ca120dd9c2f09f
Reviewed-on: https://chromium-review.googlesource.com/947385Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542242}

To ensure CastRemotingSender::ProcessNextInputTask is not run after
CastRemotingSender is destructed.

Bug: 820397
Change-Id: Ic97abf03fe9a264403162a51ac4458365a60efc8
Reviewed-on: https://chromium-review.googlesource.com/956750
Commit-Queue: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542241}

atomicops.h was fixed in January to not depend on Windows.h anymore.
Update the comment to reflect that, and enforce it in the unit test.

Bug: 559247, 796644
Change-Id: I95762b818d135f6f400e1b9aa66567464aef8951
Reviewed-on: https://chromium-review.googlesource.com/956668Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542240}

Deletes old table view DataSource implementation and creates a TableViewModel instead.
Moves Item/Cell configuration logic from recent_tabs/views/ into the VC.
Some helper methods are being re-used.


Screenshots:
https://drive.google.com/open?id=1n-IYyIffatHC2ok9fnvyIRhqH6rLADuh
https://drive.google.com/open?id=14NuWwnYFncYfijRpjIuy8kQ-EDYuIze6

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: If997fb74862d135ff68e2b4aafd930d90f13f159
Reviewed-on: https://chromium-review.googlesource.com/954227
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542239}

Changing the ClientHintsBrowserTest browser tests to use
URLLoaderInterceptor. This fixes 2 tests with the network service.

Bug: 776589
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Icfa0f2c26723de4a1c0f815411ab39e1b016d61d
Reviewed-on: https://chromium-review.googlesource.com/956753Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542238}

Remove remaining usages of MediaStatus.description field.  It is no longer used
in the UI or in the extension in M67+.

Bug: 786208
Change-Id: I19269d3a317be05765773c53b906aa75277b0407
Reviewed-on: https://chromium-review.googlesource.com/956743Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Derek Cheng <imcheng@chromium.org>
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542237}

ioctl_netc_get_if_info() has been replaced with ioctl_netc_get_num_ifs()
and ioctl_netc_get_num_ifs(). Update the corresponding code in //net.

Bug: 818320
Change-Id: I42746f97616000f8839bcb0433c42e1d7feca129
Reviewed-on: https://chromium-review.googlesource.com/956613
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542236}

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

StackLayout#flingStacks() currently takes a boolean: true if we should scroll over to the incognito
tab stack, and false if we should scroll over to the normal tab stack.

This CL is a straightforward change to make this method instead take an integer value representing
the index of the new tab stack. This is necessary to enable StackLayout to support more than two
tab stacks.

Bug: 648314
Change-Id: I4e58707c1e389638fca1c6a013abf022a8d248bc
Reviewed-on: https://chromium-review.googlesource.com/957425Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Ryan Landay <rlanday@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542234}

https://skia.googlesource.com/skia.git/+log/b537879c7214..43f0ba073068

$ git log b537879c7..43f0ba073 --date=short --no-merges --format='%ad %ae %s'
2018-03-09 reed update tool to sniff images during deserialization
2018-03-09 egdaniel Fix no gpu build
2018-03-09 herb Remove getCache from SkAutoGlyphCache*
2018-03-09 bsalomon Fix breakage from merge conflict related to deleteTestingOnlyBackendTexture sig. change
2018-03-09 robertphillips Enable opList-based DDLs
2018-03-09 bsalomon Make GrGpu::deleteTestingOnlyBackendTexture() take const GrBackendTexture&
2018-03-09 brianosman Fix a logical test in GrColorSpaceXform::Equals
2018-03-09 egdaniel Add promise images for deferred instantiation of wrapped gpu textures
2018-03-09 herb Remove one use of AttachCache, and a paint variant of FindOrCreate...
2018-03-09 robertphillips Make GrTextureStripAtlas DDL friendly
2018-03-09 bsalomon Vulkan backend render targets don't allow client to specify stencil bits
2018-03-09 angle-skia-autoroll Roll skia/third_party/externals/angle2/ e8a93c6ed..331404098 (1 commit)
2018-03-09 update-skps Update SKP version
2018-03-08 csmartdalton ccpr: Fix stale array access after dynamic resize
2018-03-09 bsalomon Add GM configs that test rendering to a GL backend texture and render target
2018-03-08 csmartdalton ccpr: Fix crash on zero-length fan tessellations
2018-03-09 herb Remove all uses of getCache with get.
2018-03-08 bungeman Avoid serializing to 'typ1' on Mac.
2018-03-09 caryclark some fuzzer fixes

Created with:
  roll-dep src/third_party/skia
BUG=809763


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;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
TBR=fmalita@chromium.org

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

This CL reverts the GPU process to the V1 sandbox while a series of
hangs are resolved.

Tbr: creis@chromium.org
Bug: 812228
Change-Id: Ie87cf5228d19cf3c50892b2f19133c3d3f2e2593
Reviewed-on: https://chromium-review.googlesource.com/957463
Commit-Queue: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542232}

This implements a CursorView class based on FastInkView. It
provides smooth low-latency cursor movement with optional
motion blur on Chrome OS devices, especially devices with
HW overlay support.

Single buffer updates are done on a high priority cursor
paint thread and events are routed directly to this thread
from the EVDEV thread. This provides minimum latency
updates that are not affected by any work done on the UI
thread. The result is smoothness guarantees that are as
good or better than existing HW cursor on Chrome OS devices.

Fast ink based cursor is currently limited to when motion
blur is enabled but can become the default mechanism to
display the cursor. And as a result allow the HW overlay
currently assigned to the HW cursor to be used for contents
and apps.

Bug: 722793
Test: chrome --ash-enable-cursor-motion-blur
Change-Id: I2baf0b5746610aca33f44b966556304d4cfc700c
Reviewed-on: https://chromium-review.googlesource.com/846992Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: David Reveman <reveman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542231}

There is a bug that when we switch from network1 to network2, DIAL devices
from network1 stays on MR dialog.

Current implementation will not restart the timer and notify
extension about sink list changes if network2 has no DIAL device.

Fix it by always restart time when we get DIAL device events from
DIAL registry.

Bug: 820215
Change-Id: Ia149778427f142bffbb9ebd61b0de920b7a54289
Reviewed-on: https://chromium-review.googlesource.com/956310Reviewed-by: Derek Cheng <imcheng@chromium.org>
Commit-Queue: Bin Zhao <zhaobin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542230}

In webview, frames with no damage sometimes call AbortDraw to prevent
draws. These aborts should not set did_draw_in_last_frame_ or the
scheduler will request new BeginFrames when it doesn't need to.

This CL stops setting did_draw_in_last_frame_ in AbortDraw while still
setting it in WillDraw.

Bug: 687695
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I84c39a5e06d578ea92558d81ce2fad5dc423cf75
Reviewed-on: https://chromium-review.googlesource.com/933292
Commit-Queue: James Wallace-Lee <jamwalla@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542229}

Change-Id: Id06be3a64b74d8453fd79cfa5915b4490e943d7c
Reviewed-on: https://chromium-review.googlesource.com/956876Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542228}