22
Replies
While it is true that the browsers have implemented some measures to prevent auto play - the big ugly play button you see at the beginning of your project is brought to you courtesy of Adobe. I believe this was implemented to force your learners to interact with the project which will allow any automatic audio or video in your project to function per the browser standard.
The major problem with this is that even projects which have no audio or video in them - and therefore no reason to be blocked from any autoplaying - still have to deal with this issue. This is an unecessary forced nuisance. If you design your projects with a start screen to force interaction anyway - it will never be an issue.
There is a couple ways around it that you may find floating around. If you do have automatically playing audio in your project - the browser will still block it because they force interaction with the project to activate the audio. The workarounds get you past the Adobe play button - but not past the browser block.
Here is what I do to get past the Play button but it has to be done after you publish your project. This works well for desktop and laptop engagement but has mixed results on mobile touch devices. I am still trying to figure out a relatively simple solution to simulate the touch versus a click.
After publish - open the index.html file in your favorite editor.
Head down to line 96 - add the highlighted text - see pic below.
Save the changes.
Here is the pic of the code. Also here is the code in the script:
{
var tag = document.createElement('script');
tag.src="https://player.vimeo.com/api/player.js";
document.getElementsByTagName('head')[0].appendChild(tag);
}
}
cpInit();
$(document.ready(function() {
$("#playImage") .click();
});
initialized = true;
if(isLivePreview() === true)
{
cp.previewFolder = window.location.href.split("\/")[4];
setInterval(isLivePreviewDirty, 1000);
}
}
 
AdChoices