GitLab

On Android Q, queryIntentActivities(.. , MATCH_ALL) doesn't return
Chrome even if Chrome is installed. Passing MATCH_DEFAULT_ONLY
instead will fix this issue.

Bug: 851725
Change-Id: Id851ec9fcbea47df5a522a23355ad2b67401544f
Reviewed-on: https://chromium-review.googlesource.com/1222675
Commit-Queue: Xi Han <hanxi@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591133}

Change-Id: Ic77f1075eda7299e5cce686dd11740081c3436ac
Reviewed-on: https://chromium-review.googlesource.com/1223026
Commit-Queue: Xi Cheng <chengx@chromium.org>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591132}

Currently, the extension action, media router action and the toolbar action bar,
all call into their delegates to close the overflow menu. Consolidate this code
so that the extension action and media router action use
ToolbarActionBar::CloseOverflowMenuIfOpen.

BUG=None

Change-Id: I4c6933901a3e3e2ba52ad0c4b0cb48efb6cd5172
Reviewed-on: https://chromium-review.googlesource.com/1222685Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591131}

This reverts commit e41ffb6c.

Reason for revert: WebAudio can still do recursive acquisition due to finalizing objects during an allocation in which the lock is held. See crbug.com/882314

Original change's description:
> WTF: CHECK if a mutex is recursively acquired.
> 
> This is a final attempt to flush out any recursive acquisition
> before support is totally removed for WTF::RecursiveMutex.
> 
> For pthreads, this requires maintaining the recursion_count_
> variable even in non-DCHECK builds. This is still quite cheap,
> and is temporary in any case.
> 
> Bug: 856641
> Change-Id: I2b550fd58e8c4cf6293ad7628dd49aa366b41ae9
> Reviewed-on: https://chromium-review.googlesource.com/1212453
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Commit-Queue: Jeremy Roman <jbroman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#589504}

TBR=jbroman@chromium.org,yutak@chromium.org,haraken@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 856641,882314
Change-Id: I1e2732ee0c810d5fed73ba29874088abaeed2d59
Reviewed-on: https://chromium-review.googlesource.com/1225297Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591130}

Bug: b/110900868
Test: manual

Change-Id: I2cdc3c62af8d78828bcf6d39e0deeac8c53a825a
Reviewed-on: https://chromium-review.googlesource.com/1215059
Commit-Queue: Mina Almasry <almasrymina@chromium.org>
Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Reviewed-by: Sergey Volk <servolk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591129}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll

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=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: I78deba6abf6e0afc6da54ba24ce16133e78031f2
Reviewed-on: https://chromium-review.googlesource.com/1225298Reviewed-by: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#591128}

...and enable the full-range-video test on mac.
This will only affect software decoded video frames as
hardware-decoded video frames seem to be converted to studio
range on mac.

Bug: 647838, 810908, 882627
Change-Id: I318d1480dff4f33fa4da4312bead4b6d09f1a810
Reviewed-on: https://chromium-review.googlesource.com/1164462Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: Fredrik Hubinette <hubbe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591127}

Fixes the page by adding the iOS WebUI messaging script to the html.

Also modifies the JavaScript to update page content after HTML has been
completely loaded, for more robustness.

Bug: 883408
Change-Id: I43d1be5077af6d42e357bfb3a5bbcb28eb5c0d60
Reviewed-on: https://chromium-review.googlesource.com/1225300Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Moe Ahmadi <mahmadi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591126}

This patches fixes a pointer offset issues, which usually happens
with Ozone/Wayland (and can happen with Ozone/X11).

That is, on certain occasions, the pointer bitmap can have an offset,
which results in wrong visual location of the pointer. This makes
it hard to press ui elements in Chromium.

The reason of that behaviour is that default scale value of the
Cursor is 0.0f (when it is not explicitly set to something
else), but the SearchTable (cursors_aura) method checks for the
bitmap hotpoints based on the lowest possible scale value, which
is 1.0f. Thus, there was an inconsitancy between the scale value
and the hotpoints. When the cursor had a scale value implicitly
set to 0.0f (in the ctor), 2x hotpoints were used.

To fix this, CreateDefaultBitmapCursor must honor the scale factor,
and set it the lowest possible one, which is 1.0f.

Bug: 869286
Change-Id: Ia792ae26a7573b58fa4dca7356c49cd4b5d8042a
Reviewed-on: https://chromium-review.googlesource.com/1203973Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#591125}

Currently resources that are modified between timing updates are held
as a set of pointers to PageResourceDataUse objects. However, these
are stored in a small map, which invalidates iterators/pointers on
insertion, causing undefined behavior when using |modified_resources_|.
Instead, store PageResourceDataUse as unique pointers and have
|modified_resources_| reference the raw pointer.

