I cannot reproduce on M61 or M62 on the MediaSession API demo page (HTTPS). @jws.fmbb - does the MediaSession API demo page work for you?

https://googlechrome.github.io/samples/media-session/video.html

It does not, nor does the audio sample page.

Chrome Dev 61.0.3163.27
Android 7.0 patch June 1 2017, Samsung Galaxy 6.

Again, the Chrome stable 59 is working fine, as is the webview that the gmail client decided to open instead of opening the browser in full.

Thank you for providing more feedback. Adding requester "beccahughes@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

(so update - Chrome 61 not 62, my apologies for losing track of where each branch is)

Chrome 60 "Beta" on the phone and it is still working. I see that the 60-61-62 upgrades are coming, according to the release blog, so I'll test again as soon as my phone is given them in the rollout.

Trying other devices: an older Samsung tab running 4.2.2 and the same version of Chrome dev 61 as above IS still working, so it may be some flag or something about the O/S that has accidentally turned it off?

let me go through the chrome://flags and privacy settings and see if I turned notifications off or something by accident...

Resolve this as "not a bug" and close, please.

In the settings at the System level (as in android gear menu, App settings), there ended up being a separate entry now for Notifications and it was changed to 'Blocked'. 

I do not know why as I have no memory of doing it unless it was one of those dialogs that appeared just as I was about to tap something else and accidentally hit it (and caused it to hide away) before I realized what I did.  At least that is my first guess.

In any case, thank you for your patience and initial attention to this. Things are now fine after turning the notifications setting back to normal.

The NextAction date has arrived: 2017-08-15