Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconnecting media elements to the playback #5

Open
avayvod opened this issue Jan 15, 2016 · 8 comments

Comments

@avayvod
Copy link
Contributor

commented Jan 15, 2016

Tracking issue for the following problem:

  • what happens when the page that is playing a media element remotely navigates / reloads?
  • should it be able to reconnect somehow to the remote playback session?

Following the Presentation API experience, the page would get an id from the start() call / onconnected event and then pass it to another call like join(playbackId) to attach the media element to the remote playback session without prompting the user again.

@mounirlamouri

This comment has been minimized.

Copy link
Member

commented Jan 18, 2016

I think we should stop the media on the remote device if the page is navigated. Otherwise, we are going to recreate a Presentation API.

@jernoble, WDYT? It seems that Safari iOS stops the session if the page is reloaded but kind of keep it alive if the page is navigated.

@jernoble

This comment has been minimized.

Copy link

commented Jan 19, 2016

@mounirlamouri I think that would be best (if we stopped the session if the page was navigated).

@avayvod

This comment has been minimized.

Copy link
Contributor Author

commented Feb 3, 2016

FWIW, both Chrome and Firefox don't stop the playback in these cases so may be we could be more flexible and say that the UA can continue playing the video remotely and provide user with some browser controls?

For Chrome, we're going to gather some data on the usage and see if it's useful but continuous playback no matter what as long as there's a way to stop it is preferred by the Chromecast guidelines and seems better for the user (although not for the developer). WDYT?

@avayvod

This comment has been minimized.

Copy link
Contributor Author

commented Feb 4, 2016

@jernoble would you be okay with the proposal above?

@jernoble

This comment has been minimized.

Copy link

commented Feb 4, 2016

@avayvod Because it may not be a choice that the UA makes (the remote end may choose to end or continue playback when the UA disconnects without input from the UA) I'd be happy if there was some explicit flexibility in the spec w.r.t. the behavior when the page closes or is navigated.

@avayvod

This comment has been minimized.

Copy link
Contributor Author

commented May 3, 2016

As I understand it, the resolution is to allow some flexibility in the spec so that the remote playback session doesn't have to be stopped when the media element goes out of scope, however, having a way to reconnect to the running session is not desired at this point (we could revisit it later if there's developer's demand for this API vs Presentation API allowing reconnecting, for example).

avayvod added a commit that referenced this issue May 11, 2016
@avayvod

This comment has been minimized.

Copy link
Contributor Author

commented May 11, 2016

Added a note to the Stopping remote playback section of the spec.

@avayvod avayvod closed this May 11, 2016
@anssiko

This comment has been minimized.

Copy link
Member

commented May 24, 2019

We revisited this issue at F2F, so I'll reopen so we remember to update the spec with the latest considerations from the Open Screen Protocol.

Related F2F discussion: https://www.w3.org/2019/05/24-webscreens-minutes.html#x08

@mfoltzgoogle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.