Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VideoTime Pro not ignoring Prevent Fast Forwarding & Resume Playback settings in Workplace #82

Open
jprovasnik opened this issue Oct 17, 2024 · 3 comments

Comments

@jprovasnik
Copy link

Hello, I'm using VideoTime pro 1.8.2 (2024050702) on Moodle Workplace 4.4.4+ Rolling (Build: 20241014)
Our site settings for the plugin have Prevent fast forwarding disabled, and have Resume playback enabled. However both of these settings are not being respected (tried in Chrome and Edge) -- no issues in FireFox.

Site settings / internal activity settings match:
Settings

In Chrome / Edit - moving the scrubber has no effect, no matter how long the video has been up on the screen. Also no matter how much I watch, when I exit the video and return, it re-starts from the beginning:
Edge

In FireFox, the video appears to "pre-load" (meaning, I see a light gray bar load along the play bar) and I can scrub to another location pretty much immediately upon page load (even with an hour long video) within that light gray bar region. When I exit and re-enter the video, it also does continue playback where it left off:
FireFox

The video is being blocked in Safari and I assume it's a CloudFlair issue.

Any suggestions for helping me troubleshoot this inability to scrub? Or is this a browser issue?

@jprovasnik
Copy link
Author

I use a custom WorkPlace theme (Kenai, by MoodleUS) but this happens in Boost theme as well.

@stefanscholz
Copy link
Member

Hi @jprovasnik ,

Thanks for getting in touch!

Can you please explain what kind of video you use? Looking at the screenshot you provided, it seems to be using videojs, so probably not a Vimeo video, right? Different browser Support different video formats so maybe that's the reason?

It would be great to have an example of a video so that we can test it on our test sites. Feel free to reach out privately privately via email.

Be aware that we recently published a new version of video time (1.8.3), so if you have a test site available, it might be worth checking if the issues remain with the new version.

The most common reasons for such problems by the way are JavaScript errors, which might be caused by a different plug-in or maybe an incompatibility of video time with something on your site. I recommend reviewing the console in your browser to see if that's the case. Such issues often are different from browser to browser so it's not surprising that it works in one browser but not the other. Safari in particular is a bit picky in some areas. It works fine though on our test sites with any browser so it must be something specific either with your specific video type or source, or with your platform.

Hope this helps,
Stefan

@jprovasnik
Copy link
Author

jprovasnik commented Oct 17, 2024

Thanks for the info. Two clarification notes:
1 - In Chrome and Edge, when I try to scrub to a new location, the video not only doesn't scrub, it resets back to 0:00.
2 - The issue is specific to videos directly uploaded into the VideoTime activity (not links to Youtube/Vimeo); In fact, there appears to be no issue with videos from Youtube links - they are pausing and resuming as expected.

I've attached a small sample video: https://app.cure4kids.stjude.org/static_assets/file_example_MP4_480_1_5MG.mp4

This is what I see in the console for Chrome:
consol

which appears to be located here?
init: function() {
started || (started = !0,
isMoodleIframe() ? window.console.log("Not starting Moodle session timeout warning in this iframe.") : (window.console.log("Starting Moodle session timeout warning."),
start()))
}

And this is what I see in the console for Edge:
Edge

I will try to test out an updated version of the plugin to see if that helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants