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

Playback speed not adjustable for non-logged-in users in TUM-Live #1395

Open
laxerhd opened this issue Nov 3, 2024 · 0 comments · May be fixed by #1400
Open

Playback speed not adjustable for non-logged-in users in TUM-Live #1395

laxerhd opened this issue Nov 3, 2024 · 0 comments · May be fixed by #1400
Assignees

Comments

@laxerhd
Copy link

laxerhd commented Nov 3, 2024

Describe the bug
When embedding TUM Live videos into a website (e.g. via iframes in Artemis), you cannot change the speed of the video.
If you want to change it, you have to log in to TUM-Live first, and then you will get the options back in your iframe.
The same applies if you want to watch a video in TUM-Live, when you are not logged in.

To Reproduce
Steps to reproduce the behavior:

  1. Logout from your TUM-Live Account
  2. Select any lecture vod (or in the case of iframes go to Artemis and select an embedded lecture from TUM-Live)
  3. Take a look at the speed section on the bottom right

Expected behavior
It would be nice to have at least some speed options when not logged into your account for convenience.

Screenshots
Not logged in to TUM-Live:
image
Logged in to TUM-Live
image

Additional context
I think this functionality was still there when there were no “playback speed settings” for an account.
So this bug was probably introduced back then.

@karjo24 karjo24 self-assigned this Nov 5, 2024
@karjo24 karjo24 linked a pull request Nov 7, 2024 that will close this issue
@karjo24 karjo24 linked a pull request Nov 7, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants