I think I can also try on my test page :)

Here's a fix from the page:

http://xxyzzzq.github.io/sandbox/media-session/full-test-with-failure.html

As you can see at https://github.com/google/WebFundamentals/pull/4057/files#diff-b6ad1f10b69cb64abd579dcd65b034d8R84, we recommend setting up the media session when audio play is successful.


      // User interacted with the page. Let's play audio...
      audio.play()
      .then(_ => { /* Set up Media Session... */ })
      .catch(error => { console.log(error) });
    });


So we should be good.
However this brings another issue I filed previously at https://bugs.chromium.org/p/chromium/issues/detail?id=685118

The idea of "broken state" sounds good. Posted comments on that bug.

However that one might not solve this issue totally, such as switching src on a very slow network, in which case no failure has occurred.

FWIW we should improve audio focus and media session routing to solve this. For example, we keep the latest session alive even if it's not playing anything. In that case we'll need a "inactive" playbackState value for the web page to indicate that the session has terminated and we don't show notification for it.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot