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

Progress bar woes on 5.0.0 #2652

Closed
indreksiitan opened this issue Sep 30, 2015 · 6 comments
Closed

Progress bar woes on 5.0.0 #2652

indreksiitan opened this issue Sep 30, 2015 · 6 comments

Comments

@indreksiitan
Copy link

Hi,

coming here with the previous issue I discovered that 5.0.0 is now out (was running on 4.12 before). So I upgraded in hopes that it just might fix my problems, but instead, unfortunately, it created a small new one:

Now the video player shows the "LIVE" badge and the progress bar starts off somewhere in the middle. Below attached is a sample of a 48 second video that I just started.

screenshot 2015-09-30 11 29 42

Since the video is stored in a web app, it's dynamically served through a PHP script - might this be the culprit?

TIA,
Indrek

@mmcc
Copy link
Member

mmcc commented Sep 30, 2015

Well the styling issues across the control bar is an issue regardless. The ordering on the right side is strange and the time remaining / live component shouldn't be at the top of the control bar like that. Do you have a live example that we can take a peek at?

Re: delivery, the only times I've seen issues on this tracker involving video dynamically served via PHP, it's been the culprit. For varying reasons, so unfortunately I don't have a "oh it's probably this" kind of answer, but it's consistently been the root cause :(

@gkatsev
Copy link
Member

gkatsev commented Oct 19, 2015

Only other thing I can think off is that the browser you're running this on isn't fully supported by our css (for whatever reason). What browser are you using?

@indreksiitan
Copy link
Author

I'm running the latest and greatest Safari. But looks like this problem has somehow magically solved itself in the meantime.

@gkatsev
Copy link
Member

gkatsev commented Oct 19, 2015

Huh, weird. Can we close the issue then and re-open if it re-manifests itself?

@indreksiitan
Copy link
Author

Fine by me.

@gkatsev
Copy link
Member

gkatsev commented Oct 19, 2015

Cool, closing for now then.

@gkatsev gkatsev closed this as completed Oct 19, 2015
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants