GitLab

This is largely a copy-and-paste from GLES2DecoderImpl, with some minor
cleanup.

- added a vertex array manager to RasterDecoderImpl and copied
  associated boilerplate because it was required by
  CopyTextureCHROMIUMResourceManager

- copied GLES2DecoderImpl::CopySubTextureHelper as
  RasterDecoderImpl::CopySubTexture with very minor modification
  (e.g. raster is given a destination texture ID instead of the target
  that GLES2 takes)

- added a unittest to verify that source and destination textures are
  cleared appropriately

Bug: 789238
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;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I1eb50e43cc52ee9931a483ab89f9cdbdf47e2332
Reviewed-on: https://chromium-review.googlesource.com/993763
Commit-Queue: Jonathan Backer <backer@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548258}

The GroupCoordinator will be used in the new Audio Service loopback and
muting features. It tracks one or more audio outputs that are members of
the same group, and notifies interested entities (e.g., a muter, a
loopback mixer, etc.) of membership changes to the group.

Bug: 824019
Change-Id: I9b8b1564e8fa7977d2d8dd21c466c7cbf5cdd3f2
Reviewed-on: https://chromium-review.googlesource.com/987093Reviewed-by: Max Morin <maxmorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548257}

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ie30ec32ff379dca98f964e2a0de0e786eec8026f
Reviewed-on: https://chromium-review.googlesource.com/994498Reviewed-by: Naoki Fukino <fukino@chromium.org>
Commit-Queue: Sasha Morrissey <sashab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548256}

Offline pages need a custom version of the menu items shown by CCT. This
change creates a custom UI type for presenting offline pages that
properly configures the menu and also disables the "powered by Chrome"
footer.

Bug: 824807
Change-Id: Ic20f03ee152b8f538161810e87bc0e514886a3e7
Reviewed-on: https://chromium-review.googlesource.com/996395Reviewed-by: Jian Li <jianli@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Carlos Knippschild <carlosk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548255}

This came up as part of an effort to switch |is_posix| to false in Fuchsia.

Bug: 812974
Change-Id: Ic8d4b745e4e88620d6ad598223d41d0b3ca08a3f
Reviewed-on: https://chromium-review.googlesource.com/988850Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548254}

This brings it up to revision 6aa3b57955fed5e137d0306478e1a4b424a6d392, which includes the following two changes:

* Support for reversed dates in timeRange() and dateRange():
  https://hg.mozilla.org/mozilla-central/rev/cd913073f87c
* Additional validation of IP(v4) literals in isInNet:
  https://hg.mozilla.org/mozilla-central/rev/dd66d01e757c

Bug: 827292
Change-Id: I3d6670c7ceed0fc1bc453d6892922ffb047ab2bc
Reviewed-on: https://chromium-review.googlesource.com/986949
Commit-Queue: Eric Roman <eroman@chromium.org>
Reviewed-by: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548253}

Bug: 829092
Change-Id: Ibfe49a09148cfcd7b6fb489eadfbc5b43bb682ec
Reviewed-on: https://chromium-review.googlesource.com/996570Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548252}

Replacing tdresser@

Change-Id: I74625e1844b5403fc63a7d20d98aaaff1529f6a6
Reviewed-on: https://chromium-review.googlesource.com/993397Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548251}

CRWWebController removes WKWebView when the web process is evicted
(crbug/815248). This leaves WKBasedNavigationManager in an inconsistent
state as previous_item_index_ may not be -1, but GetItemCount() is 0.
This causes a crash in OnNavigationItemCommitted() when user starts a
new navigation by typing into the omnibox.

Fix the crash by guarding the pointer dereference with a nullptr check.

Bug: 797756
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ie553efbe7bb558a8af955ca6f64e2b8aea58aacd
Reviewed-on: https://chromium-review.googlesource.com/996436Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Danyao Wang <danyao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548250}

This reverts commit ef18e86a.

Reason for revert: Make sure apk_merger.py works with and without the
unwind file, till downstream cl lands. Also rebase on:
https://chromium-review.googlesource.com/c/chromium/src/+/994545
and remove workaround for crbug/828528.

Original change's description:
> Revert "Enable extracting unwind table on official builds without channel"
>
> This reverts commit 16e808d7.
>
> Reason for revert: Merge step still failing.
>
> Original change's description:
> > Enable extracting unwind table on official builds without channel
> >
> > The original cl was here:
> > https://chromium-review.googlesource.com/c/chromium/src/+/990092
> > This CL fixes the following problems with the original CL:
> > 1. The apk_merger script fails because the unwind tables were only added
> >    in 32-bit apk. The merger script expects all the files to be same and
> >    the ones different should be checked.
> >  1a. The resources.arsc is non-hermetic and ordering is affected by
> >      adding file to only one apk. As a workaround for crbug/828528,
> >      add an empty (valid) unwind table file to the 64 bit monochrome
> >      apk to make the resource.arsc consistent.
> >  1b. The merger script simply adds all the files in apk which are not
> >      same. To keep the script simple and functional, the unwind resource
> >      is renamed to unwind_cfi_32 and unwind_cfi_empty in respective
> >      builds and the app_merger is updated to specify this file is
> >      expected to be different and included. This causes an extra file
> >      (4 byte) in the merged apk.
> >
> > 2. The unwind tables were always generated for "libchrome.so" for all
> >    chrome apks. The different chrome_apk(s) have different shared
> >    libraries like libchromefortest, etc.. So, update the unwind asset to
> >    get unwind table for the right library for each apk. Only adds assets
> >    to *_public_apk(s).
> >
> > 3. The monochrome_apk_checker was failing because the unwind file
> >    included was different in chrome_apk and monochrome_apk. This CL adds
> >    the asset to all apk at the same time and adds exception for this
> >    file.
> >
> > BUG=819888
> > TBR=dpranke@chromium.org
> >
> > Change-Id: Ibceeeacc19fa424d519891b8c17e349ee6c2dfd6
> > Reviewed-on: https://chromium-review.googlesource.com/991236
> > Commit-Queue: Siddhartha S <ssid@chromium.org>
> > Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
> > Reviewed-by: Bo <boliu@chromium.org>
> > Reviewed-by: agrieve <agrieve@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#547993}
>
> TBR=boliu@chromium.org,dpranke@chromium.org,mariakhomenko@chromium.org,changwan@chromium.org,ssid@chromium.org,agrieve@chromium.org
>
> Change-Id: I0a96e213133b6cb21c36db365b7c72f0f4642c8e
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 819888
> Bug: 828879
> Reviewed-on: https://chromium-review.googlesource.com/995697
> Reviewed-by: Anthony Berent <aberent@chromium.org>
> Commit-Queue: Anthony Berent <aberent@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#548066}

TBR=dpranke@chromium.org,mariakhomenko@chromium.org

Bug: 819888, 828879
Change-Id: I2eba81de32632bea90171ece4cba1a4144c55d25
Reviewed-on: https://chromium-review.googlesource.com/996272
Commit-Queue: Siddhartha S <ssid@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Changwan Ryu <changwan@chromium.org>
Reviewed-by: Siddhartha S <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548249}

Changed chrome://connection-help UI to automatically expand a section
if it matches the interstitial that caused the redirection.
Also removed windows only section on non-windows platforms.

Change-Id: I1287a4bdbc95d9cd5052212194450e72a3ebb18e
Reviewed-on: https://chromium-review.googlesource.com/988838
Commit-Queue: Carlos IL <carlosil@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548248}

This CL has no intended behavior change.

In addition to moving and renaming the classes, this CL:
  * Renamed all classes to remove "memlog_" or "profiling_" prefixes.
  * Removed profiling_constants.h and profiling_constants.cc, which were unused.
  * Moved binding logic from profiling_client.cc into chrome_content_client.cc
    to meet DEPs requirements.

Change-Id: I1ea59ef056c0592c29ff4b1a39412c17ed1c0219
Bug: 827545
Reviewed-on: https://chromium-review.googlesource.com/995872Reviewed-by: Cait Phillips <caitkp@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548247}

There could be an ordering issue with the teardown
of a tab with an infobar after the infobar change
in r547527. Watch the "infobar manager gone" callback
and ensure a correct order.

For correctness, this makes the change in all the
other places that change used the infobar observer
except for InfoBarObserver, which is changed this
way in https://crrev.com/c/991468 .

BUG=354380, 828552

Change-Id: I21add007c5b2d725dc2985cbd268d3d4674978b6
Reviewed-on: https://chromium-review.googlesource.com/996372Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548246}

