MediaMetadata is currently sent to the browser process every time the MediaSession state changes. We may want to separate the signals.
Adding this bug entry to keep track of TODO.
Maybe I need to start working on this one to prepare for the upcoming MediaMetadata changes on the Chrome side, since I don't want the metadata be passed too frequently, especially for MediaImage.
What I now have in mind is to have MediaSessionStateChanged() only for activate/deactivate signals, and MediaMetadataChanged() for metadata update. WebContentsImpl.java will have to store a copy of java MediaMetadata since MediaSessionTabHelper will ignore the metadata if the tab doesn't have audio focus. The copy of MediaMetadata should be light enough.
WDYT guys?
Comment 1 by sheriffbot@chromium.org
, Jul 3 2016