GitLab

This adds a new browsertest which adds a hook into the feedback uploader
to catch it right before it does the actual report upload. This ensures
that clicking on the button to send a feedback report actually results
in the report getting queued to be sent. This covers a regression case
which is in crbug.com/954563.

Bug: 955039, 954563
Test: Browser tests pass, fail if prior regression was put back
Change-Id: I92762c1b6741ad057e78c8cafeb924f93995b249
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632534
Commit-Queue: Jeffrey Kardatzke <jkardatzke@google.com>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666036}

This reverts commit f3d36175.

Reason for revert: The bug thought to be caused by this change was actually caused by crbug.com/966345 and fixed in https://chromium-review.googlesource.com/c/chromium/src/+/1636226/.

Original change's description:
> Revert "webvtt: Add background opacity in mac"
> 
> This reverts commit 8e606757.
> 
> Reason for revert: Caused crbug.com/964244
> 
> Original change's description:
> > webvtt: Add background opacity in mac
> >
> > To test, open a video that has a WebVTT captions file. For example, https://www.iandevlin.com/html5test/webvtt/html5-video-webvtt-sample.html is a nice example.
> >
> > Introduce new background opacity text track property for webvtt captions and wire it to apply opacity to the WebVTT caption HTML element.
> >
> > Bug: 897730
> > Change-Id: Ic8dabc2279117b7ff12eb75a9daa8d26c9d9bb25
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592622
> > Commit-Queue: Abigail Klein <abigailbklein@google.com>
> > Auto-Submit: Abigail Klein <abigailbklein@google.com>
> > Reviewed-by: Avi Drissman <avi@chromium.org>
> > Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#659116}
> 
> Bug: 964244
> Change-Id: I76ce88cee600ed98d48426b49d1d88a40d95e507
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1622433
> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
> Auto-Submit: Abigail Klein <abigailbklein@google.com>
> Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#662163}

TBR=ellyjones@chromium.org,abigailbklein@google.com

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

Bug: 964244
Change-Id: Ib14f2e59e1b84525382b207131258a46c9a18cb4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643927Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Abigail Klein <abigailbklein@google.com>
Cr-Commit-Position: refs/heads/master@{#666035}

Tbr: boliu@chromium.org, dvadym@chromium.org, bengr@chromium.org
Bug: 908139
Change-Id: I1b816b24c1a6a4d3813ae392348eaa9974151845
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631749
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666034}

Obtaining the sign in state from the handler does not work in incognito
mode or in other cases where both Dice and Mirror are disabled. Continue
to request the Print to Google Drive destination from the cloud print
server on every load for this case, and also query the server for
printers when the sign in tab closes, instead of waiting for updates to
the cookie jar (since these do not occur in incognito mode).

This CL restores much of the code that was removed in
https://crrev.com/c/1626933 for the incognito case.

Bug: 970036
Change-Id: I7265beb11ed68c8b4d1cc4959561e63688ff8ebe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639665Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666033}

Bug: 969204
Change-Id: I0f7c3d0a4dee0c6debd09ddc6ea67587dd744cbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639639
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666032}

Switch from "Wake Lock is being released" to "Wake Lock released" to make it
less confusing. The former can sound like the lock is still being released
by the time the message can be inspected, while the latter indicates this is
an operation that has been completed and cannot be reversed.

Bug: 257511
Change-Id: I8b0d3b749d404031d2e23da4050988c733be6689
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643471
Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#666031}

Change schedule of the notification so the deadline takes place between
2am and 4am local time.

Bug: 968188
Change-Id: Ie55e9f50cf365ef384fd3c7d9faaef6a0886ab91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635252
Commit-Queue: Roman Aleksandrov <raleksandrov@google.com>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666030}

This UMA has been falling over time but there are still significant
differences in how streaming media is handled, and therefore it remains
useful to measure.

Bug: 969990
Change-Id: Ib047bd320e2d77dd2018ac03f55d8c37efe24b39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642387Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666029}

The fix for crrev.com/641485 only saved off the event for redispatch
in a single situation where it wasn't handled. This was too
conservative, and didn't address cmd+C and cmd+V.

Save off the event for redispatch whenever it is unhandled.