Net.HttpContentLengthWithValidOCL
Net.HttpContentLengthCacheable
Net.HttpContentLengthCacheable4Hours
Net.HttpContentLengthCacheable24Hours

Bug: 821242
Change-Id: I54d0cd8004cd837e43ecd4dea9a0b431bad5d644
Reviewed-on: https://chromium-review.googlesource.com/996247Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548245}

It is behind the flag "FormDataEvent". The flag is off by default, and
tests will be added later.

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

This reverts commit 970f8498.

Reason for revert: Appears to be causing leaks in chromeos_unittests (PipeReaderTest.Cancel).

Bot: https://ci.chromium.org/buildbot/chromium.memory/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/

Build failure: 
https://logs.chromium.org/v/?s=chromium%2Fbb%2Fchromium.memory%2FLinux_Chromium_OS_ASan_LSan_Tests__1_%2F26886%2F%2B%2Frecipes%2Fsteps%2Fchromeos_unittests%2F0%2Fstdout

Original change's description:
> Reduce leaks in PostTaskAndReplyImpl::PostTaskAndReply.
> 
> Before, there was always a leak when the RunTaskAndPostReply callback
> posted by PostTaskAndReplyImpl::PostTaskAndReply didn't run.
> 
> With this CL, the "task" is never leaked and the "reply" is only
> leaked if the execution environment is shutdown before the deletion
> happens (e.g. MessageLoop deleted, TaskScheduler shutdown).
> 
> Bug: 807013
> 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:android_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
> Change-Id: I05205d1b0250811abe61e2204ba32919d16c16c0
> Reviewed-on: https://chromium-review.googlesource.com/902191
> Reviewed-by: François Doray <fdoray@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Reviewed-by: Kenneth Russell <kbr@chromium.org>
> Reviewed-by: Gabriel Charette <gab@chromium.org>
> Commit-Queue: François Doray <fdoray@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#548034}

TBR=sky@chromium.org,gab@chromium.org,fdoray@chromium.org,kbr@chromium.org,tzik@chromium.org

Change-Id: Ib91c72333fabb4e33c1689c5ad39a5ed53ce3beb
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 807013
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:android_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Reviewed-on: https://chromium-review.googlesource.com/996732Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548243}

Start talking to the new, component-specific bridge rather than the
SnippetsBridge.

Also, make ContextualSuggestionsBridge and ContextualSuggestionsCluster
package protected to enforce ContextualSuggestionsCoordinator being
the only Java class visible outside of the package.

BUG=822945,827654

Change-Id: Ib599a1ec9f6af53046c71c8b762b64398cb306cc
Reviewed-on: https://chromium-review.googlesource.com/996404
Commit-Queue: Theresa <twellington@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548242}

The DCHECK() asserted that the status was ERROR_DETECTED whenever
GetReasonToClose() was called. However, this function is also intended
to be called when connections are closed normally.

Bug: 829083
Change-Id: Iaee6948cf38ef3ee3ddfbde8681ec9a840928662
Reviewed-on: https://chromium-review.googlesource.com/996310Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548241}

Bug: 758733
Change-Id: I0b4cac2f3bc605383e835184ef7c27c51be1be4a
Reviewed-on: https://chromium-review.googlesource.com/994144
Commit-Queue: Peter Williamson <petewil@chromium.org>
Reviewed-by: Yafei Duan <romax@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548240}

This patch adds an UMA metric for the time spent in
ScrollingCoordinator::UpdateAfterCompositingChangeIfNeeded when a
compositing-related change does need an update.

Bug: 826883
Change-Id: I49949aa286bfc2c3c265b9ba99e2b7cd5a33b90b
Reviewed-on: https://chromium-review.googlesource.com/994541Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548239}

crrev.com/c/728325 disabled fetching/using an ICC file for display color
correction if enough information was available in the monitor EDID. This
was based on the wrong assumption that either one or the other would be
present, but not both.  This CL reenables the use of (download of) the ICC
file for monitor colorimetry, using the EDID provided info as a fallback.

On the implementation:
DisplayConfigurator::NotifyDisplayStateObservers() pings DisplayColorManager
when there's new Display info. The later calls ApplyDisplayColorCalibration()
directly or after fetching the ICC file. In either case, if all steps
succeed, SetColorCorrection() is called; at this step we are sure that the
found/downloaded ICC file is good, and we can remove the usage of the EDID
provided ColorSpace.

Bug: 828102
Change-Id: Id799f8412ea06d781712884b1d02694f124860c6
Reviewed-on: https://chromium-review.googlesource.com/990494Reviewed-by: Greg Levin <glevin@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548238}

Sometime Android system fails to extract library. Manually extract them to
cache directory and load as needed.

Bug: 806998
Change-Id: I7ccff04435cb5201e410c71bde741e52687329ab
Reviewed-on: https://chromium-review.googlesource.com/930332
Commit-Queue: Ran Ji <ranj@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548237}

This is necessary in order to land CL [1].  I've been trying for a few weeks to
land it, but there's always new merge conflicts due to changed layout test
baselines.  This CL bans changes in third_party/WebKit/LayoutTests for a few
hours while I rebase and land CL [1].

[1] https://chromium-review.googlesource.com/c/chromium/src/+/976083

BUG=787020
R=dpranke

Change-Id: I24bf199e20e5d5da1fc84e1ac8e64320213527d0
Reviewed-on: https://chromium-review.googlesource.com/996633Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548236}

Adds a test that validates that the third-party libraries used by the
chrome media gallery util service are using the right CPU info.
This is going to be usefull for an upcoming CL that changes how that
information is set (it'll be passed through IPC).

Bug: 823931
Change-Id: I9e9586af8615739db0baf36ed547ef017546adb5
Reviewed-on: https://chromium-review.googlesource.com/996392Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548235}

TBR=kbr@chromium.org

No-Try: True
Change-Id: I3b6e7a4bfe81a67b0d67b334b09217fd02b2c579
Reviewed-on: https://chromium-review.googlesource.com/996638
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548234}

Bug: 826231
Change-Id: I82f681337a754513a69d002042d42e1d5206efa5
TBR: dgozman
Reviewed-on: https://chromium-review.googlesource.com/993974Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548233}

d108fd04a5e6 linux: Add PtraceConnection::ReadFileContents
08ce02c35276 Fix crashpad build on non Android ARMEL with a recent GLIBC

Change-Id: I89fe9a22bf10b1a08a322cfd856ca9b56797c899
Reviewed-on: https://chromium-review.googlesource.com/995421Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: José Dapena Paz <jose.dapena@lge.com>
Cr-Commit-Position: refs/heads/master@{#548232}

Change-Id: Ib2a034a4ee2b38ced8e1dc51247a49eee244aede
Reviewed-on: https://chromium-review.googlesource.com/991152
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Joel Einbinder <einbinder@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548231}

This is disk caching part of Feed Image Loader, and other parts of Feed
Image Loader will come later.
leveldb_proto is used as database. This disk cache need to save images
when Image Loader fetched images from network, and next time when Image
Loader received a same URL request, disk cache can provided without
downloading. Also this disk chache will do timestamp-base garbage
collection when Image Loader requested.

Bug:807359, 807457

Change-Id: I66db2411304012cf6f04a7380fc34fb1f5306d2f
Reviewed-on: https://chromium-review.googlesource.com/981298
Commit-Queue: Gang Wu <gangwu@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548230}

This is in preparation for nested dedicated workers.

Bug: 829119

Change-Id: Ifedf3a9b3d57a2e88b294280f148d25b6071a170
Reviewed-on: https://chromium-review.googlesource.com/993773
Commit-Queue: Nate Chapin <japhet@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548229}

This is for reuse by RasterDecoder in a subsequent CL. The test added
for GLES2DecoderImpl is similar to what will be added for
RasterDecoderImpl.

Changes:
- made CopyTextureMethod an enum class for easy forward decl
- moved ValidateCopyTexFormatHelper and GetCopyTextureCHROMIUMMethod for
  future reuse
- added mock for texture copying
- added unittest to make sure that texture copying clears source and
  destination textures appropriately

Bug: 789238
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;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I44a1ca37ad48d065acfd9d94b737ac1d925d99e5
Reviewed-on: https://chromium-review.googlesource.com/993592
Commit-Queue: Jonathan Backer <backer@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548228}

https://skia.googlesource.com/skia.git/+log/42f8bc40fd37..bf74a460814a

