Hi there,
There is no update yet, maybe the same in the coming days. Facebook browser is non-standard browser, so it may take time for our developers to debug it. As of now, there is no way of checking/debugging it.
Thanks!
Thankf for the reply @Rad
Facebook’s browser is using SAFARI as an in app browser. i
Its extremely common usage of Safari inside facebook since all traffic coming from Facebook ios comes uses it.
Additionally, i advertise my site on facebook so thats 80% traffic to my site and everyone is seeing a broken site 
I hope there’ll be a solution soon for this! I hope someone can have a quick look at it because i know basically what the issue is. The inapp safari browser is taking the whole screen as the frame of the page and thats why the sticky menu is getting hidden behind the black bar on top of the page. (Theres a screenshot on top of this post)
Thanks again @Rad
Noted. Please stay tuned for updates. Thanks
Thank you.
Hi Support !
Any updates on this ? Thanks !!!
Howdy,
Thanks for writing in! Regarding this particular situation, there is a little bit of confusion surrounding the in-app browser for Facebook. “In-app browsers” are not actual browsers, but a webview window running off your device’s core browser. A webview is a chromeless browser window that’s typically configured to run fullscreen. Effectively, it’s kind of using some of the same technology but is in no way a 1:1 analog to Safari.
I wanted to personally write in to let you know that we have taken note of this and the resources shared from StackOverflow and will be taking it into consideration when we find the time to revisit this. At this time particular juncture, we are monitoring our latest releases of Pro and X and keeping watch over that for the next day or so to ensure things are running smoothly. This has been noted in our system as something to investigate, but regretfully we are unable to provide any sort of timeline on this. It is tricky for the reasons mentioned previously such as it not being a “true” browser that follows all spec conventions and there is no real way to adequately inspect and troubleshoot these issues live due to the nature of the browser. Also, in some of the resources shared, the “fixes” quickly approach the realm of being quite “hacky,” and when we have a user-base as large as ours to consider, we cannot implement changes such as those suggested in such a cavalier manner as they have huge implications for how things function. This is a much more intricate and involved update than it might appear on the surface for many reasons.
All that being said, as noted previously, we have this documented in our system and will work to find the time to address it, but we are unable to provide any sort of timeline as these things are always fluid to some degree as items come into view and we must assess what requires our attention at the time.
Thank you for your understanding, and if we have any updates on this we will work to inform you here when that time comes, or you will be able to see news of it in a changelog for a release when that time comes.