On Mon, 12 Dec 2016, at 04:00, Boris Zbarsky wrote: > On 12/11/16 8:47 AM, Mounir Lamouri wrote: > > On Sat, 10 Dec 2016, at 17:58, Boris Zbarsky wrote: > >> OK, but a website doing this won't work in Chrome Android. So what > >> would websites actually do in practice? > > > > Not sure what you mean wouldn't work. If a website is a good web citizen > > and uses PresentationRequest with an array of URLs such as > > ['http://example.com', 'cast://example', 'dial://example', > > 'mozapp://example' ], Chrome Android will work fine because it will use > > the "cast://" URL. > > I may just be missing something or misunderstanding how the API works... > > Is the 1-UA vs 2-UAs mode thing transparent to the page? Based on the > descriptions of the modes it sounded to me like you can do things in at > least 2-UAs mode that you can't do in 1-UA mode; not sure about vice > versa. So presumably it's not entirely transparent? Or is the idea > that anything that works in 1-UA mode is available in 2-UAs mode and the > APIs are identical for that subset of functionality, so a page that > pretends like it's always working with 1-UA mode will just work with > 2-UAs mode?
What specifically do you have in mind when you say that 1-UA mode might lack features? Technically, 1-UA mode is when a page is rendered on the client and sent to the remote device. It's mostly a technical detail because one can't render HTML pages on a Chrome Cast without creating an application, Chrome folks call pure HTML rendering 1-UA mode. It is fairly similar to tab mirroring. I don't think any feature should be lacking except maybe access to the APIs on the other device. -- Mounir _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