$ git log 42f8bc40f..bf74a4608 --date=short --no-merges --format='%ad %ae %s'
2018-03-22 liyuqian Fix drawBitmapRect in the threaded backend
2018-04-03 mtklein add Mac ASAN bots
2018-04-04 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ 7dd7eed65..d26d270c8 (1 commit)
2018-04-04 djsollen Tag the unique keys of lazy images.
2018-04-04 robertphillips Add SkSurfaceCharacterization operator== && !=
2018-04-04 bsalomon Revert "Revert "Make SkSL GLSL generator declare sk_FragColor inout when EXT fb fetch is used.""
2018-04-04 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 5d232d53b..bc54342bf (6 commits)
2018-04-04 egdaniel Don't use the inner radius when not stroking in DIEllipse
2018-04-04 bsalomon Revert "Make SkSL GLSL generator declare sk_FragColor inout when EXT fb fetch is used."
2018-04-03 benjaminwagner Add mips64el_toolchain_linux asset.
2018-04-03 bsalomon Make SkSL GLSL generator declare sk_FragColor inout when EXT fb fetch is used.
2018-04-04 egdaniel Handle perspective scales in GrPathUtil scaleToleranceToSrc
2018-04-03 robertphillips Hide GrPixelConfig in SkSurfaceCharacterization
2018-04-04 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ 770177dc9..7dd7eed65 (1 commit)

Created with:
  roll-dep src/third_party/skia


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;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=herb@chromium.org

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

BUG=827826

Change-Id: I6b91c4a9691f19df11f39a0799df5d5a4703681f
Reviewed-on: https://chromium-review.googlesource.com/996251Reviewed-by: James Zern <jzern@google.com>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548226}

This CL will early-out on a bad URL or there are too many requests inflight. This
avoids allocating and freeing a BitmapFetcherRequest (which is unnecessary).
This is a minor optimization for an uncommon case, but I plan to increase
the use of the bitmap fetcher - so this may become more common.

Bug: None
Change-Id: I3d498008a78faf622fcee68d20c4e9234e581e80
Reviewed-on: https://chromium-review.googlesource.com/994116
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Reviewed-by: Peter Williamson <petewil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548225}

Bug: internal b/77586397

Change-Id: I1a40b631bc3666e38008a367458737a4564f93a7
Reviewed-on: https://chromium-review.googlesource.com/994135Reviewed-by: Stephen Lanham <slan@chromium.org>
Commit-Queue: Kenneth MacKay <kmackay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548224}

Removes the was_focused_by_mouse_ flag implemented by a number of form elements,
and replaces it with a check for Node::WasFocusedByMouse().

R=tkent@chromium.org

Bug: 817199
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ibd8477732d5646f928c010a5c1cef853bafc38ee
Reviewed-on: https://chromium-review.googlesource.com/988352
Commit-Queue: Rob Dodson <robdodson@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548223}

Bug: 822951
Change-Id: If213f5703c966868778cd00511f222eba6ff5191
Reviewed-on: https://chromium-review.googlesource.com/990575
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548222}

Before playing media using the MediaPlayerBridge, we try to parse the
metadata, using the MediaResourceGetter. This class uses the Android
MediaMetadataRetriever API, which can be be resource intensive. We
eventually get all of the metadata we need from the Android
MediaPlayer, and pre-parsing the metadata sometimes does nothing but
delay the start of playback.

This CL removes the java MediaResourceGetter, and removes metadata
extraction capabilities from the C++ portion of the
MediaResourceGetter interface.

NB: This is unlikely to have a performance effect on HLS playback,
since the MediaResourceGetter did not support parsing HLS.

Bug: 739914
Change-Id: I460d5aea02bf1a0bf099f66a781a40ca6374d4d0
Reviewed-on: https://chromium-review.googlesource.com/988681Reviewed-by: Peter Wen <wnwen@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548221}

BUG=829047

Change-Id: I3ff5012311bac36cef7636030e988143f47c3339
Reviewed-on: https://chromium-review.googlesource.com/996471Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548220}

|is_posix| will be switched to false for Fuchsia, this is a preliminary change.

Bug: 812974
Change-Id: Ibfe71ea6fdd860fc83234fa31b3223339d0b71dc
Reviewed-on: https://chromium-review.googlesource.com/988847Reviewed-by: Stephen White <senorblanco@chromium.org>
Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548219}