GitLab

Now that ChromeFeaturesServiceProvider lives in
//chrome/browser/chromeos/dbus, it no longer needs a
Delegate interface.

Bug: 843392
Change-Id: Ia4b4a737e8cde0b517f6975994238dc8f03fec1a
Reviewed-on: https://chromium-review.googlesource.com/1184168Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Dan Erat <derat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584936}

These are histograms that have not been viewed in the last 6 months, but still
report data on the Stable channel. Set these histograms to stop being recorded
for Chrome releases after 2018-08-30. We will file bugs via Monorail (crbug)
reminding owners about the approaching histogram expiry – initially 30 days
prior to expiry, and also with follow-up alerts. The metrics dashboards will
also display a warning for anyone viewing a soon-to-expire histogram.

Owners and/or users of these histograms: Please comment on this CL if you think
that any affected histogram should not have an expiry date set! This should be
uncommon.

Otherwise, there are a few options going forward:
  * If the histogram is no longer needed, please send a follow-up CL to delete
    the recording code and to mark the histogram as <obsolete>. (You can also
    remove the expiry date in the same CL.)
  * If you want to set a different expiry date, please send a follow-up CL to do
    so.
  * If neither of the above apply, then keep an eye out for Monorail bugs as the
    histogram expiry date approaches.
For more info on how unused histograms are identified, see
https://goto.google.com/uma-unused-histograms-cleanup

Bug: 850539
Change-Id: Idac6a13a32465359102228499e05238da53a5e97
Reviewed-on: https://chromium-review.googlesource.com/1111468
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584935}

BUG=845393

Change-Id: I5c2f1cb68810596ade3c780658fddfcde2d9578b
Reviewed-on: https://chromium-review.googlesource.com/1182915Reviewed-by: Sam McNally <sammc@chromium.org>
Commit-Queue: Anand Mistry <amistry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584934}

Bug: 876449
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ib42fb716d79f95370f060af0a43fca7cb3288900
Reviewed-on: https://chromium-review.googlesource.com/1184141Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584933}

It contains 'tail' in addition to the contents of gnuwin-7, to be able
to run some tests that were updated in r339475.

NOTRY=true

Bug: 876139
Change-Id: I447d79591b01de309b258a54a37cb5603599201b
Reviewed-on: https://chromium-review.googlesource.com/1183909
Commit-Queue: Hans Wennborg <hans@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584932}

Now that VmApplicationsServiceProvider lives in
//chrome/browser/chromeos/dbus, it no longer needs a
Delegate interface.

Bug: 843392
Change-Id: I1c9a0cf0a251d12bf3a0c33a58b0d6e177859618
Reviewed-on: https://chromium-review.googlesource.com/1184142Reviewed-by: Timothy Loh <timloh@chromium.org>
Commit-Queue: Dan Erat <derat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584931}

This CL splits CreateOobeUIDataSource into several smaller functions.

Bug: 864686
Change-Id: I6843595bf66a9584778fa5ebbff8167a0ce605d2
Reviewed-on: https://chromium-review.googlesource.com/1182608
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584930}

This reverts commit d184f073.

Reason for revert: Speculative revert to fix net_unittests

BUG: 876563

Original change's description:
> Add NetLog events for cookie blocking by NetworkDelegate
> 
> Cookies setting and getting can be blocked by a NetworkDelegate.
> This CL adds NetLog events so they can aid in the investigation of cookies bugs.
> 
> Bug: 875849
> Change-Id: Ia2a09b443fb1ebfe8ce9dde1617920264f6f24a7
> Reviewed-on: https://chromium-review.googlesource.com/1181244
> Reviewed-by: Matt Menke <mmenke@chromium.org>
> Commit-Queue: Helen Li <xunjieli@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#584809}

TBR=mmenke@chromium.org,xunjieli@chromium.org

Change-Id: Ifbfcf98ec819cda47cb04e4c87e6274db0e93579
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 875849
Reviewed-on: https://chromium-review.googlesource.com/1184274Reviewed-by: Sky Malice <skym@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584929}

BUG=876451
R=pkasting

Change-Id: I2be8079b64ef0f05fbb740dc99562f44a1734fab
Reviewed-on: https://chromium-review.googlesource.com/1184045
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584928}

Bug: 172187
Change-Id: I0e42fe87ed76a44bff4c2a34065255e9440870a2
Reviewed-on: https://chromium-review.googlesource.com/1180822Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584927}

(Webauthn will need to parse an extension out of the token attestation
certificate.)

Change-Id: I24c3bc63bd190e6bfc4faeb02b8acf7fd0883b74
Reviewed-on: https://chromium-review.googlesource.com/1179231Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584926}

This reverts commit 1ffe88a7.

Reason for revert: Causing ChromeDriver waterfall issues

Original change's description:
> [ChromeDriver] Add replay end-to-end tests to run_all_tests.py
> 
> This change adds the end-to-end tests for the client replay component
> of ChromeDriver to the ChromeDriver waterfall by incorporating them
> into the existing run_all_tests.py. This will extend the waterfall
> coverage to include the ChromeDriver log-replay component.
> 
> Bug: chromedriver:2501
> Change-Id: I6e35675d2598a2a33c67340e0ee73e05201c3439
> Reviewed-on: https://chromium-review.googlesource.com/1174894
> Commit-Queue: Cole Winstanley <cwinstanley@google.com>
> Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
> Reviewed-by: John Chen <johnchen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#584518}

TBR=crouleau@chromium.org,johnchen@chromium.org,cwinstanley@google.com

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

Bug: chromedriver:2501
Change-Id: I6f0eec4d77b0608a38b9ccc4efcacd1b948c8c46
Reviewed-on: https://chromium-review.googlesource.com/1183827Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Cole Winstanley <cwinstanley@google.com>
Cr-Commit-Position: refs/heads/master@{#584925}

Bug: internal b/112773799
Test: cast_bluetooth_unittests
Change-Id: I988345b574ddbc9ba8f7afc821aac90f56779985
Reviewed-on: https://chromium-review.googlesource.com/1182301Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Bailey Forrest <bcf@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584924}

Bug: 722496
Change-Id: I797582085ebaf0c3f63b0eb4ec60d605342c5129
Reviewed-on: https://chromium-review.googlesource.com/1183584Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584923}

Per change in product spec, we should no longer anchor to the top of
the screen when in tablet mode. We should always anchor to the bottom.

Bug: b:112849003
Change-Id: If2ec374fc4ea26377edb2251be5ae445db736c80
Reviewed-on: https://chromium-review.googlesource.com/1182442
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584922}

R=tandrii

No-Try: True
Bug: 872448
Change-Id: Ia12df35141be3e9073167f24bd70fdf02568c66e
Reviewed-on: https://chromium-review.googlesource.com/1184249
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584921}

Without this CL, video streaming from chrome:// does not work. Now it
will work for URLs that use the WebUIDataSourceImpl source.

This also extends URLDataSource class in general, so other source
subclasses may report content size if they wish.

<video> only supports unknown length content with http/https. For these
other sources, the resources are assumed to be fully buffered.

Bug: 866703
Change-Id: I826b2fa1a732c6f99f37b5df3603658a5b5b8165
Reviewed-on: https://chromium-review.googlesource.com/1173497
Commit-Queue: Tommy Li <tommycli@chromium.org>
Reviewed-by: Rachel Blum <groby@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584920}

- Initially ExoShellSurface has both focus and active state. But when
  user clicks something on Android window, ExoSurface becomes focused.
  We need to use ExoShellSurface to get the widget. This CL changes it
  to use active window instead of focused one.

  click maximize button. Confirm that Chrome doesn't crash.

Bug: 867199
Test: Enable S2S and open Play Store app. Focus on the search box and
Change-Id: I74e363e2ee91986966a97a12f7cdb5399721f6cf
Reviewed-on: https://chromium-review.googlesource.com/1183046Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Yuki Awano <yawano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584919}

Bug: b:110107505
Change-Id: Ie642268b7bab2abd867bae2d5e1ad85b29459aa2
Reviewed-on: https://chromium-review.googlesource.com/1182667Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Li Lin <llin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584918}

Currently DisplayScheduler reports damage to SurfaceManager in any case
where a damaged surface ID damages the display. While these cases will
trigger a draw when visible, they don't necessarily trigger a draw
in any defined timeframe. This can lead to issues. Consider:

1) Display 1 is not visible, embeds surface A.
2) Surface A sends CF 1, we don't immediately ack as we will wait for
   Display 1 to draw.
3) Display 2 becomes visible, embeds surface A with a new surface ID.
4) Display 2 will never update, as no new frames will be produced for
   surface A as the renderer is continually waiting on the ack for
   CF 1.

By having DisplayScheduler report no damage if invisible, we always
ack frames in a timely manner. This may allow a renderer to produce
some extra frames when its display is invisible, but this should be
limited as the renderer itself receives visibility notifications and
won't get additional BeginFrames once visibility is fully processed.

Bug: 875895
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I272de950d8e4d4c819c445dc8162ac360afb80a1
Reviewed-on: https://chromium-review.googlesource.com/1182862Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584917}

This involved:
- Limiting conversation starter count to 3.
- Shuffling and selecting conversation starters to reach 3.
- Refreshing conversation starter cache for new UI sessions.
- Center aligning conversation starters (but keeping suggestion chips
  for interaction responses start aligned).

Bug: b:111694337
Change-Id: I1b5b94fabcd0a37ce3a3400a670db4224fc6a667
Reviewed-on: https://chromium-review.googlesource.com/1182863
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584916}

  external/wpt/web-animations/interfaces/Animatable/animate.html
  http/tests/worklet/webexposed/
    global-interface-listing-paint-worklet.html

These are the remaining test failures seen on this bot when running
with --use-gpu-in-tests. Unfortunately there doesn't seem to be a way
to specialize these for this device.

Bug: 875172
Change-Id: I050b131b2702987f2e5803ac6e75ea6dfae35b2b
Reviewed-on: https://chromium-review.googlesource.com/1183979Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584915}

Observed flaky after starting testing on the passthrough command
decoder on this configuration.

Tbr: geofflang@chromium.org
Bug: 872302
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: I44700af5fa229f10037435c226f870e306736730
No-Try: True
Reviewed-on: https://chromium-review.googlesource.com/1184178Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584914}

A new people_page/lock_screen_password_prompt_dialog is created
that implements lock screen specific logic that previously
resided in password_prompt_dialog.

Bug: 870122
Change-Id: If1fb68e6b7fd84f91850a169342ab04fb8a75404
Reviewed-on: https://chromium-review.googlesource.com/1179377
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584913}

We need to distinguish between MultiProcessMash, SingleProcessMash and
both (aka IsUsingWindowService).

* Power - ML and settings UI
* Exo
* WebRTC desktop capture
* Tabs extension API
* Tab dragging
* TestBrowserDialog

The remaining ones are in browser frame code.

Bug: 874468
Change-Id: Iac58a63b518966e781a25a090b58a24b8d2ace95
Reviewed-on: https://chromium-review.googlesource.com/1183790Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584912}

This reverts commit e06da142.

Reason for revert: Was not the root cause of test failures.

Original change's description:
> Revert "Fix background painting on scrolling contents layer with foregrounds"
> 
> This reverts commit 7834ee21.
> 
> Reason for revert: Suspected as causing failing tests in 874162
> 
> Original change's description:
> > Fix background painting on scrolling contents layer with foregrounds
> > 
> > This patch removes a negative z-index children check from
> > PaintLayer::GetBackgroundPaintLocation. This lets backgrounds paint in
> > the scrolling contents layer in the presence of negative z-index
> > children, fixing the painting of background-attachment: local. This
> > patch also removes a DCHECK that was hit when a foreground layer and
> > kBackgroundPaintInScrollingContents coexisted. This DCHECK[1] could be
> > hit for root layers without the functional change in this patch. As the
> > test in this patch shows, kBackgroundPaintInScrollingContents and
> > foreground layers work together, so this patch makes non-root-layers use
> > both, and removes the DCHECK.
> > 
> > What are foreground layers? A foreground layer is created if a stacked
> > PaintLayer has composited negative z-index children that should wedge
> > between the layer's background and the layer's contents. The foreground
> > layer will have the normal-flow contents in this case. See the comment
> > above foreground_layer_ in composited_layer_mapping.h.
> > 
> > [1] DCHECK originally added in: https://crrev.com/9a2cdc8d96d. Reading
> > the comments, I think the DCHECK was intended to ensure the background
> > would not be painted into the foreground layer.
> > 
> > Bug: 861948
> > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
> > Change-Id: I7409cbe9ac61fed444856df342d0707d6babab09
> > Reviewed-on: https://chromium-review.googlesource.com/1173532
> > Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
> > Commit-Queue: Philip Rogers <pdr@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#584802}
> 
> TBR=pdr@chromium.org,chrishtr@chromium.org
> 
> Change-Id: Ifd22a963dbd5ce288dfb31ab1e8ac41ebe63062d
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 861948
> Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
> Reviewed-on: https://chromium-review.googlesource.com/1184109
> Reviewed-by: Philip Rogers <pdr@chromium.org>
> Commit-Queue: Philip Rogers <pdr@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#584895}

TBR=pdr@chromium.org,chrishtr@chromium.org

Change-Id: I569313a9d5e1dd0b79e541cc3e3ae8816c4c3e05
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 861948
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Reviewed-on: https://chromium-review.googlesource.com/1184181Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584911}

Because changes to the MultiDevice feature prefs need to go through the
MultiDevice service, we want all reading and writing to occur through
that medium.

This CL migrates the MultiDevice Settings UI to read feature prefs from
the MultiDevice service instead of the settings page's prefs object.

Change-Id: I3c4ddb3886faf68e37c4a8a3cacd2fe87b58328e
Reviewed-on: https://chromium-review.googlesource.com/1179368
Commit-Queue: Jordy Greenblatt <jordynass@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584910}

Per the mocks, in the mini view the Assistant icon should be in its
wavy state.

Bug: b:112904117
Change-Id: Ic29c447e23d39c629a4cd2856b3953e620af0192
Reviewed-on: https://chromium-review.googlesource.com/1183973
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584909}

Decision was made to launch explore in a browser tab instead of within
Assistant container. As such, we can deprecate the deep link and will
instead use the OpenUrlResponse interaction flow.

Bug: b:111704177
Change-Id: Iec68644f0b7c8df23c3926e89fae1283f3f6fd11
Reviewed-on: https://chromium-review.googlesource.com/1183965
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584908}

Bug:773084
Change-Id: I8ef6fe66ad10246e62e926f11d1d54ef209d300c

NOTRY=true

TBR=mythia@chromium.org, ulan@chromium.org

Change-Id: I8ef6fe66ad10246e62e926f11d1d54ef209d300c
Reviewed-on: https://chromium-review.googlesource.com/1183905Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#584907}

Bug: 874261
Change-Id: I5973ae1a7afd1a0ffd6f2dd61df679cc566e998a
Reviewed-on: https://chromium-review.googlesource.com/1180253Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Mitsuru Oshima (Slow) <oshima@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584906}

In case of long relying party IDs, we should not truncate them.

Bug: 849323
Change-Id: Idbfb63866c54bd98b6a9006f47c59291a29bc4cc
Reviewed-on: https://chromium-review.googlesource.com/1183494Reviewed-by: Jun Choi <hongjunchoi@chromium.org>
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584905}

This patch uses Input.dispatchTouchEvent instead of
Emulation.setEmitTouchEventsForMouse. This gives more predictable
behavior and allows for each touch event to be awaited.

Bug: chromedriver:2144
Change-Id: Ic243c216e2f832844a64f8f2af894eb6cc4234d1
Reviewed-on: https://chromium-review.googlesource.com/1182506
Commit-Queue: Joel Einbinder <einbinder@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584904}

This CL adds a new page to the flow; the page utilizes the
chrome.quickUnlockPrivate extension API to check the user's password.

In a future CL, the auth token received from the API will be provided
to the MultiDeviceSetup Mojo service when setting the host device.

Bug: 870098, 824568
Change-Id: Ie10f6b2560a03c8879d8b7226d36e93c0311887c
Reviewed-on: https://chromium-review.googlesource.com/1180482
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584903}

This CL provides two new pieces of functionality:
(1) UiPages can disable the forward button.
(2) UiPages can prevent forward navigation, even though the button is
    enabled.

This functionality is needed for a future CL which adds a password page.
In that CL, the page's forward button needs to be disabled if no
password has been entered yet, and forward navigation needs to be
prevented if the password entered is incorrect.

Bug: 870098, 824568
Change-Id: Id887c97d4b336d6b44f4aaa567d81e0ed73f9d5d
Reviewed-on: https://chromium-review.googlesource.com/1179268
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584902}

BUG=841655

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: I2d112cfc5262e02963d1151f19f721cd84fa756f
Reviewed-on: https://chromium-review.googlesource.com/1181178Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584901}

MediaPipelineBackendManager's playing audio streams counts are now
separated by ContentType.
Added a IsPlaying method that can be called to check if there are
playing streams for a specific ContentType.

Bug: 112661891
Test: CQ and Checking with logs.
Change-Id: I81f1268fd1c46db665b9fec5cf729049932bcc2d
Reviewed-on: https://chromium-review.googlesource.com/1183952
Commit-Queue: Jimmy Tobin <jtobin@google.com>
Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584900}

Bug: 870864
Change-Id: Iae47b89761e9fff42a3fe4a8cf52bef391900988
Reviewed-on: https://chromium-review.googlesource.com/1183964
Commit-Queue: Quan Nguyen <qnnguyen@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584899}

Bug: b/112310573
Test: Manual Test
Change-Id: I3e959a5c2eb4413a306fbc33fc930757d074aeeb
Reviewed-on: https://chromium-review.googlesource.com/1182677Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Yue Li <updowndota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584898}

Bug: 876119
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Icf8628ea868bb76b27477022ee4068ed971a32ce
Reviewed-on: https://chromium-review.googlesource.com/1182509
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584897}