This repository has been archived by the owner on Aug 24, 2018. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is still in progress as I still have yet to find a solution for the YouTube looping. This branch seeks to fix #130 - though. While testing out the original report, I noticed that the loop issue was only happening on YouTube embeds, and not on Vimeo embeds. But even when
loop
was true for Vimeo embeds - they were not looping in the rendered widget.A fix for the vimeo issue can be seen in dddaa88 ( which apparently has made CI unhappy ). By adding the
loop
query arg on the Vimeo url, the underlying iframe from Vimeo loops when expected to. YouTube also supports this query arg ( https://developers.google.com/youtube/player_parameters ), but it appears that mediaelement is mangling with the YouTube embed url... because even when the logic in this branch adds theloop
query arg appropriately, the iframe src that is subsequently rendered in the widget no longer has the argument:If I manually add the
loop
query arg back into the iframe URL seen above, the YouTube video no longer loops.