Closed phloxic closed 7 years ago
@tipiirai - regardless of the UI "status display": I need to know the exact expected behavior. Mainly it's not clear when it should pause when scrolling out of view. Currently it sometimes does, it sometimes does not.
Technically (while it's still mute) it also needs sometimes 2 clicks to resume, sometimes 1 ...
When using the plugin the player should always pause when it's outside the viewport. Regardless of the state. And it should resume when it's on the viewport, but not when the user has manually pressed pause.
When the player is muted (with the extra layer) the player should unmute and play with one click. 2 clicks is an issue.
I noticed this is surprisingly complex given the seemingly simple feature. Maybe there is still a case that the above didn't cover?
Thanks for the clarification, that helps. So:
autoplay and especially muted autoplay can quickly become a can of worms, not least because of https://github.com/flowplayer/flowplayer/issues/1259 - ping @nnarhinen
I'll have a go.
The way it looks to me right now, I would also suggest to enable this only when both autoplay and muted are set; at least for the time being, otherwise it becomes even more confusing.
No.
It should use the viewport autoplay stuff without the "Click to unmute" overlay when muted
is false
ok - at least for the moment I will start with muted, one step at a time. There is even more of a muddle with muted unset when mutedAutoplay is supported. - api.muted is always undefined ...
Fixed - @tipiirai, please check at https://releases.flowplayer.org/viewport-autoplay/index.html
That is: on return the player is paused, does not resume, so an fp-play element should be shown - or the player should resume.