Users are reporting issues with Facebook OneBox and iframe embeds no longer playing inline, particularly on mobile devices, with links opening in new windows and requiring Facebook login. audiotech provides video evidence of the issue on macOS and Android, and shares example links. osioke confirms the links work for them on mobile, suggesting a possible configuration or browser-specific issue. Canapin raises additional questions about Facebook login prompts for public posts, the purpose of the facebook_app_access_token setting, and Instagram embed functionality despite the token being empty, noting a display issue with iframe height.
It seems like something have changed at Facebook that neither OneBox nor iframe is playing inline how it’s supposed to. This was ok yesterday but just a while ago every FB source opens a new window and requires a login to Facebook.
Can anyone confirm this?
Additional note:
Other sources I have tested that plays inline fine includes YouTube, Twitch and direct from Amazon S3.
They both play fine for me here on Meta using my mobile phone and checking across DiscourseHub, Chrome and Safari. Firefox doesn’t show the embeds though, but generally my Firefox on iOS doesn’t do well with videos.
I have several questions regarding Instagram/Facebook embedding.
I have the Facebook login message when I paste Facebook link and I struggle to see where does it come from.
Example:
This is a public post that can be seen when logged out from Facebook.
So what’s the issue here? How can I embed public Facebook posts or videos? I tried using the search, but I couldn’t find any clear explanation or solution… A lot of highly technical messages also.
I see that there is a Discourse setting names facebook_app_access_token, which description is:
A token generated from your Facebook app ID and secret. Used to generate Instagram oneboxes.