-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add "connecting" to the RemotePlaybackState enum #3
Comments
Adding this sounds good, but I agree that throwing exceptions sounds weird. Can't the handover be atomic, so that all commands are applied either locally or sent to the remote? Also, is "once start() is resolved, the state changes to |
I think we could rename The spec might want to specify if we must have a I think the We could then add a |
Should the spec enforce that local playback stops while |
I guess what we do while
If we specify that, it will allow a decent default behaviour: when WDYT? |
If "allowed to pause" means that the web developer can implement that behavior but could also continue to play back locally for a bit longer, then that SGTM. I realize that an issue with the handover is that if you continue playing locally as the remote buffers while I'm not sure if a better method is likely to be employed, but if it doesn't complicate things implementation-wise then perhaps it's a door that can be left open for experimentation. I'm not adamant about it though. |
Opened #25 to track the transition specification. Closing this issue as the state is in the spec now. |
Represents the state between the time when a remote playback device has been picked by the user and when the playback of the media is ready to start on the device.
The justifications:
disconnected
toconnected
The draft summary of state changes:
disconnected
connecting
; while in this state all media commands on the video element (play, pause, seek, volume, etc) throw exceptionsconnected
disconnected
The text was updated successfully, but these errors were encountered: