- ชุมชน
- คำถาม
Example https://jsfiddle.net/rost4719/1/
Works on desktop, but once switched over to mobile via the developer tool, it gets
Failed to load resource: the server responded with a status of 500 () chromewebdata/:1 Refused to display 'https://m.facebook.com/' in a frame because it set 'X-Frame-Options' to 'deny'. (index):2942 Uncaught TypeError: Cannot read properties of null (reading 'classList') at HTMLDocument.onDocumentLoad ((index):2942:19)
On PROD sites, it will also get CSP blockage since https://m.facebook.com was not used before for showing the embed therefore not configured as part of CSP.
I have run into same issue on 2 sites I manage. It worked fine less than 48 hours ago. Works fine on desktop/desktop view but not on mobile.
In my case, the plugin works on Android Chrome when viewing my Google Site directly but not via the custom domain
Same problem here. The X-Frame-Options problem is not something we can fix - this is a Meta problem.
And, for what it's worth, this problem goes back at least THREE YEARS with no resolution...
Hello all
There any update lads anyone get way to sort this issue
Is there any way to contact Meta support about this issue?
I reported this through my own FB page so other may wish to do the same.
And have you had a response from Facebook yet that this problem is known to them?
Nope
It appears FB now states in the FAQ that page plug in isn't supported on Android and IOS. https://developers.facebook.com/docs/plugins/faqs#faq_1585575021764180
I've implemented a work around with some additional CSS and a message if you're using a mobile browser. The latter goes after the orignal div class="fb-page" element.
FBmobile {
font-size: 16px; color: #fff; }
This is not a workaround, this is just an info why is it not working...
Please fix this asap
I have same issues at the moment.
Refused to display 'https://m.facebook.com/' in a frame because it set 'X-Frame-Options' to 'deny' on mobile
Is there a workaround?
Thank you
still happening. anybody has any workaround for responsive display?
I faced the same issue as well. Has anyone found a workaround?
