W3C home > Mailing lists > Public > public-secondscreen@w3.org > April 2017

Re: [remote-playback] Interoperability concerns by lack of a common denominator in transport

From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
Date: Sat, 22 Apr 2017 09:55:01 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-296362110-1492854900-sysbot+gh@w3.org>
@cynthia you are right that this is not ideal but one goal of this API was to offer a way for the web page to trigger the current "fling" feature that browsers have implemented by default (Chrome and Firefox offer Cast on Android, Safari offers Air Play). A user trying to "fling" a video shouldn't have to care whether it is using the API or the built-in feature. The concerns of not being able to use an AirPlay device from Android is larger than this API and anyone with such a configuration will be aware of the issue. Therefore, in our opinion, it is very unlikely that a user will have an unexpected/bad experience with this API.

GitHub Notification of comment by mounirlamouri
Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/74#issuecomment-296362110 using your GitHub account
Received on Saturday, 22 April 2017 09:55:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:19:02 UTC