[MediaSession] A fix for MediaSessionService routing

[MediaSession] A fix for MediaSessionService routing

Previously, MediaSessionImpl uses the metadata and controls to determine
whether a page uses the MediaSession API. However there comes an issues
that we need to update the routed MediaSession every time when a service
is created/destroyed or its metadata/controls changed, which is a lot of
maintainance work.

This CL simplifies the MediaSessionService routing strategy. It only
checks whether a service is created for a given frame. The rationale is
that a MediaSessionService is created when and only when anything passes
through mojo, which is enough for indicating whether a frame uses
MediaSession API.

BUG=670319
Committed: https://crrev.com/7f5596e8dcfd88ba7700393dd937eafb9ea39167
Cr-Commit-Position: refs/heads/master@{#439488}

[Zhiqiang Zhang (Slow), 2016-12-19 11:58:02]

zqzhang@chromium.org changed reviewers:
+ mlamouri@chromium.org

[Zhiqiang Zhang (Slow), 2016-12-19 11:58:03]

PTAL :)

Found this issue when working on the playbackState.

[mlamouri (slow - plz ping), 2016-12-19 12:20:58]

lgtm

[Zhiqiang Zhang (Slow), 2016-12-19 13:18:54]

The CQ bit was checked by zqzhang@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-19 13:19:01]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Zhiqiang Zhang (Slow), 2016-12-19 13:19:54]

Description was changed from

==========
[MediaSession] A fix for MediaSessionService routing

Previously, MediaSessionImpl uses the metadata and controls to determine
whether a page uses the MediaSession API. However there comes an issues
that we need to update the routed MediaSession every time when a service
is created/destroyed or its metadata/controls changed, which is a lot of
maintainance work.

This CL simplifies the MediaSessionService routing strategy. It only
checks whether a service is created for a given frame. The rationale is
that a MediaSessionService is created when and only when anything passes
though mojo, which is enough for indicating whether a frame uses
MediaSession API.

BUG=670319
==========

to

==========
[MediaSession] A fix for MediaSessionService routing

Previously, MediaSessionImpl uses the metadata and controls to determine
whether a page uses the MediaSession API. However there comes an issues
that we need to update the routed MediaSession every time when a service
is created/destroyed or its metadata/controls changed, which is a lot of
maintainance work.

This CL simplifies the MediaSessionService routing strategy. It only
checks whether a service is created for a given frame. The rationale is
that a MediaSessionService is created when and only when anything passes
through mojo, which is enough for indicating whether a frame uses
MediaSession API.

BUG=670319
==========

[commit-bot: I haz the power, 2016-12-19 13:59:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-19 13:59:23]

Dry run: Try jobs failed on following builders:
  win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)

[Zhiqiang Zhang (Slow), 2016-12-19 14:11:24]

The CQ bit was checked by zqzhang@chromium.org

[Zhiqiang Zhang (Slow), 2016-12-19 14:11:24]

The patchset sent to the CQ was uploaded after l-g-t-m from
mlamouri@chromium.org
Link to the patchset: https://codereview.chromium.org/2585243002/#ps20001
(title: "fixed compile warning")

[commit-bot: I haz the power, 2016-12-19 14:11:38]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-19 16:27:50]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1482156684218830,
"parent_rev": "88cff48f8b9a105e8242f0d893537a297a8e0b26", "commit_rev":
"ff46458e0b08c023b72283ce7827792993f2753b"}

[commit-bot: I haz the power, 2016-12-19 16:28:23]

Description was changed from

==========
[MediaSession] A fix for MediaSessionService routing

Previously, MediaSessionImpl uses the metadata and controls to determine
whether a page uses the MediaSession API. However there comes an issues
that we need to update the routed MediaSession every time when a service
is created/destroyed or its metadata/controls changed, which is a lot of
maintainance work.

This CL simplifies the MediaSessionService routing strategy. It only
checks whether a service is created for a given frame. The rationale is
that a MediaSessionService is created when and only when anything passes
through mojo, which is enough for indicating whether a frame uses
MediaSession API.

BUG=670319
==========

to

==========
[MediaSession] A fix for MediaSessionService routing

Previously, MediaSessionImpl uses the metadata and controls to determine
whether a page uses the MediaSession API. However there comes an issues
that we need to update the routed MediaSession every time when a service
is created/destroyed or its metadata/controls changed, which is a lot of
maintainance work.

This CL simplifies the MediaSessionService routing strategy. It only
checks whether a service is created for a given frame. The rationale is
that a MediaSessionService is created when and only when anything passes
through mojo, which is enough for indicating whether a frame uses
MediaSession API.

BUG=670319

Review-Url: https://codereview.chromium.org/2585243002
==========

[commit-bot: I haz the power, 2016-12-19 16:28:24]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-12-19 16:31:51]

Description was changed from

==========
[MediaSession] A fix for MediaSessionService routing

Previously, MediaSessionImpl uses the metadata and controls to determine
whether a page uses the MediaSession API. However there comes an issues
that we need to update the routed MediaSession every time when a service
is created/destroyed or its metadata/controls changed, which is a lot of
maintainance work.

This CL simplifies the MediaSessionService routing strategy. It only
checks whether a service is created for a given frame. The rationale is
that a MediaSessionService is created when and only when anything passes
through mojo, which is enough for indicating whether a frame uses
MediaSession API.

BUG=670319

Review-Url: https://codereview.chromium.org/2585243002
==========

to

==========
[MediaSession] A fix for MediaSessionService routing

Previously, MediaSessionImpl uses the metadata and controls to determine
whether a page uses the MediaSession API. However there comes an issues
that we need to update the routed MediaSession every time when a service
is created/destroyed or its metadata/controls changed, which is a lot of
maintainance work.

This CL simplifies the MediaSessionService routing strategy. It only
checks whether a service is created for a given frame. The rationale is
that a MediaSessionService is created when and only when anything passes
through mojo, which is enough for indicating whether a frame uses
MediaSession API.

BUG=670319

Committed: https://crrev.com/7f5596e8dcfd88ba7700393dd937eafb9ea39167
Cr-Commit-Position: refs/heads/master@{#439488}
==========

[commit-bot: I haz the power, 2016-12-19 16:31:52]

Patchset 2 (id:??) landed as
https://crrev.com/7f5596e8dcfd88ba7700393dd937eafb9ea39167
Cr-Commit-Position: refs/heads/master@{#439488}