- From: Google <sysbot+gh@w3.org>
- Date: Thu, 13 Jul 2017 20:01:06 +0000
- To: public-secondscreen@w3.org
I consider the PR I uploaded to be the minimum needed to close this issue. Regarding other aspects: I'm not sure if I have a good grasp of what "X, Y, and Z" MUST be implemented by all remote playback devices. That would require understanding better the constraints of current and future implementations, and sounds like specifying a remote playback device itself, which may not be in scope of this spec. Obviously devices that don't support basic commands like pause, mute, etc. are very bad implementations, but not confident enough to specify what is "bad" at this point. Let me think about it, but not sure it should block going to CR. As far as feature detection of supported capabilities of the remote device, I could see this being very useful, for example for a player library that wants to support remote playback on multiple devices with different capabilities. My thinking is adding capability detection would a useful extension to the Media Capabilities API based on implementation experience and developer feedback. Again not blocking CR. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/41#issuecomment-315186390 using your GitHub account
Received on Thursday, 13 July 2017 20:01:13 UTC