Define and use the virtual platform API with which media sessions interact

[xxyzzzq]

From @foolip on September 2, 2015 14:44

The spec currently defines some things in terms of what kind of media session caused a callback, with a fallback for when it was caused by something external. For example:

Let interrupting media session category be the media session category that triggered this interruption. If this interruption has no known media session category, let interrupting media session category be Default.

The way we want to implement media sessions, at least on Android, is instead to let each media session individually interact with the platform API, which implies that you would never know if an interruption comes from another media session or something else.

My proposed fix for this is to define a virtual platform API with roughly the following shape:

• A method to request audio focus of different kinds, and one to abandon it.
• Callbacks when you gain and lose audio focus, and the reason it happened.

Then define how an individual media session interacts with this system, instead of defining the interactions in terms of other media sessions.

Copied from original issue: WICG/mediasession#100

[xxyzzzq]

Closing this issue since we are moving audio focus out to a separate API.

[xxyzzzq]

From @rektide on September 19, 2016 17:53

@xxyzzzq what is that separate API? how can we follow-up/where do we look instead of here?

[xxyzzzq]

We haven't created a repo for the AudioFocus API yet. It is #138