Change-Id: Id7d75343887f9be9b9ee405b5fabc29e635d93e8
Reviewed-on: https://chromium-review.googlesource.com/1224656Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Commit-Queue: John Delaney <johnidel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591124}

The UMA recorded when strong binding process OOMs to find if there were
other processes alive, included current process bindings if it was not
unbound. So, subract the current process binding from the counts.

BUG=882741

Change-Id: I3a5774fdacf20cc94b655434c50ce0626c94fb0e
Reviewed-on: https://chromium-review.googlesource.com/1225093
Commit-Queue: Siddhartha S <ssid@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591123}

This patch is the next in a sequence of patches to add node isolation
for paint property trees. This patch adds effect node aliasing.

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I0ae2d8d35e98b8938be6207248f61eecdabf7b92
Reviewed-on: https://chromium-review.googlesource.com/1217512Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591122}

This CL makes WebappActivity/WebApkActivity not exported.
WebappActivity/WebApkActivity became exported by mistake as a result of
https://codereview.chromium.org/2941173002

BUG=882763

Change-Id: I01cd3006e3aa7e87d5c1f088859b08fda456e893
Reviewed-on: https://chromium-review.googlesource.com/1223327Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591121}

Placed the code for calculating the fieldset border offset and cutout
rectangle for the legend in a separate file, to make it shareable with
LayoutNG (when fieldset eventually gets implemented there).

The test that's supposed to test this fails on Mac, due to sub-pixel
issues. The ref uses a table, and tables don't do sub-pixel layout.
The test (using fieldset-vertical.css) could have used
inline-size:fit-content instead of display:table to avoid this issue,
but it does use display:table, because "fit-content" isn't a supported
value in Gecko.

Bug: 476234
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I2b6faaecb1dbb609d0525881a1d164f7831e8759
Reviewed-on: https://chromium-review.googlesource.com/1222826
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591120}

https://skia.googlesource.com/skia.git/+log/d2916264aae0..bc6b9cb6ac40


git log d2916264aae0..bc6b9cb6ac40 --date=short --no-merges --format='%ad %ae %s'
2018-09-13 brianosman@google.com Cleanup mip-mapped proxy creation slightly
2018-09-13 brianosman@google.com Revert "Defer mip-mapping until lazy proxy instantiation"
2018-09-13 michaelludwig@google.com Implement radial gradient layout
2018-09-13 caryclark@skia.org Condense embedded formulas.
2018-09-13 caryclark@skia.org fix 100 column violators in generated includes
2018-09-13 mtklein@google.com encode F16/F32 .pngs as Rec2020
2018-09-13 herb@google.com Change fallback for path glyphs to bulk api
2018-09-13 reed@google.com Reland "remove SK_SUPPORT_LEGACY_TYPEFACE_MAKEFROMSTREAM"
2018-09-13 herb@google.com Centralize the max glyph dimension
2018-09-13 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 44286dc870e3..daab00149ee5 (1 commits)


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

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

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

Change-Id: I0f6353a4f6bae7551271f31ee9a51a0896171bd3
Reviewed-on: https://chromium-review.googlesource.com/1224913Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#591119}

Refactors and cleans-up the code related to the GLHelperScalar shader
programs and adds it to GLScaler. Also, unit testing of the shader
programs was non-existent (only higher-level integration testing was
being done), so much of this CL is about adding testing for each of
them to confirm correct behaviors.

Bug: 870036
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I7714b7cf6ebef2cd2778ba146728e6d225b1467a
Reviewed-on: https://chromium-review.googlesource.com/1214662
Commit-Queue: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Xiangjun Zhang <xjz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591118}

Also includes the update of the service proto and a refactoring of the
actions to update and access processed action protos from Action class.

Bug: 806868
Change-Id: Ia1da3f3dfb625d2687bba407080260ecbbd84d1d
Reviewed-on: https://chromium-review.googlesource.com/1219636
Commit-Queue: Andre Elisseeff <elisseeff@google.com>
Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591117}

Also: Removed the luci-check comments, since it's no longer used.

Bug: 868202
Change-Id: If971e2c2a9ed5b445ccd7eaa9f34e57be1f75191
Reviewed-on: https://chromium-review.googlesource.com/1224798Reviewed-by: Jao-ke Chin-Lee <jchinlee@chromium.org>
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591116}

This CL removes and converts the last remaining BrowserPlugin-based test
to chrome_mime_handler_view_browsertest.cc (the new test uses a
MimeHandlerViewGuest).

Bug: 553069, 330264
Change-Id: I487fbd47ca0c989e746d087c72fe396f9e9ac867
Reviewed-on: https://chromium-review.googlesource.com/1221693Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591115}

No change to logic.

This cleans up references to PlatformServiceBridgeGoogle. This class was
removed ~6 months ago, these references should have been cleaned up back
then.

R=boliu@chromium.org

Test: N/A
Change-Id: I13acfd16301f06bd027248611b7859683dc03abf
Reviewed-on: https://chromium-review.googlesource.com/1223147Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591114}

https://pdfium.googlesource.com/pdfium.git/+log/882ed81dec7a..5700d9e2eea5


git log 882ed81dec7a..5700d9e2eea5 --date=short --no-merges --format='%ad %ae %s'
2018-09-13 tsepez@chromium.org Revert "Make things more const-y"
2018-09-13 tsepez@chromium.org Test that FX_TryRealloc failure leaves original contents intact


Created with:
  gclient setdep -r src/third_party/pdfium@5700d9e2eea5

The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll

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.



BUG=chromium:881678
TBR=dsinclair@chromium.org

Change-Id: I14dd5dc9ed13c9fcf8c7c469116521e77679b5d2
Reviewed-on: https://chromium-review.googlesource.com/1224482Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#591113}

Android throttles the number of notification updates from an app.
As a result If important notifications are throttled, the progress
notificaiton will get stuck forever. This could happen when there
are lots of ongoing downloads. This CL throttles download notification
updates before sending them to Android Notification Manager to solve
the problem

BUG=876206

Change-Id: Ic462a51050a2a04e5182991a9446369808ea3bb7
Reviewed-on: https://chromium-review.googlesource.com/1222692
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591112}

https://chromium.googlesource.com/angle/angle.git/+log/16e28fd3f2cd..f4d429c1cbc1


git log 16e28fd3f2cd..f4d429c1cbc1 --date=short --no-merges --format='%ad %ae %s'
2018-09-13 jmadill@chromium.org Fix EGL enum allocation.
2018-09-13 jmadill@chromium.org Vulkan: Update LineLoopTest expectations.


Created with:
  gclient setdep -r src/third_party/angle@f4d429c1cbc1

The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll

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

Change-Id: I2167456e78070a019e70ce47f42398db1cfb9d03
Reviewed-on: https://chromium-review.googlesource.com/1224604Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#591111}

Bug: 875452
Change-Id: Ia64b2bebd1a56a7a6b3a4753d2b3f967b5316c52
Reviewed-on: https://chromium-review.googlesource.com/1222696
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591110}

Change-Id: I4c6c2a338caeca37fb407ec292f4b8eaeb3b744f
Bug: 773928
Reviewed-on: https://chromium-review.googlesource.com/1152042
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Scott Chen <scottchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591109}

Bug: 876368
Change-Id: I93b0348e23e5396d5c1c4a5a05e2b4c7c0ca5977
Reviewed-on: https://chromium-review.googlesource.com/1181779Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Mike Klein <mtklein@chromium.org>
Commit-Queue: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591108}

BUG=none

Change-Id: I3b5e3ca3fd09cf0e9e66667cd994f916c6db1746
Reviewed-on: https://chromium-review.googlesource.com/1188611Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591107}

Just adding a flag to put some experiments related to keyword mode
under.

Bug: 883901
Change-Id: If101d7c7dfeb8910b7e7a0a81eaff075a26fe9af
Reviewed-on: https://chromium-review.googlesource.com/1224602
Commit-Queue: Kevin Bailey <krb@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591106}

Merge all the "TooManyTabs" features in the same experiment group, which
is apparently the way to go if we want to run several Finch experiments
that enable a different set of features.

e.g. we have the following config:
- On Beta: SiteCharacteristicsDatabase and ProactiveTabDiscarding are
  enabled simultaneously, PageAlmostIdle is enabled separately.
- On Stable: We only enable SiteCharacteristicsDatabase and
  PageAlmostIdle (simultaneously).

Change-Id: I0da8cace675e700dfd6662e095e7bf8aa84f7f6e
Reviewed-on: https://chromium-review.googlesource.com/1217782Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591105}

The import https://crrev.com/c/1224230 created some suboptimal
(unnecessary) platform-specific baselines because the Mac10.13 job timed
out. They can be safely merged together into the generic baseline.

TBR=bashi

Bug: 883695
Change-Id: I9cd1e63eadaa1e7b963fa83c9702cbdac870996e
Reviewed-on: https://chromium-review.googlesource.com/1224714Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591104}

Bug: 878122
Test: Run DemoSetupFRETest and manually.
Change-Id: Ic171d8f1f9609f62ae443dd69d2697f730f3cd75
Reviewed-on: https://chromium-review.googlesource.com/1198362
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Igor <igorcov@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591103}

Initiated after discussion on cxx and with danakj@

Specifically: https://google.github.io/styleguide/cppguide.html#Casting

"Use brace initialization to convert arithmetic types (e.g. int64{x}).
 This is the safest approach because code will not compile if conversion
 can result in information loss. The syntax is also concise."

(This exact guidance is mirrored in our internal style guide as well.)

Change-Id: I04f825cc84aa6e34517cb533d25053bec345297e
Reviewed-on: https://chromium-review.googlesource.com/1223332Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Dana Fried <dfried@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591102}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/02581c24f71d..86a4158a03f9


Created with:
  gclient setdep -r src-internal@86a4158a03f9

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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.



BUG=chromium:863033,chromium:790074,chromium:790091
TBR=mmoss@chromium.org

Change-Id: Ice3f9d55d186ef05df176773349bb88aa9590bc9
Reviewed-on: https://chromium-review.googlesource.com/1224479Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#591101}

This CL implements Largest Text Paint and Last Text Paint.

Largest Text Paint timing measures how long to paint the largest text
element within viewport from navigation start, intending to proxy
main visible content delivery speed.

Last Text Paint timing measures how long to paint the last text within
viewport from navigation start, intending to proxy all visible
contents' delivery speed.

Bug: 869924
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I8b36fc1ec2e75998e00f6140446b326047c72140
Reviewed-on: https://chromium-review.googlesource.com/1158853
Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591100}

Bug: 881500
Change-Id: Ib362f0563b12aa8b5d299840a965ea5e0c8f003c
Reviewed-on: https://chromium-review.googlesource.com/1222194
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591099}

Histogram description stated that the metric was recorded
per click of a search result. However, the metric is
recorded upon the opening of a search result
regardless of whether or not it was clicked.

Bug: 883131
Change-Id: Ia29dfeab3b943317e7f49b084a352a3ebe182843
Reviewed-on: https://chromium-review.googlesource.com/1219940
Commit-Queue: Daniel Zhang <oxyflush@google.com>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591098}

This is a reland of 370c8bc2

This is similar to the original change, except in two significant ways:
1. RasterImplementation now supports COMMANDS_ISSUED queries, and
2. The decision whether to use queries is handled in a single place by
   OneCopyRasterBufferProvider, and communicated to StagingBufferPool by
   setting |query_id| on the StagingBuffer.

Original change's description:
> Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers
>
> GL_COMMANDS_ISSUED_CHROMIUM is sufficient for shared memory
> GpuMemoryBuffers because they're uploaded using glTexImage2D (see
> GLImageMemory::CopyTexImage).
>
> This should reduce the number of idle wakeups in the GPU process, and
> reduce the CPU time spent on such queries which is quite high on
> Windows.
>
> Bug: 830084, 622491
> Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
> Change-Id: I8111b3d7f12abbf900383d45e2a74394848e83fd
> Reviewed-on: https://chromium-review.googlesource.com/1189126
> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
> Reviewed-by: Eric Karl <ericrk@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#587695}

Bug: 830084, 622491
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;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ia8bec687f42fef8242689fb014c1d18d2194b1e3
Reviewed-on: https://chromium-review.googlesource.com/1205990
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Jonathan Backer <backer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591097}

The current code was fragile, relying on only approximate answers
about whether a canvas was accelerated or not.

Refactor the upload paths for canvases and ImageBitmaps to properly
make the decision about whether to take the GPU or CPU based upload
path based on whether the resource they receive (usually an Image) is
texture-backed. Replace TexImageCanvasByGPU and TexImageBitmapByGPU
with a single TexImageViaGPU.

More refactorings are possible, and will be built on this. This CL is
being kept self-contained for backport to earlier releases.

Tested with new conformance test in
https://github.com/KhronosGroup/WebGL/pull/2706 .

Bug: 878545
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: I8a2653ef9f4a0cc6a36ba381941f5c30c94a57d8
Reviewed-on: https://chromium-review.googlesource.com/1217856
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591096}

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

Needed for audio service debug recording feature, that writes stream data to local
files for debug purposes. Debug recording files are created in browser process, and
file descriptors are passed to audio service process through mojo IPC.

Bug: 883687
Change-Id: I0d932fa149a224f6ae1045c93f980c8479a7d28e
Reviewed-on: https://chromium-review.googlesource.com/1224532Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#591094}