Open jondot opened 11 years ago
My lazy, unconfirmed answer would be that browsers on mobile devices require "human opt-in" to playback HTML5 media and fail silently when api calls are made.
(Now I'm going to set this up and test)
Rick
On Tue, Mar 26, 2013 at 11:34 AM, Dotan J. Nahum notifications@github.comwrote:
Hi, Looks like Chrome beta (possibly non-beta too) not playing via the #play() interface.
To reproduce, hook remote debugging to your mobile device, and within Chrome Beta, go to http://popcornjs.org and issue a Popcorn('#video').play() in the Javascript Console on your desktop (which is remote debugging the mobile Chrome).
Nothing will happen.
Thanks.
— Reply to this email directly or view it on GitHubhttps://github.com/mozilla/popcorn-js/issues/305 .
I think you're right. Though I thought this only includes 'autoplay' to avoid unattended battery drain and not explicit Javascript calls. Thanks in any case
On Tuesday, March 26, 2013, Dotan J. Nahum wrote:
I think you're right. Though I thought this only includes 'autoplay' to avoid unattended battery drain and not explicit Javascript calls. Thanks in any case
Explicit JavaScript calls would allow a side channel autoplay
Rick
—
Reply to this email directly or view it on GitHubhttps://github.com/mozilla/popcorn-js/issues/305#issuecomment-15488327 .
Hi, Looks like Chrome beta (possibly non-beta too) not playing via the #play() interface.
To reproduce, hook remote debugging to your mobile device, and within Chrome Beta, go to http://popcornjs.org and issue a Popcorn('#video').play() in the Javascript Console on your desktop (which is remote debugging the mobile Chrome).
Nothing will happen.
Thanks.