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
Facebook embedded video do not work on HTTP. #1898
Comments
Can you provide a URL or the iframw code to check how you are setting it up? You are testing this on the 3.x-dev branch? |
The issue is because you are using a URL that starts with https; change it to http and that might solve it |
tried with HTTP
did not solve. |
@Ron666 I can send a link but not on public |
Sure send it to my email; you will find it on my profile |
@MosheL It should be fixed now; in the test file, the renderer was missing. Please let me know if that worked. Thanks |
Can this ticket be closed? |
need to check it. thanks |
Update: I was re-downloaded the test file. |
Unfortunately, this is a limitation on Facebook embed (as well as Vimeo) so nothing we can do about it |
If this is correct, we must disable the ME toolbar on this case. |
@MosheL After some research I was able to achieve the hiding of controls; please download the latest version of 3.x-dev branch and let me know. Thanks |
|
Thanks. I'll check this and keep you posted ASAP about the fix |
@MosheL Please download and test this again; I found some issues and took me some time to figure out why fullscreen was not behaving as it should with the full player |
|
Update: other tools on toolbar did not work, and also Play after video ended. |
Yeah Facebook videos are not as mature as the other renderers and are very limited with the features we offer related to time wise; for now just remove any features that don't work and I'll check the play issue. That will be the last thing I can do in the Facebook side. Thanks |
@MosheL Fixed the issue with Play with video ended. Facebook right now doesn't account for a |
@MosheL Update: I was able to make the progress bar click to work. Also, most of the features related to time must be working right now; please confirm and let me know |
Update: FB is working. I can skip the timeupdate and similar. https://www.facebook.com/VirallUSA/videos/vb.201208910316415/204884829948823/ |
I'll test setting dimensions for live videos I never considered that. Thanks for pointing this out |
update: .mejs-mediaelement {overflow: hidden} |
I'll give you an update soon. That link is still active? |
I just used https://www.facebook.com/MdRaqibulHasanRana/videos/1121837361186419/ and no issues. The only thing I noticed is volume but I'm checking that right now. The link you posted is not active and that might be causing the issues you are seeing |
@MosheL I haven't found any information in regards of live videos and how to interact with them. Seems that is very limited now. I'll continue searching but as it is right now, Facebook renderer is very stable. Feel free to close this ticket if you consider it. Thanks |
The problem is the live video are closed so I can't add a realable link. also there is a diffrent between RTMP-sourced live stream and phone-sourced live stream. The live stream you are used is a RTMP-sourced and its 16x9. if you will use a phone and start broadcasting (like this ugly test: https://www.facebook.com/admini/videos/10154655923894932/?pnref=story ) you will get a diffrent ratio. |
For now there's a lack of documentation as you know so there's no much we can do at this stage. As soon as updates come to the Facebook videos we'll integrate them or simply use the iframe |
so close this and reopen a new one about the live problem? |
Yeah that's fine. Thanks |
I am trying to use Facebook Embedded, on HTTP website. Its doesn't works and I am reciving this error message:
Uncaught SecurityError: Blocked a frame with origin "..." from accessing a frame with origin "https://www.facebook.com". The frame requesting access has a protocol of "http", the frame being accessed has a protocol of "https". Protocols must match.
The text was updated successfully, but these errors were encountered: