Skip to content
This repository has been archived by the owner on Jan 4, 2019. It is now read-only.

autoplay block no longer conflicts with timeline change pause #199

Closed
wants to merge 1 commit into from

Conversation

darkdh
Copy link
Member

@darkdh darkdh commented May 17, 2017

@darkdh darkdh self-assigned this May 17, 2017
@darkdh darkdh requested review from bridiver and bbondy May 17, 2017 22:38
// If we're already playing, then this play would do nothing anyway.
// Call playInternal to handle scheduling the promise resolution.
- if (!m_paused) {
+ if (!m_paused || m_hasPlayed) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand why this is necessary. Once a user has given autoplay permission, it should last at least for the duration of the site visit. I think this is a browser-laptop issue and not a muon issue

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, it is actually blocked on muon side.
When users start playing video, it will not block. But as user drag timeline , some sites like vimeo or netflix will trigger a pause() first, and that will cause m_paused to be true and it won't continue playing.

@bridiver bridiver closed this Jun 6, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

autoplay block shouldn't weigh in once users start playing media
2 participants