"When the user presses the MediaTrackPrevious me..."

[annevk]

https://mediasession.spec.whatwg.org/#mediaremotecontrols-event-handlers

When the user presses the MediaTrackPrevious media key,

How should this happen relative to the task that is already queued for pressing that key? Should it in fact all be part of the same task, or a set of tasks (what order?).

[richtr]

This relates to the discussion starting at #21 (comment).

@foolip wrote:

My hope is that there wouldn't be any reason to use [existing input events for multimedia keys].

Ideally MediaSession should replace handling for multimedia input events.

For platforms that do currently fire multimedia key events we have three options:

1. fire multimedia key events against active media sessions. If no active media session is present, fire them as multimedia input events.
2. fire multimedia key events against active media sessions. If no active media session is present, do not fire multimedia input events at all.

The other proposal is to fire media session events after keyboard events:
3. fire keyboard multimedia key events normally and if they are not preventDefault()ed then continue to fire them again at active media sessions, if any.

Of the three options, my preference would be on (2). Once we know the order we want to fire these events (or if we want to continue firing multimedia key events as input events at all) I think we can start to look at the event timing/ordering text we need to add to the spec.

[mounirlamouri]

We need implementer feedback on this. I'm not sure what the timing should be and whether cancelling a key event should block the media session action. At the moment, Chrome did not implement an action that is also a key event so I prefer not to write something in the spec without any implementation feedback.

[foolip]

@jernoble, there's some chance you'll be the first to try to tie actions to keys on a keyboard, any thoughts?

FWIW, I can see two relative sane options:

1. If the keypress is will translate to a MediaSession action, it isn't delivered as a KeyboardEvent at all.
2. A KeyboardEvent is fired, and only if the event isn't canceled does the MediaSession action happen.

[foolip]

Ping @jernoble?

[jernoble]

AFAICT, I don't think that the media buttons will ever generate key events on Mac platforms. That they're on the keyboard (on non-Touch Bar Macs) is coincidental.

[youennf]

I think @jernoble comment still holds on Apple platforms.
If there is no change in implementations where a keypress might trigger both an event and a media session action, we could document this in the spec.
Marking as "Ready for PR" for now.

[youennf]

Closing, given the spec has been rewritten to no longer talk about key press and so on.