Chrome Version : 72.0.3595.2
OS Version: Chrome
What steps will reproduce the problem?
1. browser_tests --gtest_filter=AudioPlayerBrowserTest.NativeMediaKey --enable-features=MediaSessionAccelerators
What is the expected result?
Test should pass
What happens instead of that?
Doesn't.
I don't think the CrOS AudioPlayer isn't hooking any special permission to do this, so it's possible stuff on the wider web is broken too.
I think the MediaSessionAccelerators handling is swallowing the event before WebContents gets a chance to see it and, e.g., preventDefault() on the keydown event (so that the media session *never* sees it).
The test landed recently as a regression test for Issue 899094
Chrome Version : 72.0.3595.2
OS Version: Chrome
What steps will reproduce the problem?
1. browser_tests --gtest_filter=AudioPlayerBrowserTest.NativeMediaKey --enable-features=MediaSessionAccelerators
What is the expected result?
Test should pass
What happens instead of that?
Doesn't.
I don't think the CrOS AudioPlayer hooks any special permission to do this, so it's possible stuff on the wider web is broken too.
I think the MediaSessionAccelerators handling is swallowing the event before WebContents gets a chance to see it and, e.g., preventDefault() on the keydown event (so that the media session *never* sees it).
The test landed recently as a regression test for Issue 899094
The following will work now:
browser_tests --gtest_filter="*PlayerBrowserTest.NativeMediaKey" --enable-features=MediaSessionAccelerators --enable-audio-focus --enable-blink-features=MediaSession
Comment 1 by tapted@chromium.org
, Nov 7