Bug: 964052
Change-Id: Iaa9b8d747e396aa1f0a3144c83400ae73dd44a80
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643732Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666028}

In |ShelfWidget|, override |OnNativeWidgetActivationChanged| instead of
|OnWidgetActivationChanged|. This achieves the same purpose, is more
consistent with what |StatusAreaWidget| does, and avoids the need to
add/remove widget observers.

Note that this doesn't directly fix the linked bug but is a step in the
right direction. No behavior change is expected from this change.

Bug: 956080
Change-Id: Id4002b30197a5d6a97baccaaf1a912db39c45e9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643413Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666027}

The directory layout is reworked. public/internal files now live in
public/internal subdirectories.

The root directory contains files belong to chrome and build target
used to include the internal library.

Bug: 966535
Change-Id: Ib53a3e3696b381cc989278e9c13fd015c82da053
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639359
Commit-Queue: Xing Liu <xingliu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666026}

The UMA was added to get data on how often we need to serialize ops >
512k and what the size distribution for these ops looks like. The data
from stable channels puts it at ~0.4 ops per million tiles, and even in
those cases ~85% of them fit within 600k and only 0.01% of the cases
exceeded the max limit of 16M. So it looks like this is enough of an
edge case that the current solution for reallocation on a serialization
failure is good enough.

This change removes the UMA since its no longer needed and increments the
default size we begin with to 600k so the common cases require minimum
reallocations.

R=enne@chromium.org, piman@chromium.org

Change-Id: I022ead6728c2b0a04bc898db892d3ccc4ac5d0e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641810
Commit-Queue: Khushal <khushalsagar@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666025}

Original CL description:

Implement AppLaunchManager for controlling app-under-test for EG2 tests.

No tests are added to smoke_egtest to test app relaunching, as it descends
from ChromeTestCase, which currently has logic which is required to run
every time the app-under-test is launched. Long-term, it is preferred if
this logic is moved to -setUp and executing before every test method. This
refactor will happen in a later CL as it requires some planning.

Confirmed that smoke_egtest does however only launch the app once with the
change to use AppLaunchManager.

Bug: 922813
Change-Id: I02d7e65cb47d86c35c09d049bc628c0220b4adb8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641468Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: ericale <ericale@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666024}

Change-Id: I16a94ad8e0d8ad95fa524c57b87cb2063d1c5a71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643174Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666023}

The only pangocairo flag usage at //chromium/BUILD.gn has been removed in
crrev.com/c/755996 but its import has been left behind, so this CL remove it.

No behavioral changes.

Change-Id: Ic237ed0bfd8a649cb61af1efb351e3e548e0590a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643929Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Commit-Queue: Nick Yamane <nickdiego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#666022}

This CL ensures that native theme backgrounds are applied consistently
to the Autofill dropdown. This is accomplished by listening for
OnNativeThemeChanged events.

Remaining work includes fixing text in Autofill (currently GTK theme
text colors are not respected, leading to some poor contrast
situations; see the attached bug).

Bug: 914974
Change-Id: If6d705d9bd0d1b38958650f1e26722881a7e4192
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1431533
Commit-Queue: Tommy Martino <tmartino@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Reviewed-by: Fabio Tirelo <ftirelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666021}

This CL removes StartDiscoverySession() function from TestBluetoothAdapter
in the //device/bluetooth/bluetooth_adapter_unittest.cc since the
StartDiscoverySession() is not a virtual function, and it doesn't need
to be overloaded in the TestBluetoothAdapter.

Bug: None
Change-Id: Ic1fac18ce46282083643e222495b7ba9879dd510
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643990Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Jun Cai <juncai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666020}

The existing logic does not detect and forward the URL for SVG anchor
elements. This contributed to the behavior in the linked bug, where
TalkBack (and presumably other systems that rely on Chrome's
accessibility tree) could not access the link URL of these elements.

Bug: 958553
Change-Id: I1367d6ea501cf7fa002db5e6bfd2b6f47d108531
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628232
Commit-Queue: Aran Gilman <gilmanmh@google.com>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666019}

The test verifies compilation, linking, and java dependencies. At
runtime it instantiates the test harness, and runs the BrowserTestBase
and ChromeBrowserMainParts initialization steps without crashing.

R=jam@chromium.org

Bug: 961849
Change-Id: I90adfab765d62fced8781695010eb6687693edfb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635356
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666018}

Bug: 950413
Change-Id: Id1b6d06a8d028937e080cb94d300ace35df7575b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642469Reviewed-by: Ben Pastene <bpastene@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Jon Wilson <jpwilson@google.com>
Cr-Commit-Position: refs/heads/master@{#666017}

Bug: 966671
Change-Id: Id3adf06eacabf5630edf3de31cbcf81314345f6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642156Reviewed-by: Klaus Weidner <klausw@chromium.org>
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Auto-Submit: Piotr Bialecki <bialpio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666016}

- Fix UA string not to report Fuchsia as an X11 platform.
- Switch Fuchsia away from using the generic POSIX OS & CPU info logic,
  with the result that CPU architecture is no longer reported.

Bug: 936327
Change-Id: I691253d4f83457a68fcd5d2ce5e5efdf47834381
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639741
Commit-Queue: Wez <wez@chromium.org>
Auto-Submit: Wez <wez@chromium.org>
Reviewed-by: Thiemo Nagel <tnagel@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666015}

Bug: 967011,961808
Change-Id: Ic214bd469cebe29fc4aad785342cd57930e03d54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637860Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: benjamin joyce <bjoyce@google.com>
Cr-Commit-Position: refs/heads/master@{#666014}

Test that when an AudioBufferSourceNode stops, the number of channels
of its output changes (eventually) to 1 as required when a node is not
actively processing anymore.

Chrome already supports this notion (via |DisableOutputs()|), so we're
just adding a test for this.

Bug: 954545
Test: the-audiobuffersourcenode-interface/active-processing.https.html
Change-Id: I4fab646df204720cc1efe2e3ae325e60cb22e49b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643729
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666013}

This was meant to be disabled before the branch point but we missed it,
so disabling on top of tree to ask for a merge request for M76.

BUG=chromium:955699
BUG=chromium:852089
TBR=kbr@chromium.org

Change-Id: I055e07b421b38a6ea24d753e5d0b53881f93a2c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643510Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666012}

Bug: 875053
Change-Id: I0c1a493ec7dc8b45135748e8f314c121e962b0ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640792
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Nick Harper <nharper@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666011}

Bug: 966791
Change-Id: Ie81093bcf58e363855b72c57c81b9efce8cdeec6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643967Reviewed-by: Kristi Park <kristipark@chromium.org>
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666010}

 - Add minify_polymer.py script that uses rollup and uglify to
   bundle and minify Polymer3.
 - rollup will only be installed locally by whoever is rolling a new version
   of Polymer, and does not need to be checked-in to Chromium's toolchain for
   now.
 - Update reproduce.sh to call minify_polymer.py, and to update the paths
   of all iron-* and paper-* dependencies to point to the bundle file.
 - Update demo page accordingly.

Bug: 965770
Test: chrome://print/polymer3/demo.html should still work
Change-Id: Ia71c4779a7b2559affb3617c9c81c35e224555df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636274Reviewed-by: Dan Beam <dbeam@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666009}

The coverage was non-zero for CRLSet::Parse, but it appears the
fuzzers never managed to get the bottom of the function. As such,
ReadCRL had no coverage.

This CL improves the coverage by creating a new fuzzer specifically
for CRLSet::Parse with a seed corpus. I just grabbed files from
net/data/ssl/certificates/ that contained "crl" in their name -- this
was enough to get the fuzzer to venture into ReadCRL.

Change-Id: I67618a448b23c36313ea7c8df09536529522075c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643908Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Dan McArdle <dmcardle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666008}

This reverts commit 58fe1e69.

Reason for revert: This looks like it breaks an ios internal trybot https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/ios-internal-chromium-tot

Original change's description:
> Delete GaiaCookieManagerServiceObserver in favor of callbacks.
> 
> This CL replaces GaiaCookieManagerServiceObserver with vanilla
> callbacks. Now that GCMS is owned by IdentityManager, and cannot have
> multiple observers, a callback interface seems more natural than an
> Observer class.
> 
> This also has the nice side effect of removing transitive includes of
> gaia_cookie_manager_service.h via identity_manager.h.
> 
> Change-Id: I9cdac56c8237c9a09eb2c2ce87f41f48872a9fb6
> Bug: 939372
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1630162
> Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
> Reviewed-by: Colin Blundell <blundell@chromium.org>
> Commit-Queue: Lowell Manners <lowell@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#665616}

TBR=blundell@chromium.org,msarda@chromium.org,lowell@chromium.org

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

Bug: 939372
Change-Id: I777df13eb9bc5eddeea46640b973c287d6622061
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642232Reviewed-by: Lowell Manners <lowell@chromium.org>
Commit-Queue: Lowell Manners <lowell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666007}

The test was disabled waiting for https://crrev.com/c/1617498
to land.

Bug: 927949
Change-Id: Ie1d555d21eb21d04b4b859ff007767d8bb77847b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643529
Auto-Submit: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666006}

Does not actually implement scrolling, and the UI is hidden behind
--enable-experimental-accessibility-autoclick.

Bug: 947068
Change-Id: I9e66dcbe589c09f6819b2822c179240e48c0cd0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639362
Commit-Queue: Katie Dektar <katie@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Anastasia Helfinstein <anastasi@google.com>
Cr-Commit-Position: refs/heads/master@{#666005}

These three colors are never set to non-default values, so hard-code
them in the only place where they're used (NativeThemeBase).

Bug: none
Change-Id: I0c3d8ee2efd0f5fd428917341dadc54c1a3f958d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642271Reviewed-by: Leonard Grey <lgrey@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666004}

Tablets don't have an overview mode when an accessibility service is not
enabled. Restrict the test to phones only.

BUG=970184

Change-Id: If1d7f160203a1abc96f9cb837098f11b58d17ec5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643105Reviewed-by: Becky Zhou <huayinz@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666003}

A previous approach to splitting native code into DFMs benefited from
having a different libmonchrome.so for bundles. The latest approach
doesn't need a separate library, because the impact of splitting on the
main lib is negligible. Therefore, return to using the same lib for both
bundles and APKs.

The first step is flipping the switch off in this CL, and removing some
related code.  Then, conditionals can be safely removed downstream, and
finally, the flags and any remaining cruft can be purged from the public
config.

TBR: agrieve@chromium.org
Bug: 962477
Change-Id: If5582f49894b053daf307b42df04406815133370
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641387
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666002}

https://swiftshader.googlesource.com/SwiftShader.git/+log/75841d73c2de..5b424e69101a


git log 75841d73c2de..5b424e69101a --date=short --no-merges --format='%ad %ae %s'
2019-06-04 sugoi@google.com Revert Chromium vulkan unit test build for now
2019-06-04 sugoi@google.com Build fix for MacOS and Fuchsia
2019-06-03 sugoi@google.com Add vulkan unit tests to Chromium


Created with:
  gclient setdep -r src/third_party/swiftshader@5b424e69101a

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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=swiftshader-team+autoroll@google.com

Change-Id: I6bbbad70e874f8cdb12bb6cf8da54c6989be78aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643316Reviewed-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@{#666001}

This CL adds the metadata fields for tracing.

BUG=925151

Change-Id: I35d4e81c093dfd84574907221007c6dabb10189d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639321Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: ssid <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#666000}

AVDA has been deprecated for many releases and has been fully replaced
by MediaCodecVideoDecoder.

Bug: 970062, 789435
Change-Id: I76f32185f7e8a28153e87c38485ba83e29386850
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641641Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#665999}

Child throttling and BeginFrame throttling really have the same
purpose, which is to prevent the client from sending further frames
when there are frames that aren't drawn yet. I don't think there is a
need for two different mechanisms to achieve this. Make BeginFrame
throttling work across multiple surfaces (it currently only supports
one), and remove child throttling.

Bug: 938947
Change-Id: Id2765030eb52f4a8923535d86397cccbe70e829d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637526Reviewed-by: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#665998}

The pref name referenced in the settings page did not match the setting
created in ash/pref_names.cc.

Bug: None
Change-Id: I6a83ee7aa7d454276d9fd71e0a721afb86aa717e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642961Reviewed-by: Dan Beam <dbeam@chromium.org>
Commit-Queue: Anastasia Helfinstein <anastasi@google.com>
Cr-Commit-Position: refs/heads/master@{#665997}