You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Strangely I'm having an issue with the Mojs Player tracker line being latent. It's only an issue in my Chrome Browser(Version 55.0.2883.87 m, which is the most current). In FF and IE10/Edge it seems to work fine. The error also doesn't seem to show up on CrossBrowserTesting (the site that CodePen uses for Cross Browser Testing).
Hello @zfrisch . There's a big chance your problem is related to a chrome extension. It's a really common issue. Try to run it in an anonymous window and see if the issue persists.
Hi @eltonmesquita ! Thanks for the advice. I tried this in Incognito Mode and made sure my Chrome extensions were all disabled for good measure. Unfortunately it's still showing the same on my screen.
I have seen that issue when you use the player inside an iFrame, for instance it behaves like that when you use it with webpack-dev-server. Is it true for you? Any environments details I should know about?
@zfrisch commented on Wed Dec 21 2016
Hello! Strangely I'm having an issue with the Mojs Player tracker line being latent. It's only an issue in my Chrome Browser(Version 55.0.2883.87 m, which is the most current). In FF and IE10/Edge it seems to work fine. The error also doesn't seem to show up on CrossBrowserTesting (the site that CodePen uses for Cross Browser Testing).
I recorded a video to show what I'm talking about:
https://www.youtube.com/watch?v=K_ib-3OWCuE
Here's the CodePen :
http://codepen.io/zfrisch/full/yVwmoW/
Thanks!
@eltonmesquita commented on Wed Dec 21 2016
Hello @zfrisch . There's a big chance your problem is related to a chrome extension. It's a really common issue. Try to run it in an anonymous window and see if the issue persists.
@zfrisch commented on Wed Dec 21 2016
Hi @eltonmesquita ! Thanks for the advice. I tried this in Incognito Mode and made sure my Chrome extensions were all disabled for good measure. Unfortunately it's still showing the same on my screen.
@legomushroom commented on Wed Dec 21 2016
Hi Zak, Hi Elton!
I have seen that issue when you use the player inside an iFrame, for instance it behaves like that when you use it with webpack-dev-server. Is it true for you? Any environments details I should know about?
Thanks a lot for the issue!
@legomushroom commented on Wed Dec 21 2016
Oh yeah, I think we should move this issue to https://github.com/legomushroom/mojs-player repo
@legomushroom commented on Wed Dec 21 2016
Oh I see, that's another issue actually. Interesting. Never saw that. That's for the video and codepen sample.
@legomushroom commented on Wed Dec 21 2016
Issue moved to legomushroom/mojs-player #3 via ZenHub
@legomushroom commented on Wed Dec 21 2016
Issue moved to legomushroom/mojs-player #4 via ZenHub
The text was updated successfully, but these errors were encountered: